Re: Workgroup computers not visible, shares not available.

On Fri, 30 Dec 2005 19:33:02 -0800, "Denis" <Denis@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

>My network:
>
>Newworkstation ? running windows XP Pro
>
>Videoeditor ? running windows XP Pro
>
>Filestore ? running windows 98 SE
>
>Vader ? print server and workstation running windows XP Pro
>
>Burner ? workstation running windows XP Pro
>
>Laptop 1 - running windows XP Pro
>
>Laptop 2 - running windows XP Pro
>
>Graphicedit ? Mac OS 9.2
>
>
>It is not a complicated problem every computer on the network can see every
>other computer except Newworkstation which does not show any computer on the
>workgroup except itself. It takes forever to even look for a computer when I
>go ?Start? ?Run? and type in the IP address of the computer I want to connect
>to. I will see the computer when I do this but will not necessarily connect
>to the computer. It will connect to folder shares on some but not all of the
>other computers. On the computers to which it will not connect I get the same
>message:
>
>\COMPUTERNAMESharedDocs is not accessible. You might not have permission to
>use this network resource. Contact the administrator of this server to find
>out if you have access permissions.
>
>Access is denied
>
>Alternatively I have also received the same message as above but with the tag:
>
>No network provider accepted th given network path.
>
>In the registry I edited the following
>
>HKLM/System/Services/NetBT and added DWORD NodeType with Binary set to 8 ?
>I recently tried setting it to 4.
>
>To answer the inevitable questions: Yes all computers are part of the same
>workgroup. Yes all computers other than Newworkstation show all computers on
>the network in the workgroup view. All shares are accessible from other
>machines and writeable. Only the new machine Newworkstation is having this
>issue. Yes Computer Browser is turned on in services and it is set to
>automatic. Yes I have added IPX/SPX and configured it for networking on all
>machines. Yes NetBIOS over TCP/IP is configured correctly. Yes Windows
>Firewall is turned off. Yes ZoneAlarm trusted zone is configured correctly.
>I?ve been doing this kind of thing for a while and am really stumped.
>
>All to no avail. Any help would be appreciated.
>
>
>Denis
>*email_address_deleted*

Denis,

What protocols do you truly need? Your slow name resolution is symptomatic of
excess transports, so the name resolution datagrams have to travel thru 2 or
more protocols, 1 at a time. All you really should need is NBT. Seriously.
<http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html>
http://nitecruzr.blogspot.com/2005/05/fix-network-problems-but-clean-up.html

Now, a node type = 4 is Mixed, and an 8 is Hybrid. Both use the same resolution
techniques, but reverse the order.
<http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html>
http://nitecruzr.blogspot.com/2005/05/address-resolution-on-lan.html

I've also advised people with your symptoms, and the end diagnosis has been LSP
/ Winsock corruption. This is not the shortest diagnostic / repair you can run.
<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

What I'd advise you to do first is slow down, and make one change at a time. I
get a headache trying to read your report (I can't imagine you feel any better).
<http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html>
http://nitecruzr.blogspot.com/2005/08/solving-network-problems-tutorial.html

If you provide "browstat status" and "ipconfig /all" from the problem computer,
and from any TWO of the properly working XP computers (your choice), we can
start to diagnose the problem. Read this article, and linked articles, and
follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp

--
Cheers,
Chuck, MS-MVP [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.
.

Relevant Pages

  • iPAQ5450 not recognising Home Network
    ... with a cable connection to a D-Link wireless router. ... A laptop running Windows XP Pro is wirelessly connected through a D-Link ... This part of the network works without any problems. ...
    (microsoft.public.pocketpc.wireless)
  • Re: Network - one computer cant access files in the other
    ... I have set up 2 computers via a wireless network ... >; both running windows XP, ... Are you running XP Home, XP Pro, a combination? ... Guest account is enabled, on each computer. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Disabling CDW
    ... Follow up question Jim re:thumb drive ... How can I disable it also to all my users in network? ... I'm using Windows XP Pro and I'm running Windows 2000 AD Domain. ...
    (microsoft.public.windowsxp.hardware)
  • Sharing files on wireless network with domains and workgroups
    ... I have 2 desktop PC's that I have hooked up to a wireless network, ... running Windows XP pro and one running Windows XP home using Linksys PCI ... notebook PC which has Windows XP pro on it connected to this network but it ...
    (microsoft.public.windowsxp.general)
  • Re: Network Neighborhood
    ... > inability to browse by using Network Neighborhood in Windows 95 or Windows ... > communicated effectively with the other workgroup computers. ... > not have a common networking protocol, a common workgroup, and common user ... the computer that is running Windows ...
    (microsoft.public.win2000.networking)