A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows XP » Networking and the Internet with Windows XP
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Home Network: Comp A can access CompB, but CompB doesnt see CompA



 
 
Thread Tools Display Modes
  #16  
Old November 22nd 04, 04:19 AM
tanker
external usenet poster
 
Posts: n/a
Default where the FAQ?


-----------------------------------------
ÔÚ £¬Ð´µÀ£º

-----------------------------------------

Ö Àñ£¡
tanker


Ads
  #17  
Old November 26th 04, 03:11 AM
No_Name
external usenet poster
 
Posts: n/a
Default Paging Chuck

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

On Mon, 22 Nov 2004 03:15:54 GMT, DK wrote:

Chuck, I "flipped" Computer Browser Service - disabled it on A and
enabled it on B:

Here are results:

comp A browstat:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKcd..

C:\Documents and Settingsbrowstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52A8-0FE7-461D-83C
5-916105A611F7}
Browsing is active on domain.
Master browser name is: PIII800MHZ
Could not open key in registry, error = 53 Unable to determine
build of br
owser master: 53
\\\\PIII800MHZ . Version:05.01 Flags: 51003 NT POTENTIAL
MASTER
1 backup servers retrieved from master PIII800MHZ
\\PIII800MHZ
There are 2 servers in domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52
A8-0FE7-461D-83C5-916105A611F7}
There are 1 domains in domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52
A8-0FE7-461D-83C5-916105A611F7}

C:\Documents and Settings

Comp B browstat:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\browstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B
3-0236FD4ECCE4}
Browsing is active on domain.
Master browser name is: PIII800MHZ
Master browser is running build 2600
1 backup servers retrieved from master PIII800MHZ
\\PIII800MHZ
There are 2 servers in domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7E
DB-B177-4F6C-88B3-0236FD4ECCE4}
There are 1 domains in domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7E
DB-B177-4F6C-88B3-0236FD4ECCE4}

Still I can not connect to A shares from B computer


On 21 Nov 2004 20:11:06 -0600, Chuck wrote:

On Sun, 21 Nov 2004 22:56:37 GMT, *email_address_deleted* wrote:


SNIP

Once again - from A to B I have no problems - ping works both on IP
and hostname; I can see shares and operate with files in them.

From B to A - i can ping A by IP and hostname, but now I keep getting
message "Workgroup 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."

On Both:

WinXP Pro with SP2
Simple File Sharing is enabled
Computer Browsing service is enabled
Same user ID and passwords are established.
Windows Firewall is disabled on Local Area connections

NETSTAT on B shows:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKnetstat

Active Connections

Proto Local Address Foreign Address State
TCP piii800mhz:netbios-ssn 192.168.1.100:3166 ESTABLISHED

NET VIEW from B returns an error:

"System error 121 occurred - the semaphore timeout period ahs expired"

\\piv24ghz from B shows error message "Server PIV24GHZ is not
accessible"

I has ZoneAlarm installed on Comp A - have removed it completely and
tried troubleshooting without it - made NO difference - I do not
believe that ZA is interfering in any way.

Thanks.



ICQ 6124479
dimdur at ureach dot com
  #18  
Old November 26th 04, 08:41 AM
Chuck
external usenet poster
 
Posts: n/a
Default Paging Chuck

On Fri, 26 Nov 2004 02:11:34 GMT, wrote:

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 time1ms 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?

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
  #19  
Old November 26th 04, 09:12 PM
No_Name
external usenet poster
 
Posts: n/a
Default Paging Chuck - network.jpg (0/1)

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.



On 26 Nov 2004 01:41:10 -0600, Chuck wrote:

On Fri, 26 Nov 2004 02:11:34 GMT, wrote:

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 time1ms 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
  #20  
Old November 26th 04, 09:13 PM
No_Name
external usenet poster
 
Posts: n/a
Default Paging Chuck - network.jpg (1/1)



Attached Images
File Type: jpg network.jpg (41.8 KB, 55 views)
  #21  
Old November 27th 04, 12:26 AM
Chuck
external usenet poster
 
Posts: n/a
Default Paging Chuck - network.jpg (0/1)

On Fri, 26 Nov 2004 20:12:59 GMT, *email_address_deleted* wrote:

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.


Dmitri,

The browser subsystem provides a list of servers, without worrying about the
addresses of those servers. If CompA has an ip address that changes, and its
name resolves to a non-existent ip address, your problems with browstat, or in
accessing shares displayed in Network Neighborhood, are a normal result.

Please provide browstat and ipconfig information for CompA, CompB, and for the
Win2K laptop. Any effective diagnosis of your problem has to be made with
accurate data.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
  #22  
Old November 28th 04, 07:10 AM
Carey Holzman
external usenet poster
 
Posts: n/a
Default Paging Chuck - network.jpg (0/1)

On the XP machines, click Start, click Run, type REGEDIT (hit enter)

Go to the following reg key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\LSA

Look for "RestrictAnonymous" and ensure it is set to 0.

Reboot for changes to take affect

Carey

wrote in message
news
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.



On 26 Nov 2004 01:41:10 -0600, Chuck wrote:

On Fri, 26 Nov 2004 02:11:34 GMT, wrote:

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 time1ms 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



  #23  
Old November 30th 04, 04:01 AM
Dmitri
external usenet poster
 
Posts: n/a
Default Paging Chuck - network.jpg (0/1)

Chuck - Comp A NEVER changes IP - it is always ON .
Comp B is on sometimes - and I would like to share printers attached to A to
use them when B is on - this has been the culprit all along.

There is something on A that precludes B from accessing it.

Today I am able to access my workgroup and B "sees" A again but can not
access shares on A.

It is very interesting to mention that BROWSTAT on A now sees И as Master
Browser:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKbrowstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52A8-0FE7-461D-83C
5-916105A611F7}
Browsing is active on domain.
Master browser name is: PIII800MHZ
Could not open key in registry, error = 5 Unable to determine build
of br
owser master: 5
\\\\PIII800MHZ . Version:05.01 Flags: 51003 NT POTENTIAL MASTER
1 backup servers retrieved from master PIII800MHZ
\\PIII800MHZ
There are 2 servers in domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52
A8-0FE7-461D-83C5-916105A611F7}
There are 1 domains in domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52
A8-0FE7-461D-83C5-916105A611F7}

C:\Documents and Settings\DK

Computer Browser Service is running on Both now. If I turn it off on B - B
can not access Workgroup; when it is ON on B - B "sees" workgroup and A -
but can not access resources on A.

Here is BROWSTAT result from B (as of today - 11/29):

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


C:\Documents and Settings\DKbrowstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B
3-0236FD4ECCE4}
Browsing is active on domain.
Master browser name is: PIII800MHZ
Master browser is running build 2600
1 backup servers retrieved from master PIII800MHZ
\\PIII800MHZ
There are 2 servers in domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7E
DB-B177-4F6C-88B3-0236FD4ECCE4}
There are 1 domains in domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7E
DB-B177-4F6C-88B3-0236FD4ECCE4}

C:\Documents and Settings\DK

On 11/25 (with Comp. Browser Service off) I was getting:

C:\browstat dn

List of transports currently bound to the browser

1 \Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B3-0236FD4ECCE4}

C:\browstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B
3-0236FD4ECCE4}
Browsing is active on domain.
Master browser name is: PIV24GHZ
Could not connect to registry, error = 53 Unable to determine build
of br
owser master: 53
Unable to determine server information for browser master: 64
1 backup servers retrieved from master PIV24GHZ
\\PIV24GHZ
Unable to retrieve server list from PIV24GHZ: 53

Here is IPCONFIG for A:


C:\Documents and Settings\DKipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : pIV24ghz
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
Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-50-8D-E1-22-9B
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 167.206.3.232
167.206.3.231
167.206.3.166
Lease Obtained. . . . . . . . . . : Monday, November 29, 2004
2:00:16 PM

Lease Expires . . . . . . . . . . : Tuesday, November 30, 2004
2:00:16 P
M

C:\Documents and Settings\DK

Here is IPCONFIG for B:


C:\Documents and Settings\DKipconfig /all

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
Ethe
rnet NIC
Physical Address. . . . . . . . . : 00-40-F4-33-6B-A8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 167.206.3.232
167.206.3.231
167.206.3.166
Lease Obtained. . . . . . . . . . : Monday, November 29, 2004
8:42:46 PM

Lease Expires . . . . . . . . . . : Tuesday, November 30, 2004
8:42:46 P
M

C:\Documents and Settings\DK

Here is CDIAG for A:

CDiagnosis V1.05
Start diagnosis for PIV24GHZ (Targets pIV24ghz 192.168.1.100 piii800mhz
192.168.1.101)

Target pIV24ghz

"ping pIV24ghz"



Pinging pIV24ghz [192.168.1.100] with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view pIV24ghz"

Shared resources at pIV24ghz

Main Unit

Share name Type Used as Comment


-------------------------------------------------------------------------------
Canon Print Canon i470D

D Disk

EPSON860 Print EPSON Stylus COLOR 860

H Disk

Printer Print Print to this device to send a photo quality
fax.
Printer10 Print BroadGun pdfMachine

Printer11 Print Creates Adobe PDF

Printer2 Print Print to this device to send a fax.

Printer3 Print SnagIt 7

Printer4 Print Okidata OL-600e

Printer5 Print Microsoft Office Document Image Writer

Printer6 Print Fax via eFax

Printer7 Print Epson Stylus COLOR 860 ESC/P 2

SharedDocs Disk

Storage (I) Disk

The command completed successfully.


Target 192.168.1.100

"ping 192.168.1.100"



Pinging 192.168.1.100 with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 192.168.1.100"


Target piii800mhz

"ping piii800mhz"



Pinging piii800mhz [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view piii800mhz"

Shared resources at piii800mhz

TWO

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
D Disk (UNC)
SharedDocs Disk
The command completed successfully.


Target 192.168.1.101

"ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 192.168.1.101"

Shared resources at 192.168.1.101

TWO

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
D Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms 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


"net view 127.0.0.1"

Shared resources at 127.0.0.1

Main Unit

Share name Type Used as Comment


-------------------------------------------------------------------------------
Canon Print Canon i470D

D Disk

EPSON860 Print EPSON Stylus COLOR 860

H Disk

Printer Print Print to this device to send a photo quality
fax.
Printer10 Print BroadGun pdfMachine

Printer11 Print Creates Adobe PDF

Printer2 Print Print to this device to send a fax.

Printer3 Print SnagIt 7

Printer4 Print Okidata OL-600e

Printer5 Print Microsoft Office Document Image Writer

Printer6 Print Fax via eFax

Printer7 Print Epson Stylus COLOR 860 ESC/P 2

SharedDocs Disk

Storage (I) Disk

The command completed successfully.


Target 192.168.1.1

"ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 192.168.1.1"

End diagnosis for PIV24GHZ


Here is CDIAG from B:

CDiagnosis V1.05
Start diagnosis for PIII800MHZ (Targets pIV24ghz 192.168.1.100 piii800mhz
192.168.1.101)

Target pIV24ghz

"ping pIV24ghz"



Pinging pIV24ghz [192.168.1.100] with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view pIV24ghz"


Target 192.168.1.100

"ping 192.168.1.100"



Pinging 192.168.1.100 with 32 bytes of data:



Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128

Reply from 192.168.1.100: bytes=32 time1ms TTL=128



Ping statistics for 192.168.1.100:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 192.168.1.100"


Target piii800mhz

"ping piii800mhz"



Pinging piii800mhz [192.168.1.101] with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view piii800mhz"

Shared resources at piii800mhz

TWO

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
D Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.1.101

"ping 192.168.1.101"



Pinging 192.168.1.101 with 32 bytes of data:



Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128

Reply from 192.168.1.101: bytes=32 time1ms TTL=128



Ping statistics for 192.168.1.101:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 192.168.1.101"

Shared resources at 192.168.1.101

TWO

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
D Disk
SharedDocs Disk
The command completed successfully.


Target 127.0.0.1

"ping 127.0.0.1"



Pinging 127.0.0.1 with 32 bytes of data:



Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms TTL=128

Reply from 127.0.0.1: bytes=32 time1ms 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


"net view 127.0.0.1"

Shared resources at 127.0.0.1

TWO

Share name Type Used as Comment

-------------------------------------------------------------------------------
C Disk
D Disk
SharedDocs Disk
The command completed successfully.


Target 192.168.1.1

"ping 192.168.1.1"



Pinging 192.168.1.1 with 32 bytes of data:



Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150

Reply from 192.168.1.1: bytes=32 time1ms TTL=150



Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms


"net view 192.168.1.1"

End diagnosis for PIII800MHZ


Win2K notebook is from work and most of the time does not participate on the
network that much.

Thanks

Dmitri

Corey,

I looked at your suggestion and value is already 0 - thanks


"Chuck" wrote:

On Fri, 26 Nov 2004 20:12:59 GMT, *email_address_deleted* wrote:

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.


Dmitri,

The browser subsystem provides a list of servers, without worrying about the
addresses of those servers. If CompA has an ip address that changes, and its
name resolves to a non-existent ip address, your problems with browstat, or in
accessing shares displayed in Network Neighborhood, are a normal result.

Please provide browstat and ipconfig information for CompA, CompB, and for the
Win2K laptop. Any effective diagnosis of your problem has to be made with
accurate data.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.

  #24  
Old November 30th 04, 07:07 AM
Chuck
external usenet poster
 
Posts: n/a
Default Paging Chuck - network.jpg (0/1)

On Mon, 29 Nov 2004 19:01:02 -0800, Dmitri
wrote:

Chuck - Comp A NEVER changes IP - it is always ON .
Comp B is on sometimes - and I would like to share printers attached to A to
use them when B is on - this has been the culprit all along.

There is something on A that precludes B from accessing it.

Today I am able to access my workgroup and B "sees" A again but can not
access shares on A.

It is very interesting to mention that BROWSTAT on A now sees ? as Master
Browser:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\DKbrowstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52A8-0FE7-461D-83C
5-916105A611F7}
Browsing is active on domain.
Master browser name is: PIII800MHZ
Could not open key in registry, error = 5 Unable to determine build
of br
owser master: 5
\\\\PIII800MHZ . Version:05.01 Flags: 51003 NT POTENTIAL MASTER
1 backup servers retrieved from master PIII800MHZ
\\PIII800MHZ
There are 2 servers in domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52
A8-0FE7-461D-83C5-916105A611F7}
There are 1 domains in domain GSA02 on transport
\Device\NetBT_Tcpip_{B47C52
A8-0FE7-461D-83C5-916105A611F7}

C:\Documents and Settings\DK

Computer Browser Service is running on Both now. If I turn it off on B - B
can not access Workgroup; when it is ON on B - B "sees" workgroup and A -
but can not access resources on A.

Here is BROWSTAT result from B (as of today - 11/29):

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


C:\Documents and Settings\DKbrowstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B
3-0236FD4ECCE4}
Browsing is active on domain.
Master browser name is: PIII800MHZ
Master browser is running build 2600
1 backup servers retrieved from master PIII800MHZ
\\PIII800MHZ
There are 2 servers in domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7E
DB-B177-4F6C-88B3-0236FD4ECCE4}
There are 1 domains in domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7E
DB-B177-4F6C-88B3-0236FD4ECCE4}

C:\Documents and Settings\DK

On 11/25 (with Comp. Browser Service off) I was getting:

C:\browstat dn

List of transports currently bound to the browser

1 \Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B3-0236FD4ECCE4}

C:\browstat status


Status for domain GSA02 on transport
\Device\NetBT_Tcpip_{021D7EDB-B177-4F6C-88B
3-0236FD4ECCE4}
Browsing is active on domain.
Master browser name is: PIV24GHZ
Could not connect to registry, error = 53 Unable to determine build
of br
owser master: 53
Unable to determine server information for browser master: 64
1 backup servers retrieved from master PIV24GHZ
\\PIV24GHZ
Unable to retrieve server list from PIV24GHZ: 53


Dmitri,

OK, trying to absorb the clues that you're providing is a real trip. So many
interesting things to consider.

You ran browstat once from Computer A (pIV24ghz), and twice from Computer B
(piii800mhz). You say that the browser service is running on both computers,
but no browstat reflects that. Browstat #1 (from pIV24ghz) shows the master
browser as PIII800MHZ. Browstat #2 (11/29 from PIII800MHZ) again shows the
master browser as PIII800MHZ.

However, browstat #3 (11/25 from PIII800MHZ) shows the master browser as
PIV24GHZ.

What changes did you make between 11/25 and 11/29? When did you turn the
browser off on PIII800MHZ? When did you turn it on again?

Remember that simply turning the browser off or on isn't enough. If you read
the long Browser reference document, you should know that changing the status of
the browser on any given computer may not be noticed by the computers in the
workgroup, unless you restart each computer (forcing each computer to ask what
computer is the master browser?).

Has Computer C (the laptop) been connected to the network at any time during
your experimentations?

If you turn the browser service off, on a computer that's not the master
browser, that may not be noticed. If you turn the browser service off, on a
computer that is the master browser, that should be noticed, but possibly as
much as 52 minutes later. In either case, running browstat could produce
unpredictable results.

Remember that with a single computer on the network, the browser service is not
needed. With two computers on the network, having the browser service running
on just one is sufficient. With three computers on the network, having two
computers with the browser service running is a good idea (if the one computer
running the browser service goes offline, one of the other two computers will
need to have the service running).

When making changes to the browser setup on your LAN (turning browser service
off or on), for consistency, please follow these steps:
1) Make change (turn service off or on as appropriate).
2) Power every computer off.
3) Power the computer on that you intend to use as the master browser, first.
4) Power other computers on.

Now to the errors observed by browstat. Note that "Error = 5" is a permissions
error, and "Error = 53" is a not found (cannot resolve name) error. A name
resolution problem generally has one of two causes - either incorrect node type
(Peer-Peer or WINS), or a connectivity problem, probably caused by a rogue
firewall. Both computers have "Unknown" node type, which is normal. Both of my
WinXP computers have Node Type = Unknown, and my LAN works fine with all 3 of my
computers.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
2 home computers XP Pro on comp. and Home Ed. on other? Tiger General XP issues or comments 4 July 25th 04 08:00 PM
2 home computers XP Pro on comp. and Home Ed. on other? Tiger General XP issues or comments 4 July 25th 04 04:48 PM
2 home computers XP Pro on comp. and Home Ed. on other? Tiger General XP issues or comments 4 July 25th 04 10:21 AM
2 home computers XP Pro on comp. and Home Ed. on other? Tiger General XP issues or comments 4 July 25th 04 08:33 AM
2 home computers XP Pro on comp. and Home Ed. on other? Tiger General XP issues or comments 4 July 25th 04 06:20 AM






All times are GMT +1. The time now is 07:59 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.