win98 netbios over tcpip problems

[artheim]

I have three systems that were working okay using NetBeui with file/print sharing and not having NetBios over TCP/IP enabled. I now need to change and remove NetBeui and allow NetBios over TCP/IP. 2 of the systems work okay, all 3 can ping any of the other 3 okay. All can use TCP/IP with Internet through NAT okay, but 1 Win98 system cannot see any of the other systems' shares. Also none of the other 2 systems can see the 1 system's shares - they can see the system name okay. I have double checked settings - all on same workgroup, all have file/print sharing enabled and all have multiple drives marked as shared, and all have netbios over TCP/IP enabled.. NET DIAG between the failing Win98 system and another Win98 system does not work. Remember, all I did was removed NetBeui and enabled NetBios over TCP/IP on all three systems.. any ideas/suggestions?

 

[bcastner]

Sounds like a browser issue. Is the browser enabled on all three machines?

 

[bcastner]

You may find this site helpful in your diagnosis. Look at the subhead Browser Issues, and the subhead Workgroup as a start:

http://www25.brinkster.com/ChicagoTech/

 

[artheim]

The problem was a simple one.. I had selected the Windows logon on the failing system, instead of Client for Microsoft Windows.. sure gives wierd indications.. but changed the Win98 system to use the Client for MS Windows and all is working now..

 

[artheim]

I was wrong!! (again).. I still have a problem with 1 Win98 system. My network currently has 2 Win98 systems and 1 Win2K Pro system - all configured with NetBios over TCP/IP. All had NetBeui and had NetBios over TCP/IP disabled before and were working okay. I have searched most of the site at

http://www25.brinkster.com/ChicagoTech/

and still am unable to get it working correctly. What I am observing is:

Win98 #1 - Immediately after boot, can see all systems with net view, can see all systems' shared resources with net view \\[systemname], and can map to any shared resource on the net. After some minutes, can no longer map to the other systems unless LMHOSTS file contains the network systems info.

Win98 #2 - Appears to always be able to map to any shared resource on the Win2k Pro, but never to the Win98 #1 system. nbtstat -a win98#1 fails with host not found. Ping to win98#1 times out, but ping to IP of win98 #1 always works.

Win2k Pro - Appears to always be able to map to any shared resource on the Win98 #2 system, but never to the Win98 #1 system. ping of win98#1 works okay, nbtstat -c shows win98#1 in the cache, net view shows all systems, including the win98 #1 system, but net view \\win98#1 falis with System error 53 - network path not found.

I have tried with and without the browser enabled on all systems, with the browser only enabled on the Win98 #2 system, with and without a LMHOSTS file and enabled, but nothing so far has allow the mapping in both directions with the Win98 #1 system to work - even after rebooting all systems.

Any suggestions or references to additional areas to figure out how to get the shared resources to work without NetBeui installed would be most welcome.

 

[ckuner]

Try removing the client for Microsoft networks on win98#1 and then reinstall it (with a reboot in between). I've seen that problem with win9x machines before and that's always fixed it for me.

 

[artheim]

Thanks ckuner, but that did not seem to make any difference. One additional piece of info that MAY be important, I have the Win98 #1 and the Win2K Pro systems connected to a Wireless AP and then the Win98 #2 connected to a hub that is also connected to the AP.. I would have thought that may make the Win98 #2 not visable, but will play with the cabling to see if maybe changing how the systems are connected to the hub makes a difference.