Yeah, you heard me right. I've recently run into the problem of a Windows XP Pro system only allowing 10 connections per share and am trying this as a last resort before buying Server 2003 Standard for the 2 systems with shares.
Here's the situation: I have a domain with 1 2003 SBS server and about 150 PCs. 2 of those PCs each have 2TB of storage shared to the network for video file backups. I want to map a drive from any of the 150 PCs to the file servers to transfer files over the network, but need more than 10 users connected to the share at one time - something like 25 would be great. I thought that if I mapped a network drive to the storage PCs from the server and then used a logon script to map, say K:, to the mapped network drive on the server, it would only be seen as 1 connection and I can have as many people as I wantusing it at once. Only problem is I can't figure out how to map a drive to a mapped drive...
Thanks for any help
Here's the situation: I have a domain with 1 2003 SBS server and about 150 PCs. 2 of those PCs each have 2TB of storage shared to the network for video file backups. I want to map a drive from any of the 150 PCs to the file servers to transfer files over the network, but need more than 10 users connected to the share at one time - something like 25 would be great. I thought that if I mapped a network drive to the storage PCs from the server and then used a logon script to map, say K:, to the mapped network drive on the server, it would only be seen as 1 connection and I can have as many people as I wantusing it at once. Only problem is I can't figure out how to map a drive to a mapped drive...
Thanks for any help