Windows Forum

Ask something
Discussion Locked

Lan Gateway

0 helpful
14 replies

by mdbrewer

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Heres the info:
I've just installed a new server w/ Win2k server on it. This server is part of a push/pull network w/ another server at a different location. It's running as a PDC along w/ active directory, DHCP and Wins. Also, 2 network cards are installed, 1 for external and the other internal. All client pc's are Win98.
Now, onto the problem:
I can't get the clients out onto the internet.
The internal network card(on server) works fine as far as clients logging into the domain and accessing the server. I can ping the server and the router.(The router is connected to the external network card for internet and connectivety to the other server ie: exchange routing). From the server, i can access the internet, ping the other server andping the router and gateway. Now, from the clients, i have NO internet access. I can ping the router, but not the gateway ip. My question is this:
Where would be a general starting place for troubleshooting client pc's that cannot ping the gatewayip and don't have internet access?
I've been over the server settings what seems like a hundred times and can't find anything wrong. Could it be a possible DNS mis-configuration? Any suggestions would be much appreciated and just ask if you need more info on the server.
Thanks!
-Matt

14 replies

by sgt_shultz

i shouldn't even open my big mouth as i know nothiiinng about this really, but...
could it be you need to set up a static route on server between network segments...

by quintar51

HI,

to answer your question on where is a good idea to start from, I would say the last device that you can ping successfully.

In this case, it would be the router, as you said your Win98 clients can ping the router, but not beyond that. I would check the routing table again.

Now, just one more question. When you say your clients are unable to ping the gateway, do they get 'request timed out'?

are you ping the router by IP or by name?

If you can't ping by IP, then DNS/WINS aren't an issue...yet.

by mdbrewer

Hey Sgt Shultz and quintar51, thanks for your responses. I did try and add a static route using the "route add" command. It didn't seem to work, although i might have done it wrong. I may have to go back and look at that. Also, i did get a request timed out error trying to ping the gateway. I was using the ip address w/ ping.
Thanks!

by banyanman

Shot in the dark here, but shouldn't the win98 client's be using the server as the gateway and then the server run NAT or proxy software?

by ins413

Are the IP addresses on the NIC cards (in the server) on two diiferent subnets? If they are, then RRAS needs to be enabled and the server configured as a network router to pass the packets from one network to the other. A simple test to make sure is by pinging (from the client) the NICs in the server. If you can ping the internal adapter and not the external, then turn RRAS on and configure the server as a network router.

by lordinfidel

1st off AD Domain controllers should not have 2 Nics installed. They are not supposed to be Multihomed. That is first off.

What you need to do here is:

1. Remove the second NIC from the server.
(I am not trying to be an asshole here, but AD DC's should not have 2 NICS installed)

2. Create a second server, use it for DNS, Install 2 NICS in it. Confiugure Routing and Remote Access.

3. For your clients, their gateway should be the internal address of your internal nwtk card on the server running RRAS.

4. The next part will be tricky, you will need to figure out where to place your DC, I would personally put it on the local internal network and set up forwarders for the AD traffic ports needed for communication betweenthe other DC's.
(Don't know the ports off of the top of my head, I know 138 and 139 but there should be 2 others it needs for Domain traffic)

Also, DNS running on a DC is also bad. This can create a perpetual loop if the DC is unable to contactitself. It was in an MS article I read and it makes sense the way they put it.

by kr

You can resolve this by going into DNS MMC, Right click the Server icon, slect properties. On the properties page select the Forwarders Tab, Check Enable Forwarders. Add the IP addresses of your ISP's DSN server(s). I assume you are using DHCP. Everyone will have access...you may want to review your security.

Ken

This discussion is closed to new replies.