Discussion Locked

Proxy Server 2.0 on WinNT

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I run proxy for my Win95/98 workstations to access the internet via proxy. I have two nic cards, one internal, one external for the internet. The external one is the only one that has a default gateway. Neither my server or my workstations can access the internet. They keep timing out. I tried pinging the default gateway and it comes back as timed out. However I can ping the ISP IP address ok. My ISP says its a proxy configuration problem. They have checked the local telephone line with no problems there. When I do a tracert to my ISP it shows me a different gateway. All the IP addresses supplied by my ISP are all correct according to them. Have I missed something somewhere?

14 replies

by shawn.tooley

Check and make sure that your LAT (Local Address Table)is correct. It should include only IP's on your LAN. You could also turn on IP Forwarding in the Network Properties to see if this makes it work. I would not leave it on though; just use it to see if it corrects the problem. This would surely let you know if its your problem or the ISP's. Good luck...

by dmiles

This problem came up in a similar question last week in the forum and it refered to the hardware of UPS.Research the questions and it may give you an idea of the cause.

by dmiles

The problem is pointing towards the WINS configuration which could be rectified by reinstalling the dhcp and wins configuration.Hope this helps

by nettek

I think what is happening is that because you only have a default gateway set on the external NIC of your Proxy (which is how it should be set up), the Proxy is sending all responses that are coming from your LAN out the external NIC to the Internet. Your internal PCs will therefore receive no response. You need to tell your proxy server that the IP addresses for your LAN are internal. You do this by going to the command prompt and adding a static route:
c:\route.exe add -p 209.1.2.0 mask 255.255.255.0 209.1.2.1
The -p means persistant (this will reinstate the route statement after reboot). 209.1.2.0 is whatever the internal Net ID is for your LAN. mask 255.255.255.0 is whatever the network mask is for your LAN. 209.1.2.1 is the IP address for the internal NIC on your Proxy.
This command will tell your proxy to send responses to all IP addresses having your Net ID back out its internal NIC.

by jaybrdie

On the Internal NIC the Default gateway should be set for the Router to the internet. Make sure that the Preferred DNS on Internal NIC is set your Server. On the external NIC the default gateway should be set to the Router (like the internal NIC is set). The external NIC's IP should be on the same subnet as the Router's IP. The External NIC's Preferred DNS should be what your IP provider gave you. This covers just the NICs but there are several other areas you should check is this doesn't work. Let me know and I can tell you where else to look. GOOD LUCK!

Jay

by salexiev

Hello,
First, it will be good to check LAT table ? it must contain only your internal IP addresses (internal NIC). If it is OK, check if the workstations have MS Proxy client installed (from the server directory ? mspclnt) ? if they have this client all should be ok (although probably you will not be able to ping the Internet, because of the preset filters).
Hope it will work.

by zharia

LAT table is correct. Workstations have the client and have been updated accordingly.

by rkreuzburg

First, You have set up the proxy server EXACTLY how it is supposed to be setup. No default gateway on the internal NIC, also no IP Fowarding enabled. If you have real IP's internally it wont matter if proxy server is up and running since IP fowarding works at a lower layer and will bypass the proxy security completely. As long as you dont have a proxy client installed on the proxy server (dont laugh, this was the default setup in SBS and caused A LOT of problems) the server itself should be able to ping anything. NOTE: You wont be able to 'ping' any external IP from a WS behind the proxy so do all your testing from the server. If you can ping your own ip on the server then the IP stack is functioning correctly. If you can ping the gateway (your router) then the problem is between the router and your ISP. Call them and see if they can ping your router. If they cannot ping it then they have an incorrect route on thier end OR the router is not configured correctly. If you are using the Proxy client on the WS's then dont have a default gateway set on them. The proxy client will take care of that itself. If you are not using the client then the gateway is your server's Internal NIC's IP and you will only be able to have Web access if you configure the Web Browser to use a proxy server. If all the IP's given to you are correct then the bottom line is this is a Router issue that your ISP should be taking care of.

by zharia

Using this information I found that it was a problem with our ISP. I called them the first time and they said they couldnt ping the router, but still said it was a problem on my end. You gave me some ammo to use and after they intervened and checkedtheir settings, my proxy works fine:)
I would like to thank all of those who offered suggestions.

This discussion is closed to new replies.