Win XP no longer able to access LAN with win 98SE machines

anonymous_at_discussions.microsoft.com
Date: 09/01/04 

Date: Tue, 31 Aug 2004 23:07:08 -0700

only fix I've found so far is to use restore to get rid of
SP2!

>-----Original Message-----
>I cannot use my LAN either after updating XP Home and Pro
>to Service Pack 2. If you find anything to remedy this
>problem, please let me know. My LAN says it is not
>connected or has no connectivity! But, Everything is
>still connected. THANKS! ....Rick
>
>
>
>>-----Original Message-----
>>To any LAN or Networking troubleshooters out there:-
>>
>>Recently (after allowing updates) my Win XP machine no
>longer is able to
>>access shares on my LAN.
>>
>>The LAN has 5 other computers (4 Win 98SE and 1 Win NT
>4.0) machines
>>connected to two Linksys routers (One acting as a
>Gateway for three PCs and
>>the other router which is wireless and acts as a router
>for the other two PC
>>and other wireless components, eg. wireless print
>server).
>>- All machines on the network can successfully 'ping
>each other'
>>- All of the Win 98SE machines and the Win NT 4.0
>machine can accessess each
>>others shares (mapped drives, etc)
>>- The Win XP machine could originally access the other
>machines but it now
>>returns the message " 'Workgroup' is not accessible. You
>might not have
>>access to the Network resource. Contact the
>administrator of this server to
>>findout if you have access permissions"
>>- All machines, including the XP machine, are part of
>the same named workgroup
>>- ICF is disabled on the XP machine
>>- No other firewall software is installed on the XP
>machine. The firewall
>>software on the Win 98SE machines is set to allow the IP
>address of the XP
>>machine
>>- The XP machine has been assigned a Static IP address
>of the type
>>192.168.1.XXX (where xxx is a number within the range
>allowed by the routers)
>>- No network bridges are present on the XP machine.
>Although it has two
>>network adapters (wired and wireless) each has been
>assigned a separate
>>static ip address and one is disabled when the other is
>in use.
>>- The connections have "File and print sharing", "Client
>for Microsoft
>>Networks", Internet Protocol (TCP/IP) and [Qos packet
>scheduler] installed;
>>TCP/IP being configured with static ip addresses and DNS
>entries.
>>
>>Neither LINKSYS, COMPAQ or Microsoft have been
>successful in helping me
>>solve this issue so I would be most interested to hear
>if anyone else has
>>experienced the same problem, namely a machine which
>happily connected to a
>>LAN suddenly experiences the error mentioned above after
>installation of
>>windows xp updates including SP 2.
>>
>>The error is #6118 when "net view" is typed in a command
>window. There is a
>>Microsoft "Q" *** which suggest that if the XP machine
>was connected to a
>>Domain which has the same nam as the work group the
>error described at the
>>top of this post could occur. I tried changing the name
>of the workgroup for
>>all of the network components and rebooting the LAN and
>Broadband connection
>>but the problem still persists.
>>
>>I hope someone has the time to read this (sorry about
>the length, tried to
>>be through) and make a wise suggestion.
>>
>>Thanks,
>>
>>Dave Robinson
>>
>>ps - I tried booting up different machines in sequence
>to allow different
>>machines to hold the master browser list but that only
>caused a delay in how
>>long it took before all the machines could see each
>other. The XP machine
>>still wouldn't access the shares of the other machines
>or allow them to acces
>>its shares; sometimes the XP machine would not even see
>the other machines
>>but it could still ping them and they could ping it.
>>.
>>
>.
>