Strange Routing problem...

  • Thread starter Thread starter Sean Rector
  • Start date Start date
S

Sean Rector

I have a client who had a DSL Router go bad, and they do not want to replace
it. They had a spare nic, so viola, the server became the router as well.

Problem I've got is that the client machines can ping both nics in the
server, and the server is forwarding DNS queries, but they cannot ping the
public nic's gateway (the server can).

Configuration is as follows:

Win2k Svr, SP4
DHCP - Scope is 192.168.0.100 - 192.168.0.200.
DNS - Forwarding is enabled, and it is looking on both nic's.

LAN Nic is configured as follows:
IP 192.168.0.1
Mask 255.255.255.0
GW

DNS 192.168.0.1

WAN Nic is configured as follows:
IP 64.xxx.xxx.xxx
Mask 255.255.255.0
GW 64.xxx.xxx.1

DNS 64.xxx.xxx.10
64.xxx.1.10

Added Registry entry for EnableIPForwarding = 1

No ideas what to try next.

TIA

Sean
 
here's what seems to be your configuration

Client -------------(private i/f)Server(public i/f)----------------Public
Gateway.

Now when you try to ping from server, ping uses public address 64.x.x.x to
ping the gateway and since gateway knows this address it reponds back and
ping succeeds.
When clients try to ping public gateway they use private address 192.168.0.x
address. Public gateway get the ping packet but does not know how to route
it (because 192.168.0.x) is private address. So ping fails.

To enable private clients to be able to contact public internet via just one
public address look at article http://support.microsoft.com/?id=310888
 
The problem I'm seeing with your answer is that these are not RAS clients -
RRAS is not installed, but I did add the Registry Entry for
EnableIPForwarding

Must RRAS be installed as well, even though these are wired clients?

Your diagram is correct, btw.
 
Re-read article - follow up question on article...

I have to run the command "netsh routing ip nat add interface internal
private" to enable NAT? Both I/F's show up in the Routing Tables (public=if
2 and private=if 3), but I'm not positive what I replace "private" in this
example with - the IP or "if 3".

I personally think there should have been more examples of the route command
in "route ?".
 
DNS on your external nic should *only* point to your server-IP. Check the
bindingorder and make sure the internal nic is on top.
 
I don't think that article applies to this scenario since there are no RAS
or VPN clients.

Sean you need to configure the server to do NAT. See 310357 HOW TO:
Configure the NAT Service in Windows 2000
http://support.microsoft.com/?id=310357

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Jeez...

You'da thunk it coulda been done w/o installing RRAS. Now I know better.

Thanks Marc.

Marc Reynolds said:
I don't think that article applies to this scenario since there are no RAS
or VPN clients.

Sean you need to configure the server to do NAT. See 310357 HOW TO:
Configure the NAT Service in Windows 2000
http://support.microsoft.com/?id=310357

--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.
Click to expand...
 
Back
Top