Comp A can see comb B but not vice-versa! Help!

[6tr6tr]

I have the two comp's (A=server, B=laptop). Both can ping each other. Both can reach the internet (laptop goes through server). However, while the server can reach laptop through "whack, whack": "\\laptop" - a login box popped up - laptop canNOT do the same with the server. "\\serverA" ends up with error box of no such resource.

Any idea what the issue could be?

I tried it with the firewall off and still couldn't find the resource "\\serverA".

 

[jfp23]

What OS is on the laptop? Also when you ping the server from the laptop do you use the machine name or the IP does it work for both? if you do \\IP of server what happens?

 

[6tr6tr]

Thanks for the reply.

The laptop is Windows 2000 Professional (Service Pack 1).

Doing "\\192.168.0.1" (server IP) also does not find the resource. but from the server, "\\192.168.0.2" (laptop ip) DOES work.

When I ping the server, I used the IP. I don't know how I'd ping the name of the server. I don't think you can do that (i.e. the internal, actual network id of the server). I can ping the external domain-name and IP from the laptop successfully.

I'm really at a loss here.

 

[jfp23]

do you have the client for Microsoft Networks loaded, is it in the same domain or workgroup if no domain present

 

[6tr6tr]

They are both in the same workgroup. When I check the local area connection on the laptop, it has "Client for Microsoft Networks" checked.

 

[6tr6tr]

I solved it! Apparently, when I turned off NetBIOS for the NIC (on the server) going to the external internet, it somehow propogated that for all NIC cards.

 

[dbMark]

Unless you have a really good reason not to, you really ought to update your laptop to the latest Windows 2000 service pack.