Not able to browse but tracert and ping work fine.

[Guest]

What can be the problem if I have some computers on a network that won't
browse through IE? The clients can ping external addresses and I can run
tracert and it bounces through fine. The servers on the network get on the
internet fine and so does my laptop. Any suggestions would be greatly
appreciated.
Thanks,
Tom

 

[Kevin D. Goodknecht Sr. [MVP]]

What can be the problem if I have some computers on a network that
won't browse through IE? The clients can ping external addresses and
I can run tracert and it bounces through fine. The servers on the
network get on the internet fine and so does my laptop. Any
suggestions would be greatly appreciated.

Are you able to resolve internet names using nslookup?
Are you using an Active Directory domain?

Post an ipconfig /all from a client and a server.

 

[Guest]

Thanks for the quick response. The dns from the server tests fine. I didn't
try the nslookup. I am using AD on a Windows 2000 server. The ipconfig /all
looks the same on the servers and clients. All clients point to the server
for dns and even when I point them to our internet providers dns they still
won't work. The act like they are going to bring up a website then just
freeze up. Thanks.

 

[Herb Martin]

Thanks for the quick response. The dns from the server tests fine. I
didn't
try the nslookup. I am using AD on a Windows 2000 server. The ipconfig
/all
looks the same on the servers and clients. All clients point to the
server
for dns and even when I point them to our internet providers dns they
still
won't work.

Don't do this EXCEPT for very temporary testing on a single
machine -- it will mess up your domain authentication and
resource access even to MIX internal with external (Internet)
DNS servers. Internal DNS clients must point STRICTLY at the
internal DNS server (set) which can resolve every name they
will ever need.

Even when testing it is generally best to use the nslookup with
an explicit IP for the external DNS to perform the other test
anyway.

Ok, back to the problem: You can resolve names since Ping
(and presumably Nslookup) works.

Therefore you do not have a DNS issue but rather some problem
with IE.

The act like they are going to bring up a website then just
freeze up. Thanks.

Perhaps a "popup protector" or some other add-on. Perhaps
a full cache area. Perhaps a damaged DLL in IE (reinstall).

You most likely have some issue with IE.

(I have seen or experience all of the above -- and DNS problems
too -- so they are all real possibilities.)

You can test this by installing a second browser (Firefox etc.)
that does NOT use the IE browser control (e.g., do NOT use
Netscape as its current default it to use IE for the browser pane.)

 

[Guest]

Actually Herb, the nslookup gives me an error message:

NSLOOKUP MSN.COM
Server: Msn.com
Address: 207.68.172.246

DNS request timed out.
timeout was 2 seconds.
***Request to msn.com timed-out

I get this error message even from the machines that the internet works fine
on. However, the majority of the pcs won't load. I installed firefox and
it won't load a page either. Thanks for your help.
Tom

Thanks for the quick response. The dns from the server tests fine. I
didn't
try the nslookup. I am using AD on a Windows 2000 server. The ipconfig
/all
looks the same on the servers and clients. All clients point to the
server
for dns and even when I point them to our internet providers dns they
still
won't work.

Don't do this EXCEPT for very temporary testing on a single
machine -- it will mess up your domain authentication and
resource access even to MIX internal with external (Internet)
DNS servers. Internal DNS clients must point STRICTLY at the
internal DNS server (set) which can resolve every name they
will ever need.

Even when testing it is generally best to use the nslookup with
an explicit IP for the external DNS to perform the other test
anyway.

Ok, back to the problem: You can resolve names since Ping
(and presumably Nslookup) works.

Therefore you do not have a DNS issue but rather some problem
with IE.

The act like they are going to bring up a website then just
freeze up. Thanks.

Perhaps a "popup protector" or some other add-on. Perhaps
a full cache area. Perhaps a damaged DLL in IE (reinstall).

You most likely have some issue with IE.

(I have seen or experience all of the above -- and DNS problems
too -- so they are all real possibilities.)

You can test this by installing a second browser (Firefox etc.)
that does NOT use the IE browser control (e.g., do NOT use
Netscape as its current default it to use IE for the browser pane.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

 

[Kurt]

Two problems. The server that replied was msn.com. Unless your domain is
named msn.com, the reply should have come from your AD DNS server. Here are
the results when msn.com is queried on one of my DNS servers:

C:\>nslookup msn.com
Server: dc-01
Address: 192.168.10.74

Name: msn.com
Address: 207.68.172.246

Your clients (and your servers) should point ONLY to the AD DNS server(s).
If your server can't resolve Internet names there are several possibilities:

1) The DNS service is not running.
2) You have a root (".") forward lookup zone and have not configured
forwarders.
3) Your DNS server cannot get to the Internet (wrong default gateway or
other setting)
4) You have a firewall issue.

I'm sure there are others, but those would be a good place to start. First
be sure you can resolve names from the DNS server itself, and that the reply
is coming from your own server. Get that working, then move on to DNS
clients.

....kurt

Actually Herb, the nslookup gives me an error message:

NSLOOKUP MSN.COM
Server: Msn.com
Address: 207.68.172.246

DNS request timed out.
timeout was 2 seconds.
***Request to msn.com timed-out

I get this error message even from the machines that the internet works
fine
on. However, the majority of the pcs won't load. I installed firefox
and
it won't load a page either. Thanks for your help.
Tom

Thanks for the quick response. The dns from the server tests fine. I
didn't
try the nslookup. I am using AD on a Windows 2000 server. The
ipconfig
/all
looks the same on the servers and clients. All clients point to the
server
for dns and even when I point them to our internet providers dns they
still
won't work.

Don't do this EXCEPT for very temporary testing on a single
machine -- it will mess up your domain authentication and
resource access even to MIX internal with external (Internet)
DNS servers. Internal DNS clients must point STRICTLY at the
internal DNS server (set) which can resolve every name they
will ever need.

Even when testing it is generally best to use the nslookup with
an explicit IP for the external DNS to perform the other test
anyway.

Ok, back to the problem: You can resolve names since Ping
(and presumably Nslookup) works.

Therefore you do not have a DNS issue but rather some problem
with IE.

The act like they are going to bring up a website then just
freeze up. Thanks.

Perhaps a "popup protector" or some other add-on. Perhaps
a full cache area. Perhaps a damaged DLL in IE (reinstall).

You most likely have some issue with IE.

(I have seen or experience all of the above -- and DNS problems
too -- so they are all real possibilities.)

You can test this by installing a second browser (Firefox etc.)
that does NOT use the IE browser control (e.g., do NOT use
Netscape as its current default it to use IE for the browser pane.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

:

Tom wrote:
What can be the problem if I have some computers on a network that
won't browse through IE? The clients can ping external addresses
and
I can run tracert and it bounces through fine. The servers on the
network get on the internet fine and so does my laptop. Any
suggestions would be greatly appreciated.

Are you able to resolve internet names using nslookup?
Are you using an Active Directory domain?

Post an ipconfig /all from a client and a server.

 

[Herb Martin]

Actually Herb, the nslookup gives me an error message:

NSLOOKUP MSN.COM
Server: Msn.com
Address: 207.68.172.246

DNS request timed out.
timeout was 2 seconds.
***Request to msn.com timed-out

I get this error message even from the machines that the internet works fine
on. However, the majority of the pcs won't load. I installed firefox and
it won't load a page either. Thanks for your help.

Then you just add the -time=10 (or some such) parameter to the NSLookup
command.

nslookup -time=10 name.company.com IP.Address.DNS.Server

If you get an error where NSLookup cannot lookup the ADDRESS and
get the NAME of the DNS server that is a bogus (and irrelevant)
"feature" (read: bug) in NSlookup, ignore it as long as you get the
answer to the REAL question.

 

[Herb Martin]

Actually Herb, the nslookup gives me an error message:

NSLOOKUP MSN.COM
Server: Msn.com
Address: 207.68.172.246

DNS request timed out.
timeout was 2 seconds.
***Request to msn.com timed-out

Why are you querying an MSN.com server? The LONG timeout will
fix this failure if you really want to query MSN directly.

You should ALWAYS show us the command you entered as well, not
just the results.

Your internal DNS clients should NOT be set to use MSN directly.

I get this error message even from the machines that the internet works fine
on. However, the majority of the pcs won't load. I installed firefox and
it won't load a page either. Thanks for your help.
Tom

Thanks for the quick response. The dns from the server tests fine. I
didn't
try the nslookup. I am using AD on a Windows 2000 server. The ipconfig
/all
looks the same on the servers and clients. All clients point to the
server
for dns and even when I point them to our internet providers dns they
still
won't work.

Don't do this EXCEPT for very temporary testing on a single
machine -- it will mess up your domain authentication and
resource access even to MIX internal with external (Internet)
DNS servers. Internal DNS clients must point STRICTLY at the
internal DNS server (set) which can resolve every name they
will ever need.

Even when testing it is generally best to use the nslookup with
an explicit IP for the external DNS to perform the other test
anyway.

Ok, back to the problem: You can resolve names since Ping
(and presumably Nslookup) works.

Therefore you do not have a DNS issue but rather some problem
with IE.

The act like they are going to bring up a website then just
freeze up. Thanks.

Perhaps a "popup protector" or some other add-on. Perhaps
a full cache area. Perhaps a damaged DLL in IE (reinstall).

You most likely have some issue with IE.

(I have seen or experience all of the above -- and DNS problems
too -- so they are all real possibilities.)

You can test this by installing a second browser (Firefox etc.)
that does NOT use the IE browser control (e.g., do NOT use
Netscape as its current default it to use IE for the browser pane.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

:

Tom wrote:
What can be the problem if I have some computers on a network that
won't browse through IE? The clients can ping external addresses and
I can run tracert and it bounces through fine. The servers on the
network get on the internet fine and so does my laptop. Any
suggestions would be greatly appreciated.
Are you able to resolve internet names using nslookup?
Are you using an Active Directory domain?

Post an ipconfig /all from a client and a server.

 

[Guest]

Thanks for the help I'll check your suggestions guys. Tom

Actually Herb, the nslookup gives me an error message:

NSLOOKUP MSN.COM
Server: Msn.com
Address: 207.68.172.246

DNS request timed out.
timeout was 2 seconds.
***Request to msn.com timed-out

Why are you querying an MSN.com server? The LONG timeout will
fix this failure if you really want to query MSN directly.

You should ALWAYS show us the command you entered as well, not
just the results.

Your internal DNS clients should NOT be set to use MSN directly.

I get this error message even from the machines that the internet works fine
on. However, the majority of the pcs won't load. I installed firefox and
it won't load a page either. Thanks for your help.
Tom

Thanks for the quick response. The dns from the server tests fine. I
didn't
try the nslookup. I am using AD on a Windows 2000 server. The ipconfig
/all
looks the same on the servers and clients. All clients point to the
server
for dns and even when I point them to our internet providers dns they
still
won't work.
Don't do this EXCEPT for very temporary testing on a single
machine -- it will mess up your domain authentication and
resource access even to MIX internal with external (Internet)
DNS servers. Internal DNS clients must point STRICTLY at the
internal DNS server (set) which can resolve every name they
will ever need.

Even when testing it is generally best to use the nslookup with
an explicit IP for the external DNS to perform the other test
anyway.

Ok, back to the problem: You can resolve names since Ping
(and presumably Nslookup) works.

Therefore you do not have a DNS issue but rather some problem
with IE.

The act like they are going to bring up a website then just
freeze up. Thanks.
Perhaps a "popup protector" or some other add-on. Perhaps
a full cache area. Perhaps a damaged DLL in IE (reinstall).

You most likely have some issue with IE.

(I have seen or experience all of the above -- and DNS problems
too -- so they are all real possibilities.)

You can test this by installing a second browser (Firefox etc.)
that does NOT use the IE browser control (e.g., do NOT use
Netscape as its current default it to use IE for the browser pane.)


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

:

Tom wrote:
What can be the problem if I have some computers on a network that
won't browse through IE? The clients can ping external addresses and
I can run tracert and it bounces through fine. The servers on the
network get on the internet fine and so does my laptop. Any
suggestions would be greatly appreciated.
Are you able to resolve internet names using nslookup?
Are you using an Active Directory domain?

Post an ipconfig /all from a client and a server.