strange network/internet problem

[Guest]

I'm having a strange internet connection issue - some programs are able to
connect, while others can't seem to find that I have a connection. Those
that can are, for example: IE6, Windows Media Player 10 (features like
internet radio), Windows Automatic Updates, Symantec's Live Update. Those
that can't: Firefox (any version), Thunderbird, Outlook, IE7, and update
check features built in to programs like Adobe Acrobat Reader. Also, I
upgraded from XP Home to Pro because I thought maybe it was Home's limited
network ability that might be causing the problem (I'm on a university
network), and when I had to activate the copy of Pro, the Windows Activation
program couldn't detect that I had a connection.

It doesn't seem to be a firewall issue, as both Windows firewall and
Symantec's firewall being on or off make no difference in what can connect.
While troubleshooting this with the IT guy in our department, he noticed the
Node Type, which you find by using the command "ipconfig /all", was set to
Peer-Peer. Once I figured out how to change that (to Unknown, Broadcast, or
Hybrid), that still made no difference. He set the card to manual
configuration instead of IP being assigned by DHCP, and that made no
difference. I've removed the connection and the card driver, and reinstalled
to no avail. I've even tried a different network card, and the same problems
happen. This has to be the most unusual network problem I've ever
encountered. I use a Dell Dimension 3000, P4 2.8 GHz, with an Intel Pro/100
VE built in NIC. I asked Dell support, and they said basically to reformat
and start fresh. Any ideas other than starting fresh would be greatly
appreciated - thanks!

 

[Chuck]

I'm having a strange internet connection issue - some programs are able to
connect, while others can't seem to find that I have a connection. Those
that can are, for example: IE6, Windows Media Player 10 (features like
internet radio), Windows Automatic Updates, Symantec's Live Update. Those
that can't: Firefox (any version), Thunderbird, Outlook, IE7, and update
check features built in to programs like Adobe Acrobat Reader. Also, I
upgraded from XP Home to Pro because I thought maybe it was Home's limited
network ability that might be causing the problem (I'm on a university
network), and when I had to activate the copy of Pro, the Windows Activation
program couldn't detect that I had a connection.

It doesn't seem to be a firewall issue, as both Windows firewall and
Symantec's firewall being on or off make no difference in what can connect.
While troubleshooting this with the IT guy in our department, he noticed the
Node Type, which you find by using the command "ipconfig /all", was set to
Peer-Peer. Once I figured out how to change that (to Unknown, Broadcast, or
Hybrid), that still made no difference. He set the card to manual
configuration instead of IP being assigned by DHCP, and that made no
difference. I've removed the connection and the card driver, and reinstalled
to no avail. I've even tried a different network card, and the same problems
happen. This has to be the most unusual network problem I've ever
encountered. I use a Dell Dimension 3000, P4 2.8 GHz, with an Intel Pro/100
VE built in NIC. I asked Dell support, and they said basically to reformat
and start fresh. Any ideas other than starting fresh would be greatly
appreciated - thanks!

The Node Type is relevant in local name resolution, and shouldn't have any
effect on Internet services.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

If you're certain that the problem is NOT a firewall (and when you have 2
firewalls, this is always a possibility), look at LSP / Winsock corruption.
Note that this is a repetitive process.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

But if you read thru some other posts in this forum about Norton / Symantec
products, you'll note many advices to follow all detailed instructions from
Symantec, and un install all Symantec components, before further testing. And
there are other possibilities too.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

 

[Guest]

The Node Type is relevant in local name resolution, and shouldn't have any
effect on Internet services.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

If you're certain that the problem is NOT a firewall (and when you have 2
firewalls, this is always a possibility), look at LSP / Winsock corruption.
Note that this is a repetitive process.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

But if you read thru some other posts in this forum about Norton / Symantec
products, you'll note many advices to follow all detailed instructions from
Symantec, and un install all Symantec components, before further testing. And
there are other possibilities too.
<http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html>
http://nitecruzr.blogspot.com/2005/05/your-personal-firewall-can-either-help.html

It did turn out to be something wrong with Symantec's Firewall. I actually
stumbled across it on my own before I read your post. It must've got
corrupted or something, because I couldn't change any settings in it, so I
decided to uninstall and reinstall it. After that, everything that didn't
work started working. Thanks for the reply though!

Matt

 

[Chuck]

It did turn out to be something wrong with Symantec's Firewall. I actually
stumbled across it on my own before I read your post. It must've got
corrupted or something, because I couldn't change any settings in it, so I
decided to uninstall and reinstall it. After that, everything that didn't
work started working. Thanks for the reply though!

Matt

Thanks for the feedback, Matt!