Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

Failure to browse in XP HOME network since SP3 + updates

0 views

Skip to first unread message

tonydave

unread,

Nov 11, 2009, 10:00:01 PM11/11/09

For some time I have been having problems with browsing the network at home.
At all times I have been able to make file sharing work by using absolute
addressing in explorer (entering say \\192.168.0.51 in the address bar) and
then navigating the shared file system. All the computers have at least 1
common account name and password to make this work. What doesn't work is
trying to view the workgroup in explorer. I have been using XP since it was
released until about a year ago without problems on up to 8 PC's.

I have spent many hours reading about the problem including some very useful
time on PChucks Network. However it seems that all the solutions work
everywhere except on XP Home SP3.

This came to a point 2 weeks ago when I had to rebuild a machine and my only
usable install disk is SP2. That machine as browse-master and the network
sang again!!! I thought great and ran checks before letting Microsoft update
at it for 12 hours (yes 12 hours to run all the updates), at which point the
network died - OK it just went back to its previous state - limping along.

So SP2 networking XP Home OK, SP3 networking XP Home busted. Well to be
more accurate I do not know exactly when it broke, I have reason to think
that it may have been during the updates.

The reason. 2 months ago I bought my son a Netbook running XP3 and while
running the updates one of them broke wireless networking, so I wired it and
a later update fixed wireless networking.

OK. That has set the scenario now down to the tests and any other details.
Please believe me when I say that I have diligently tried all the fixes as
detailed by PChuck and elsewhere - while doing this I accidentally "broke"
the machine which was rebuilt above. Firewall - Sunbelt Kerio, this has been
switched off uninstalled disabled and had all rules opened up. Windows
firewall switched off and on and checked that the workgroup ports were not
blocked even when switched off (posted on MSN). Network includes wireless,
but this problem persists when machines are just connected with a switch,
besides which the router has been the same for 4 years.

BROWSTAT
Status for domain YATESNET on transport
\Device\NetBT_Tcpip_{591B0C6E-50E9-4903-AF2C-A57683259FF8}
Browsing is NOT active on domain.
Master browser name is held by: TONYACERCOMP
Master browser is running build 2600

This is the nub of the problem, this command was executed on TonyAcerComp
and the result is the same on any machine that holds master browser status.

I ran
ntrights +r SeNetworkLogonRight -u Guest
ntrights -r SeDenyNetworkLogonRight -u Guest
ntrights +r SeNetworkLogonRight -u Everyone
ntrights -r SeDenyNetworkLogonRight -u Everyone

NB. to PChuck the -g on your site for Everyone gives an error from NTRIGHTS
which indicates that -u applies to user or groupname.

It made no difference. All the services I have seen referenced are running.

On the SP2 machine disconnected from the network BROWSTAT indicated an
active browser with expected results - 1 server exactly the same as an XP pro
SP3 machine I have access to.

To keep it simple. A computer should be able to browse itself when
disconnected from the network.

So my problem is HOW TO FIX THE WORKGROUP BROWSER ON XP HOME.

Although I also have Vista and now Windows 7 machines the XP Home machines
are not going away any time soon and can easily become BrowseMaster and screw
the network.

Just for fun here is PChucks CDIAG.CMD slightly modified to pipe the errors
to the text file - "net share >>c:\cdiag.txt" becomes "net share
>>c:\cdiag.txt 2>&1" where the 2>&1 pipes standard error to the standard
output. So here is the command run just for one machine powered up on the
network.

CDiagnosis V1.40
Start diagnosis for TONYACERCOMP
Full Targets TonyAcerComp 192.168.0.51 127.0.0.1
Ping Targets www.yahoo.com 66.94.230.32 192.168.0.1

Over All Analysis

Enumerate Shares

Share name Resource Remark
-------------------------------------------------------------------------------
print$ C:\WINDOWS\system32\spool\drivers
Printer Drivers

IPC$ Remote IPC

AcerDVD V:\
SharedDocs C:\DOCUMENTS AND SETTINGS\ALL USERS\DOCUMENTS
TonyData (M) M:\
TonyStore S:\
Printer Send To Microsoft OneN Spooled Send To OneNote 2007

Printer3 XPSPort: Spooled Microsoft XPS Document Writer

Printer4 USB001 Spooled Canon iP4300

Printer5 Microsoft Document Ima Spooled Microsoft Office Document Image
Wr
The command completed successfully.

Adhoc Browser View

System error 6118 has occurred.

The list of servers for this workgroup is not currently available

Full Targets Analysis TonyAcerComp 192.168.0.51 127.0.0.1

Target TonyAcerComp

"TONYACERCOMP ping TonyAcerComp"

Pinging tonyacercomp [::1] with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Ping statistics for ::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TONYACERCOMP net view TonyAcerComp"

Shared resources at TonyAcerComp

Tony's Acer Aspire T120E
Share name Type Used as Comment
-------------------------------------------------------------------------------
AcerDVD Disk
Printer Print Send To OneNote 2007
Printer3 Print Microsoft XPS Document Writer
Printer4 Print Canon iP4300
Printer5 Print Microsoft Office Document Image Writer
SharedDocs Disk
TonyData (M) Disk
TonyStore Disk
The command completed successfully.

Target 192.168.0.51

"TONYACERCOMP ping 192.168.0.51"
Pinging 192.168.0.51 with 32 bytes of data:
Reply from 192.168.0.51: bytes=32 time<1ms TTL=128
Reply from 192.168.0.51: bytes=32 time<1ms TTL=128
Reply from 192.168.0.51: bytes=32 time<1ms TTL=128
Reply from 192.168.0.51: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.51:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TONYACERCOMP net view 192.168.0.51"

Shared resources at 192.168.0.51

Target 127.0.0.1

"TONYACERCOMP ping 127.0.0.1"
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

"TONYACERCOMP net view 127.0.0.1"

Shared resources at 127.0.0.1

Ping Targets Analysis www.yahoo.com 66.94.230.32 192.168.0.1
Target www.yahoo.com
"TONYACERCOMP ping www.yahoo.com"
Pinging www-real.wa1.b.yahoo.com [87.248.113.14] with 32 bytes of data:
Reply from 87.248.113.14: bytes=32 time=39ms TTL=55
Reply from 87.248.113.14: bytes=32 time=38ms TTL=55
Reply from 87.248.113.14: bytes=32 time=61ms TTL=55
Reply from 87.248.113.14: bytes=32 time=36ms TTL=55
Ping statistics for 87.248.113.14:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 61ms, Average = 43ms

Target 66.94.230.32
"TONYACERCOMP ping 66.94.230.32"
Pinging 66.94.230.32 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 66.94.230.32:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Target 192.168.0.1
"TONYACERCOMP ping 192.168.0.1"
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

End diagnosis for TONYACERCOMP

Sorry this is a long post but I have tried to be thorough. I may have
missed something simple, but there does seem to be something else or why
should I be seeing this problem over such a wide range of machines?
Including several colleagues, members of a local computer club, and a new
machine. The common denominator being fully patched and updated XP Home.

0 new messages