Discussion Locked

Can't view websites using Win2k from NT4

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

Here's a strange one...

We are running a web server on Windows 2000. The main page doesn't require any authentication, just static HTML. It's behind a Watchguard Firewall using NAT.

We also have a partner company that runs NT4 workstations, IE 5.5, sharing an ISDN connection using a ZYXEL Prestige 1001H ISDN Hub Router. Looking at the services on the system, no strange programs appear to be running. I was told that they installed a Porn Filter, but I couldn't find out where it was blocking things (pretty sure it's not at the workstation level).

So, from any maching running NT4, we can't get to our website or connect to any service at that location. We get a ping response, traceroute works fine, but no connections. However, if you boot up a laptop running Windows 2000, the connection works fine.

The only thing I could think of was that the domains were different. The NT4 machines logged on to a local domain. But, the 2000 laptop was just standalone. The web server is running on a seperate domain.

Can anyone else think of a reason for this? Thanks in advance for any advice!

1 reply

by shmaltz

If Tracrert and ping work and Win2k works it is for sure a firewall problem, but to make sure try first the following:
at a command prompt type the follwing:
telnet dnsname/ipaddress 80 (where dnsname/ipaddress is either the DNS name or the IP address).
if the screen stays blank (it doesn't give you an error) then somthing is wrong with IE, if it does give you a connection error than the problem is with the firewall/filtering.
Another way to make sure that it is the filtering:
In IIS on the Web server change it so it uses port 81 istead of the default 80, now on the clients tryp to connect to your server using www.domainnaem:81 (where www.domainame is the url for the web server, you can also use the IP Address, the :81 tells IE that it should connect using port 81 instead of the default 80) you have to make sure that the port number appears before any slashes or IE will not read it as a port number. For example www.techrepublic.com:81 tells IE to connect to techrepublic using port 81, while www.techrepublic.com/:81 doesn't do the same.

This discussion is closed to new replies.