We have a 7 workstation Peer to Peer XP Home network. On one workstation is the Organize folder, shared openly to the network. We use Lotus Organizer, and it points to this shared folder so we can all access and share schedule files. No problems.
Now,recently took out one of the XP Home workstations and put in an older workstation running 2000pro. This workstation does NOT use Organizer, and shares nothing but our dsl line (as do all others). Now, whenever the 2000 workstation is on (and never when it is off) most users are getting access errors indicating too many shares are in use. Therefore they have to try repeatedly before their Organizer program accesses the shared folder and launches their schedule. Trying repeatedly DOES achieve the connection. There is no way we're using more than 10 shares, and if a different machine (XP home) is connected in place of the 2000 machine, there is no problem.
Since I can't imagine what settings to look for in the network settings (heck, everyone's the same..nothing unique) I'm starting to wonder if the problem may be hardware. Perhaps a noisy NIC in the 2000 machine. Any suggestions? I never use 2000, so I have no idea if I'm overlooking something simple.
Now,recently took out one of the XP Home workstations and put in an older workstation running 2000pro. This workstation does NOT use Organizer, and shares nothing but our dsl line (as do all others). Now, whenever the 2000 workstation is on (and never when it is off) most users are getting access errors indicating too many shares are in use. Therefore they have to try repeatedly before their Organizer program accesses the shared folder and launches their schedule. Trying repeatedly DOES achieve the connection. There is no way we're using more than 10 shares, and if a different machine (XP home) is connected in place of the 2000 machine, there is no problem.
Since I can't imagine what settings to look for in the network settings (heck, everyone's the same..nothing unique) I'm starting to wonder if the problem may be hardware. Perhaps a noisy NIC in the 2000 machine. Any suggestions? I never use 2000, so I have no idea if I'm overlooking something simple.