Discussion Locked

Access to shared drive

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I work with a large peer to peer network that intermittently has problems connecting to shared resources on one of the Windows 2000 systems, the last system added to the network. The problem system shows in network neighborhood, but when you try to connect to a shared drive, a message appears saying that the ?The device does not exist on the network?. The problem is only with connecting to this one system, but intermittently occurs while trying to connect from multiple other systems.

This network consists of 2 Windows 2000 systems, 4 Windows 98 systems, 3 Windows 95 systems and 3 DOS systems. Each of these systems has 4 ? 10 mapped drives. There is also a Cisco router for Internet access through ADSL. The router is set up to assign IP addresses through DHCP. All systems are part of the same Workgroup.

All systems, except the DOS systems, use IPX/SPX protocol, with net bios enabled. The systems that need to access the DOS systems also have NetBEUI loaded. TCP/IP protocol is also loaded on all systems (except DOS systems) for Internet access, but not bound to file and print sharing.

Since this problem started with the last system added, have I exceeded some limit of peer to peer networking?

I would greatly appreciate any comments or suggestions. Thanks.

5 replies

by stillatit

Older versions of workstation could only accept 10 simultaneous external connections. I don't know if this is still true in W2K, but what you are describing sounds suspiciously similar. When you see a station not being able to connect, try looking at the server manager and seeing if there are already 10 connections.

Good luck.

by cviehweg

Actually your peer-to-peer network is not that large. Until recently (past 12 months), we were running peer-peer with 89 nodes (printers, switches, PCs, and Unix). Our sharing ,problesm were almost always cleared up when we bound all services to both TCP//IP and NetBUI. I am not a fan of NetBUI, but if it took loading NetBUI to make my customers happy - I did it. So, number of workstations is not your problem. Try reviewing your bindings and let me know.

by dhl

Thanks, I loaded NetBeui on all systems, as the default, however I did not bind TCP/IP to file and print sharing for better security. After reading some additional information on the MS Website, I disabled master brouse services on all workstationsexcept the Win 2000 systems.

So far everything is working great!!!

Thanks again for your help.

This discussion is closed to new replies.