Quote:
Quote:
The browser gives me a "DNS error or server cannot be found" error.


Ah, the catch-all Internet Explorer error. It could mean any of the following:

1. No DNS.
2. No route to the server.
3. Nothing listening on port 80 on the server.
4. Connection dropped after connecting to port 80 on the server.

You have to diagnose each one in turn. nslookup will help you diagnose (1). tracert (or traceroute will help you diagnose (2), and telnet or netcat will help you diagnose (4).

Obviously, if you're having this problem with every website you contact, then it's not (3) or (4). If other traffic's working fine, then it's probably not (1) or (2).

What can sometimes cause this problem in IE is if you've got a misconfigured (or misdetected) proxy.


It's definately not a misconfigured IE issue. It happened on all the pc on the network when I made the DNS changes. In order to make it work I had to revert my DNS changes on the Win2K server and then for some reason turn off the proxy built-into the smoothwall. The problem is also present on FireFox... again with no changes made to its configuration.

Rene
_________________________
12 gig empeg Mark II, SN: 080000101
30 gig RioCar SN: 30103114
My blog