Discussion Locked

http:// OR www. ?

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

We have a strange problem on IE (XP Pro SP2) with a single computer, all the other 140 on the domain are OK (Win Server2k3) If www.example.com is typed into the address it will not open the page. If http://www.example.com is then the page opens OK as normal.
Can anyone throw any light on it?

7 replies

by peter johnstone

Poster rated this answer. Thanks for the reply. The problem turned out to be an overlooked setting on our hardware firewall. However your answer did provide useful information. Thanks, PJ

by cg it

though broswers are some what smart, they only process what you type in the address bar. http:// indicates your looking for a web site with the name www..com. Just as ftp:// indicates your looking for a file transfer program site.

When Internet name servers query other name servers for an address for www..com if there isn't an A record for wild card e.g. *..com, the authoritative DNS server for the domain name won't return the query to the Internet name servers the address for www..com

www. is part of the domain name. Example: com is the top level, then next is the . then next is the www or sales or support or whatever the subdomain is. DNS would have A records that indicate sales..com is address xxx.xxx.xxx.xxx so you would be taken to that address which can display a web page. Without indicating what your looking for by using the http:// or ftp:// browsers assume http:// on port 80. As we mentioned above DNS has to be able to resolve a query for www. to return an address else the error page can not be displayed is returned in the browser.

by peter johnstone

Poster rated this answer. Thanks for the reply. The problem turned out to be an overlooked setting on our hardware firewall. However your answer did provide useful information. Thanks, PJ

by gary56789

Try doing an uninstall/reinstall through Add/Remove programs, Add/Remove windows components.

by peter johnstone

Poster rated this answer. Thanks for the reply. The problem turned out to be an overlooked setting on our hardware firewall. However your answer did provide useful information. Thanks, PJ

This discussion is closed to new replies.