Re: one lonely computer on a peer to peer net
- From: "Chuck [MVP]" <none@xxxxxxxxxxx>
- Date: Tue, 28 Aug 2007 09:52:24 -0700
On Mon, 27 Aug 2007 13:31:27 -0700, fritz <-rem-figure23@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
Chuck [MVP] wrote:
> My pleasure, Fritz.
It's not NetBIOS, though, it's NetBIOS Over TCP (aka NetBT). Don't confuse it
with "NWLink IPX/SPX/NetBIOS Compatible Transport". NetBT depends upon the
TCP/IP NetBIOS Helper service. Check the services, then check again the network
components.
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#Components
Hi,
I decided to go back to the beginning so to speak. On the PChuck page
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html
I started at the top with physical problems.
Computer had the following symptoms:
1. Email and Internet access are not affected. They work fine!
2. Nothing shows up in 'My Network Places' nor does anything show when 'View Workgroup Computers' is clicked
3. Even though 'Enable NetBios over TCP/IP' (NetBT) is checked on the WINS tab a 'ipconfig /all' call shows that it
is 'Disabled'.
4. Pings by IP address go through but pings by host name do not.
A. Physical
The physical network itself is done correctly and all cards, cables, etc have been checked, secured and all
computers are directly connected, on the same LAN segment.
B. Logical
The network driver has been reinstalled from the manufacturer's disk that came with the machine and it's website
checked for any upgrades. It was the latest and only driver.
NetBT. Ensured that 'NetBIOS over TCP/IP' is enabled on the Wins tab of Advanced TCP/IP Settings dialog.
However, when 'ipconfig /all' is called via cmd NetBIOS over TCP/IP is shown as disabled. No amount of fussing,
fooling, or farting could change that. Until, in the 'Logical Network Problems' section I came to 'a corrupt LSP/Winsock
layer' hyperlink. It was there that it was suggested to reset the TCP/IP protocol.
I used the "netsh winsock reset catalog" call and reset. To my astonishment everything was right with the world. And
so I can only thank and thank again Chuck for having a web site that offers guidance and also for answering all those
questions! Chuck, who has the same last name as so many other people I have corresponded with - "MVP". Because I can't
pronounce it I am guessing a Slavic background? ;-)
Here's wishing you eternal sunshine,
Fritz
And we have another case of LSP / Winsock corruption. Cured by the native
"netsh" command. I'm glad that my layered diagnostic technique helped you,
Fritz. Thanks for letting us know. B-)
--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.
- References:
- one lonely computer on a peer to peer net
- From: fritz
- Re: one lonely computer on a peer to peer net
- From: Chuck [MVP]
- Re: one lonely computer on a peer to peer net
- From: fritz
- Re: one lonely computer on a peer to peer net
- From: fritz
- Re: one lonely computer on a peer to peer net
- From: Chuck [MVP]
- Re: one lonely computer on a peer to peer net
- From: fritz
- Re: one lonely computer on a peer to peer net
- From: Chuck [MVP]
- Re: one lonely computer on a peer to peer net
- From: fritz
- Re: one lonely computer on a peer to peer net
- From: Chuck [MVP]
- Re: one lonely computer on a peer to peer net
- From: fritz
- one lonely computer on a peer to peer net
- Prev by Date: Re: Losing XP file access on LAN
- Next by Date: Re: Always get network cable is unplugged message after rebooting computer
- Previous by thread: Re: one lonely computer on a peer to peer net
- Next by thread: Re: one lonely computer on a peer to peer net
- Index(es):
Relevant Pages
|
Loading