Win2000 Routing NAT

I am running Server2000 with 1 NIC
and 1 Modem.  
NAT services doesnt seem to "route" the network for the computers connected to
the server.
NAT will NOT allow connectd computers
to ping or surf across to the interfaced modem to see the "gateway".
NAT DIALUP, of course makes the connection fine....and my ISP gives the server an IP address and gateway.  
The SERVER sees the gateway
and surfs/pings fine on internet.

No NAT/network routing via the modem/nic card.  (meaning NO SHARED access)
How to make the "shared" modem connection run via NAT?  


mavvAsked:
Who is Participating?
 
Moses_RConnect With a Mentor Commented:
You need to setup your forward lookup zones on the domain server. There are several resources that show you how to do this. Just do a search on Hotbot for network adress translation and you'll find it.
0
 
estestCommented:
mavv,

We need a couple of tests here....

Can you ping the 2000 server from the clients?
Is the default gateway on the clients set to the NIC on the 2000 server?
Also check your subnet masks, they can also effect routing...


Tim
0
 
mavvAuthor Commented:
Tim:  Yes to all your questions.
But the gateway on the server2000 is
BLANK ....AFTER demand dialup makes
the connection to ISP.
NAT demand dialup goes blank after
calling into ISP and getting gateway
on modem showing up.
NIC card has no gateway shown using
ipconfig /all.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
apaduaCommented:
Are your clients set up for DHCP? You can't have manually configured IP addresses for them. Also, is there a DHCP server on your network (If there is one, Internet Sharing will disable its DHCP, and your machines won't get an IP).
0
 
estestCommented:
I configured 2 Win2K Pro machines for sharing and this is what I saw...

The "server" changed the addresses of my NIC to 192.168.0.1 when I enabled sharing on it....
I did not change the modem properties...

I configured the "client" for DHCP and it drew an address from the "server".

That's really strange that your "server" doesn't have a default GW setup even when you are dialed into the ISP. Your "client" machines shouldn't have a problem with their default GW settings since they are DHCP.

I did not use demand dialup (I just VNC to the other  machine when I need the connection...) so I can't speak about it.



Tim
0
 
mavvAuthor Commented:
I am in the process of reloading
server2000.  DHCP is set and working
correctly.  DNS is working.  Client machine is working.  Clicking SHARE modem connection works.
MANUALLY SETTING NAT and NOT CHECKING
SHARE MODEM .....IS NOT WORKING.
NAT will not allow translation across
ISP to LAN.  NAT will only allow ISP to
talk to server2000.  
WHY WHY WHY?
0
 
PortangCommented:
Hi, Mavv, are you still there ?

1. DHCP is not necessary, period. Sorry, apadua.

2. Windows 2000 Server has two ways of sharing Internet:
 A. ICS - By check the "Allow Internet Connection Sharing" on the Dial-Up Networking's Sharing Property.
 B. NAT - By configuring RRAS, the Routing and Remote Access Service.

3. Your NAT probably actually means ICS, Internet Connection Sharing, in this case. In fact, it's easier to configure.

4. Your Internal network has to be 192.168.0.x  w/ mask of 255.255.255.0 .  Is this what you have with your Ethernet ??  If not, and you don't want to adapt to this private IP scheme, then you need to configure RRAS w/ NAT !

5. Based on the above:
*** On the server - Make Ethernet adapter having IP of 192.168.0.1 . Also share the Dial-Up Network Adapter for Internet.
*** On the other computers - Make sure their default gateway is 192.168.0.1 . Also make sure in "Internet Options", choose MANUAL configure, LAN connection, NO proxy ...

Please feel free to let me know if there is any questions.  If you're interested in RRAS w/ NAT, surely let me know, too.
0
 
apaduaCommented:
Sorry dude. You're right. W2000 Professional is the one that requires DHCP. OOPS.


A.
0
 
PortangCommented:
Could somebody out there to unlock that thing !
0
 
mavvAuthor Commented:
Answer accepted
0
 
mavvAuthor Commented:
U were correct....forward lookup
was not running correctly.
Thanks again..........and it works
now.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.