Some burning technical issues...
 

I thought the whole idea behind the Internet originally was if part of it goes down here, the information will automatically be rerouted around the problem area and get to its destination. So why are there occasions when some people can't see a site due to "a router problem in Iowa" or something like that?

Why is it that some domains won't work with the www. in front of them and some won't work without?

And what is it with www2. and shit like that? Is there a 2nd World Wide Web?

Enquiring minds would like to know...

eh you have much to learn :thumbsup

A) You can't access the site because that is the only backbone (assuming we are talking about a backbone) the server is connected to.

B) www2, www3, are just additional servers on some websites. (usually mirrors)

Q: Why is it that some domains won't work with the www. in front of them and some won't work without?

A: server is not set up right - should answer the header both with and without the www.


Q: And what is it with www2. and shit like that? Is there a 2nd World Wide Web?

A: That is the L33tnet - its 1005 cool



Q:So why are there occasions when some people can't see a site due to "a router problem in Iowa" or something like that?


A: Depends on what kind of connection the host is on. If he only got one route to a DIX (keypoint on the net) then he is dead if the string is cut. Closer to DIX = better

You see that way too much and on big company web sites etc.
Funny.


Burtman

Here's a tip for IE users:

Simply type the URL of the website without the www. & .com, and hit Ctrl+Enter on your keyboard. Internet Explorer automatically fills in the http://www. .com. This is called inline AutoComplete.

yep - mostly because they have some retarded local IT-guy set it up, and not the host

whoa

cool:)