WAN subnet not accessible

  • Thread starter Thread starter kr
  • Start date Start date
K

kr

the problem subnet has 5 win 2k pc's and one Unix server. the Network
consists of an NT PDC, 2003 DNS, 2000 Wins. the entire subnet does not
appear in NetHood, and is not accessible by name. It is accessible by IP.

Ipconfigured correctly and host files are not in use. the Subnet is
routed with a Cisco 1760, ip adresses are static.

the result of browstat view for all pc's on the Sub:

D:\>browstat view
\Device\NetBT_Tcpip_{5B541357-***-****-****-35DE4F5B50EC}
\\192.168.0.1 Remoting NetServerEnum to \\192.168.0.1 on transport
\Device\NetBT_Tcpip_{5B541357-***-****-****-35DE4F5B50EC} with flags
ffffffff Unable to remote API to \\192.168.0.1 on transport
\Device\NetBT_Tcpip_{5B541357-0ED0-4ECA-B125-35DE4F5B50EC}: No more
connections can be made to this remote computer at this time because there
are already as many connections as the computer can accept. (40
milliseconds)
 
the problem subnet has 5 win 2k pc's and one Unix server. the
Network consists of an NT PDC, 2003 DNS, 2000 Wins. the entire
subnet does not appear in NetHood, and is not accessible by name.
It is accessible by IP.

Ipconfigured correctly and host files are not in use. the Subnet
is routed with a Cisco 1760, ip adresses are static.

the result of browstat view for all pc's on the Sub:

D:\>browstat view
\Device\NetBT_Tcpip_{5B541357-***-****-****-35DE4F5B50EC}
\\192.168.0.1 Remoting NetServerEnum to \\192.168.0.1 on transport
\Device\NetBT_Tcpip_{5B541357-***-****-****-35DE4F5B50EC} with
flags ffffffff Unable to remote API to \\192.168.0.1 on transport
\Device\NetBT_Tcpip_{5B541357-0ED0-4ECA-B125-35DE4F5B50EC}: No
more connections can be made to this remote computer at this time
because there are already as many connections as the computer can
accept. (40 milliseconds)
Click to expand...

I see this result when the computer thinks it is querying the browse
master and it turns out that the machine it thinks is the browse master
really isn't. Try doing a "browstat status" before the "browstat
view" and verify that an active browse master is identified on the
subnet. Then do a "netstat -a <browse master>" and verify that the
identified master browser thinks it really is a master browser by
looking for a "__MSBROWSE__" line in the results.

HTH,
John
 
I see this result when the computer thinks it is querying the browse
master and it turns out that the machine it thinks is the browse master
really isn't. Try doing a "browstat status" before the "browstat
view" and verify that an active browse master is identified on the
subnet. Then do a "netstat -a <browse master>" and verify that the
identified master browser thinks it really is a master browser by
looking for a "__MSBROWSE__" line in the results.

HTH,
John
Click to expand...
hey John, thanks for your time, I am guessing you meant "nbtstat -A
<remote machine>"?? and yes, my PDC returns as the master. I suspect the
problem is related to what you mention, but release renew does not help
and the remote machines all have the proper browser settings in the
registry. I have another node that displays this behavior as well, and
the common thread between the two is a Unix box. I will explore this
next...
 
hey John, thanks for your time, I am guessing you meant "nbtstat
-A <remote machine>"?? and yes, my PDC returns as the master.
Click to expand...

Yes. I stand corrected with nbtstat. This is a strange one... a PDC
that doesn't accept connections... I'm clueless.

-- John
 
Back
Top