Computing.Net > Forums > Windows NT > NT4.0, IIS4, Proxy 2.0 no workee!!!!

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

NT4.0, IIS4, Proxy 2.0 no workee!!!!

Reply to Message Icon

Name: Joe Lang
Date: July 8, 2002 at 10:25:07 Pacific
Comment:

I come from a Novell background and am learning NT via the 'throw him in' method.

Our proxy server developed a bad virus and I set up a new one, which ain't working. Old one- NT4.0, IIS3.0, Proxy 2.0- New one- NT4.0, IIS4.0, Proxy 2.0

The signal from the router goes to a 10/100 hub, from there to a Nortell Accelar. The Accelar has five ports set with private address spaces for student access, 10.12.xx.xx, each accelar port being 10.12.xx.1, so each building is a different subnet. One accelar port is 10.12.1.1. This feeds back into the 10/100 hub via a fiber connection. The proxy server's internal nic is 10.12.1.11, so it should get that traffic. I can ping from student stations to 10.12.1.1, I can ping from the proxy to 10.12.1.1, but student stations cannot find the proxy server. They all report trying to find 10.12.1.11 and can't find it. As far as I can see, it should be working. Nothing special on the f/o port that feeds from 10.12.1.1, nothing special on port that connects to 10.12.1.11. I'm about ready to tear my hair out. Old proxy server is disconnected and I got it up, setup is exactly mirrored on new server.

Any ideas?



Sponsored Link
Ads by Google

Response Number 1
Name: Stuart Clarke
Date: July 9, 2002 at 02:55:55 Pacific
Reply:

Have you checked for static routes on the old server ? Maybe you're missing some...
Check from dos using route print then check the default route, etc.


0

Response Number 2
Name: Joe Lang
Date: July 9, 2002 at 10:13:57 Pacific
Reply:

Yes, I have. But, unfortunately, one of the things I tried was changing the NIC card. I used the second nic from the old proxy server. Poof, no more static routes. I did run the f/o connection for 10.12.1.1 into a separate switch and connected proxy's internal interface to that switch, no joy. I can ping from the client, which is 10.12.64.xxx to 10.12.1.1, the gateway to the proxy, and 10.12.1.9, the switch connected to the internal card, but cannot ping the card itself. Everything I've read says that it is set up just as it should be, but nobody ain't talking to nobody. I could set up a static route for 10.12.1.11 making 169.204.186.1 the gateway, but I don't see what good that would do if the clients themselves cannot see the internal nic on the proxy at all. It's all very strange and I have a headache.


0

Sponsored Link
Ads by Google
Reply to Message Icon

Related Posts

See More


NT sees only 8GB of my ne... CD RW permissions



Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows NT Forum Home


Sponsored links

Ads by Google


Results for: NT4.0, IIS4, Proxy 2.0 no workee!!!!

Proxy 2.0 server www.computing.net/answers/windows-nt/proxy-20-server/19973.html

Winnt & Proxy 2.0 www.computing.net/answers/windows-nt/winnt-amp-proxy-20/22507.html

WinNT4.0 server and MS proxy 2.0 HELP! www.computing.net/answers/windows-nt/winnt40-server-and-ms-proxy-20-help/4636.html