net view shows "no entries in list" via name but works via IP

[johndog]

When my broadband hub hangs and requires a reset, I find that peer-to-peer
netbios connectivity dies and has a very hard time being reactivated. It
appears that netbios just loses touch.

(Client: XP SP2; Host: Server 2k3 SP1)


Here are the commands I run:

1) First, the command I expect to work:

net view \\bobox

There are no entries in the list.

2) Okay, that's weird, I know there are shares. Let's check using the IP:

net view \\192.168.2.2

Shared resources at \\192.168.2.2

Share name Type Used as Comment

-------------------------------------------------------------------------------
bin Disk
c-drive Disk
d-drive Disk
LexmarkX Print Lexmark X125
Share Disk
The command completed successfully.

3) Really! Those are the shares I was looking for... Maybe the bobox net
bios name is using the wrong IP address?

nbtstat -c

Local Area Connection 2:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Wireless Network Connection:
Node IpAddress: [192.168.2.254] Scope Id: []

NetBIOS Remote Cache Name Table

Name Type Host Address Life [sec]
------------------------------------------------------------
BOBOX <03> UNIQUE 192.168.2.2 -1
BOBOX <00> UNIQUE 192.168.2.2 -1
BOBOX <20> UNIQUE 192.168.2.2 -1

Ok, now how is this possible???? Both ping and nbtstat show that name
resolution is working! nbtstat -R and -RR have no effect either.

Any ideas appreciated...
John

 

[Chuck]

When my broadband hub hangs and requires a reset, I find that peer-to-peer
netbios connectivity dies and has a very hard time being reactivated. It
appears that netbios just loses touch.

(Client: XP SP2; Host: Server 2k3 SP1)


Here are the commands I run:

1) First, the command I expect to work:

net view \\bobox

There are no entries in the list.

2) Okay, that's weird, I know there are shares. Let's check using the IP:

net view \\192.168.2.2

Shared resources at \\192.168.2.2

Share name Type Used as Comment

-------------------------------------------------------------------------------
bin Disk
c-drive Disk
d-drive Disk
LexmarkX Print Lexmark X125
Share Disk
The command completed successfully.

3) Really! Those are the shares I was looking for... Maybe the bobox net
bios name is using the wrong IP address?

nbtstat -c

Local Area Connection 2:
Node IpAddress: [0.0.0.0] Scope Id: []

No names in cache

Wireless Network Connection:
Node IpAddress: [192.168.2.254] Scope Id: []

NetBIOS Remote Cache Name Table

Name Type Host Address Life [sec]
------------------------------------------------------------
BOBOX <03> UNIQUE 192.168.2.2 -1
BOBOX <00> UNIQUE 192.168.2.2 -1
BOBOX <20> UNIQUE 192.168.2.2 -1

Ok, now how is this possible???? Both ping and nbtstat show that name
resolution is working! nbtstat -R and -RR have no effect either.

Any ideas appreciated...
John

John,

Interesting. I can think of a couple possibilities.

First, ping Bobox from itself, and from another computer.

Next, let's look at "browstat status" and "ipconfig /all" from each computer.
Read this article, and linked articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>