Networks

Ask something
Discussion Locked

NAT won't share?

0 helpful
6 replies

by kuryous1

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Please bare with me. SOHO network using Windows 2003 SBS as it's main server. Active Directory,domain controller,etc. Windows 2000 Advance is member server with ADSL installed and connected. Two NIC's for public and private interface. Private IP: 192.168.X.X. Enabled RRAS and NAT(LAN only). Instructions said to activate the DHCP allocator and DNS proxy on the NAT if I have DHCP on the LAN. Event logs says allocator shutdown because of two DHCP's on same network. Un-check automatic IP addressing and client resolution and still nothing. Now suddenly, the modem itself sent a DHCPNACK meesage and no DSL? HelP! What am I obviously doing wrong?? Thanks alot in advance.....very troubled..:-(

6 replies

by cg it

I'm curious as to why your using another server to act as a gateway. Not that is matters but it does make things somewhat more complicated and more expensive. You could opt for a consumer level router which if far less expensive, has NAT built in, and most have a firewall built in a well. Does everything that your trying to do with your member server.

IMHO if your going to run a server to act as a gateway/router for your network, install something like ISA Server 2004 [you can download free trialware for it] or some Proxy Server software package AND firewall package. That way it will do everything your trying to get it to do e.g. be a proxy server/gateway for your network AND provide firewall protection.

DHCP has options for providing clients gateways,routers,DNS, other DHCP addressing. Configure DHCP with these options.

on your member server thats the gateway, RE-check automatic IP & DNS address discover on the external interface that hooks up to your modem.
On the internal interface set a static IP address[which will become your gateway address]. Run the ICS wizard.

by kuryous1

Sorry for the delay. (Network problems) The network was inherited. Original tech wanted to set up a DMZ with two servers but couldn't. Now I get to try with cost issues. (seriously!) No router, software, etc. Use what I have. (FUN!) I know that 2003 SBC doesn't do trusts. Therefore, member server. The problem appeared to be with the two NIC's communicating. I did setup the Private side with static IP. DNS & Gateway pointing to ISP's IP per ipconfig. Public is dynamic. NAT allocator turned off and I am connected to all workstations. However, I'm new to routing and suspect that I'm still having NIC problems. I'm dropped at odd times and event logs give no clue other then "can't find...". Thanks in advance

by sgt_shultz

run around to everything essential to this setup and use ipconfig to see what it is set to. make notes...you might find one without valid ip addresss
you sure dsl modem is not trying to dish out dhcp stuff? i think you went down because something didn't get good ip address. but i am confused as to what. modem? public nic? private nic? by now you are back up i bet by fooling with ipconfig and setting up static
you have need of server to be at public routable ip address?
are you back up?
let us know what is going on...we will help you get working and save advice on configuring for later...

by kuryous1

Lets pretend I'm working for a mean and stengy employer and wants absolute perfection in his obsolete network setup...:-) My Job....fixit!

This discussion is closed to new replies.