FryingLizard
Programmer
Hi y'all,
I have a Win2k Advanced Server box sitting outside of our company firewall/NAT (on the 'real' internet). When we connect to this box from inside the company network, the NAT nat-urally (sorry) makes all our internal machines appear to have the same IP address. Also, the box cannot establish connections back through the NAT, which is fine by me, but may contribute to the following problem)..
Right, everyone inside the firewall can map drive shares from this box with no problem (using "map network drive.."
. Everything works fine until more than one person inside the company accesses files on the box at the same time. You can be pulling a file off the box and if someone else starts grabbing files simultaneously, your file share gets disconnected. If only one user is using the shared drives, you can read/write as many files as you want, with no problems.
I'm assuming this is because the box sees all fileshare requests as coming from the 'same' machine (i.e. the IP address of the NAT) and it gets confused and screws things up when multiple files are opened by different clients.
Any suggestions? I could really do with resolving this, and I've clearly got only just enough Windows sysadmin knowledge to be dangerous!
Thanks,
Rich Aplin
I have a Win2k Advanced Server box sitting outside of our company firewall/NAT (on the 'real' internet). When we connect to this box from inside the company network, the NAT nat-urally (sorry) makes all our internal machines appear to have the same IP address. Also, the box cannot establish connections back through the NAT, which is fine by me, but may contribute to the following problem)..
Right, everyone inside the firewall can map drive shares from this box with no problem (using "map network drive.."
. Everything works fine until more than one person inside the company accesses files on the box at the same time. You can be pulling a file off the box and if someone else starts grabbing files simultaneously, your file share gets disconnected. If only one user is using the shared drives, you can read/write as many files as you want, with no problems. I'm assuming this is because the box sees all fileshare requests as coming from the 'same' machine (i.e. the IP address of the NAT) and it gets confused and screws things up when multiple files are opened by different clients.
Any suggestions? I could really do with resolving this, and I've clearly got only just enough Windows sysadmin knowledge to be dangerous!
Thanks,
Rich Aplin
