Discussion Locked

Routing problem between NT 4.0 Servers

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

I have this routing problem between my NT 4.0 systems that is driving me nut. We have a couple of Windows NT 4.0 servers and a Novell Netware 3.12 serving just over 100 users on our LAN. We have a WAN link of 64kbps leased line connecting the head office to the two branches via a 2600 series Cisco router. The problem now is this: My office just deployed a wireless radio link via an ISP to the Internet and there started my headache. For security reasons, we installed a multi-homed Windows NT 4.0server and dedicated it for proxy service excluding all range of IP addresses that are not part of our LAN. The IP adresses for this server are 192.0.0.199 mask 255.0.0.0 default gateway 192.0.0.250 (LAN) and 63.130.101.236 mask 255.255.255.224 default gateway 63.130.101.225 (from the ISP). Now, the PDC can't ping Internet(external)IP addresses using the multi-homed proxy server NT 4.0 system as gateway. The PDC has been configured with two gateways (192.0.0.250- for the WAN LINK and 192.0.0.199- to the proxy server system). The route to the DNS servers (63.227.234.195 & 210) has also been added to the PDC interface yet it can't ping them. tracert and NSLOOKUP brings no result. domain name resolution is not possible.
The PDC can ping the two interfaces of the proxy server system. Can somebody help?

7 replies

by parbo

It seems that your routing stops at the lan connection. Both your gateways point to the lan itself and none to the ISP link. Default gateways specify where to look for an ip address if its not on the LAN. Try setting the GW's on your PDC to 192.0.0.199 and the 2nd to 63.130.101.236. For the DNS use at least one external DNS.

by oyeleye

I've tried using both 192.0.0.199 and 63.130.101.236 as the gateways on the PDC without success. Using 63.130.101.236 might not work 'cos the IP address on the PDC reads 192.0.0.200, packets meant for the 63.130.101.0 network will be dropped 'cos there is no interface to carry them. To solve this I tried using a valid IP address on the 63.130.101.0 network as an alternative IP address on the PDC but this will not work too 'cos the system will be acting as multihomed.

Please don't give up on me!

by parbo

have you tried to use a static routing table, where you add a route to the table?
I assume both connections work independently. Can you at least ping the proxy external addres 63.130.101.236?
reply to my hotmail account if you like.

by stillatit

Taking stuff roughly in order:

1. Your LAN address for the server is 192.0.0.199 with a mask of 255.0.0.0 ??? What is a class A mask doing on class C number? If you were trying to use private addressing, you should be in range 192.168.x.y with a mask of 255.255.255.0.

2. Since 192.0.0.x mask 255.255.255.0 is theoretically a legal address somewhere on the internet, you should not be using those numbers unless they are assigned to you. If IP forwarding is not turned off on the Proxy box (itshould be anyway), you can cause routing problems on the net.

3. The way Proxy is set up, you place in the Local Address Table (LAT) the address ranges of your local network. Is that what you meant by "excluding all range of IP addresses that arenot part of our LAN"? If not, you need to check this configuration.

4. If you did not install the proxy client on all machines other than the proxy server, those machines will not be able to ping, or do other tcp/ip things outside your network. The Winsock client on each machine intercepts those calls to the protocol stack and redirects the requests to the proxy server.

5. Proxy is a very complex product. I strongly advise reading ALL of the manual.

Good luck.

by oyeleye

Sorry for the wrong info on the subnet mask The PDC's IP address is 192.0.0.199 with subnet mask of 255.255.255.0 and not 255.0.0.0.

This discussion is closed to new replies.