Not going out of local network

  • Thread starter Thread starter Mike Ryan
  • Start date Start date
M

Mike Ryan

I have a couple of computers that are suddenly having the same problem over
the last few days.

The computers are doing the following:
they will ping a number inside the local network and outside.
they will map to drives within the network
they will not find the dns server to locate a domain name(yahoo.com not
found) I have checked and given several valid dns servers sitll nothing.
If you type in the address IE 6.x will not pull up the page for that site.
even the intranet web pages.


I have unistalled the network drivers and reinstalled them I have also tried
firefox.
I had the same problem on another computer and reinstalled the computer from
scratch everything works fine.

any Ideas were to turn to I do not want to keep reinstalling everything on
their computers?

thanks for your help

Mike Ryan
Gunnison Valley Hospital
IT Specialist
 
All machines on the LAN must use the internal LAN's AD/DNS Server for DNS
and they should never use any other DNS, ever.

The AD/DNS machine then uses the ISP's DNS as a "forwarder" listed in the
Forwarders list within the config of the DNS services.

Never use an IP# in a URL. IE does *not* know what an IP# is,...it will
simply see the "dots" and assume it is a FQDN and will try to send it to a
proxy server no matter what (assuming there is a proxy). Using IP#s in a
URL is not a way to test. IP#s work fine in UNC paths (Windows Explorer),
but not Internet URLs (Internet Explorer).
 
Phillip Windell said:
All machines on the LAN must use the internal LAN's AD/DNS Server for DNS
and they should never use any other DNS, ever.

The AD/DNS machine then uses the ISP's DNS as a "forwarder" listed in the
Forwarders list within the config of the DNS services.

Never use an IP# in a URL. IE does *not* know what an IP# is,...it will
simply see the "dots" and assume it is a FQDN and will try to send it to a
proxy server no matter what (assuming there is a proxy). Using IP#s in a
URL is not a way to test. IP#s work fine in UNC paths (Windows Explorer),
but not Internet URLs (Internet Explorer).
Click to expand...

So how come this works then ?

http://216.37.33.199/

True it will get you the wrong website sometimes where the host has virtual
servers, for example this IP is what came back from doing a DNS on the
wandtv address you quoted, but all I typed in to IE was the number
216.37.33.199 and then copied and pasted it back here from IE... IE added
the http://

Charlie
 
Charlie Tame said:
So how come this works then ?

http://216.37.33.199/
Click to expand...

It is because you don't have a proxy server in the IE proxy settings. When
the proxy settings are blank, IE just dumps the request on the OS's
networking layers which have no trouble knowing what to do with it. My main
point is that using IP#s in a URL is not a good way to test connectivity
because in certain situations it does not avoid possible DNS problems, but
actually makes it worse.

I'm not making it up. This is a known behavor. All versions of IE are that
way and it is possible (I haven't verified) that all other Mosaic-Based
browsers are this way (Netscape, Mozilla, etc):
http://support.microsoft.com/default.aspx?scid=kb;en-us;303650

Here is the relvant quote from the article:
 
Phillip Windell said:
It is because you don't have a proxy server in the IE proxy settings.
When the proxy settings are blank, IE just dumps the request on the OS's
networking layers which have no trouble knowing what to do with it. My
main point is that using IP#s in a URL is not a good way to test
connectivity because in certain situations it does not avoid possible DNS
problems, but actually makes it worse.

I'm not making it up. This is a known behavor. All versions of IE are that
way and it is possible (I haven't verified) that all other Mosaic-Based
browsers are this way (Netscape, Mozilla, etc):
http://support.microsoft.com/default.aspx?scid=kb;en-us;303650

Here is the relvant quote from the article:
-----------------------------------------------------
CAUSE
This behavior may occur if an FQDN or IP address contains periods. If an
FQDN or IP address contains a period, Internet Explorer identifies the Web
site or share as in the Internet zone.
---------------------------------------------------------
Click to expand...



Sorry the reply is a bit late, must have missed this group for a few days.
Yes I understand that but I wasn't aware that a proxy was being used. I have
actually met this problem using shared stuff before and I'm not sure if
other browsers make this assumption either. Will have to try it sometime.
 
Charlie Tame said:
Sorry the reply is a bit late, must have missed this group for a few days.
Yes I understand that but I wasn't aware that a proxy was being used. I
have
Click to expand...

So a proxy was being used?
I can't see the machine myself, I was offering that as the possiblity for
the situation.
 
Back
Top