C
Carey Holzman
On the XP machines, click Start, click Run, type REGEDIT (hit enter)
Go to the following reg key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
Look for "RestrictAnonymous" and ensure it is set to 0.
Reboot for changes to take affect
Carey
Go to the following reg key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
Look for "RestrictAnonymous" and ensure it is set to 0.
Reboot for changes to take affect
Carey
Chuck,
IP Address indeed changed once I rebooted PC.
I am attaching a diagram of my network as it stands right now.
I can not access workgroup from either Comp B or from the laptop -
Workgroup not accessible.
I keep getting System error 121 or 53 when running browstat status on
either of the two.
They just do not see Comp A.
I can ping all three by their IPs of Hostnames.
Chuck
I have not heard from you since I last posted.
My status has not changed - Comp B can not see Comp A - I get error
message that "workgroup is not accessible"
I can ping each other by IP and hostname - but nothing more.
Also BROWSTAT on B now tells me it is unable to connect to registry,
error 53 unable to determine build of browser master: 53.
Browsing service on È is disabled. It does see A as master browser.
Thanks
Dmitri,
You have a name resolution problem.
IPConfig for piii800mhz (which you provided earlier):
Windows IP Configuration
Host Name . . . . . . . . . . . . : piii800mhz
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast
Ethernet NIC
Physical Address. . . . . . . . . : 00-40-F4-33-6B-A8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.102
OK, when I setup CDiag, I used 192.168.1.102 for the address of
piii800mhz.
Yet, when we ping piii800mhz by name, from both computers, we get:
Pinging piii800mhz [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time<1ms TTL=128
And, when we ping 192.168.1.102, we get:
Pinging 192.168.1.102 with 32 bytes of data:
Request timed out.
Name resolution problems can also result in errors about browser registry
access, and in apparent permission problems when trying to open shares.
Is it possible that, when you rebooted piii800mhz, it got a new IP
address?
What does IPConfig for piii800mhz show right now?
Also, please identify version of WinXP on each computer - Home or Pro?
ICQ 6124479
dimdur at ureach dot com