More Connections Can Be Made At This Time "Multiple connections to the ...
while the dialup connection is active "No operation can be performed on the ... http://www.chicagotech.net/neterrors.htm
The amount of remote connections you can make to a machine depends on the licensing of your OS. Standard licenses allow up to two concurrent connections. Many of the basic server licenses allow ten. There are enterprise licenses that allow even more than that however, but they cost a pretty penny.
So, I'm assuming that I have the "standard" license. I don't understand how or why this would interfere with me trying to use "Net View".
The computers I am having this issue on are WindowsXP connected to a 2003 server domain. I am not running the license module on the server.
Is there a way I can change this "Standard" license number?
I read another thread in here and they mentioned that I might try tweaking the register. Here's what I did:
1. Start Registry Editor.
2. Locate, and then click the following key in the registry:
3. On the Edit menu, click Add Value, and then add the following registry value:
Value Name: RestrictAnonymous
Data Type: REG_DWORD
A value of 2 restricts null session connections.
I had to reboot but it seems to be working. However, when I run net statistics server, it shows only one session now. That might be due to the reboot. I'll wait and see if it keeps working or not.
Nope. Didn't work. I changed it back and now I am getting the system error 72 message when logging on and attempting to map four drives to specific shared folders on the server.
Man, I just LOVE Microsoft. Each version just gets better and better....
I ended up ditching all Microsoft tech for servers a year ago just because of reasons such as this. They don't disclose limitations like this when you purchase the software and expect you to pay them to for the priviledge of finding out how truly limited the OS is. Then they tell you that you need to buy a new OS or upgrade your license. It's a stupid mess that they have created all in order to justify the need for MSCE certifications and higher-priced "server line" Windows versions.
In the end, I built a Linux server running Samba. Since then, I haven't had any problems accessing the network drives, doing remote logins to the local server, etc. The funny thing is that this didn't cost me one red cent, just a bit of time that ended up being far less than the time I spent diagnosing problems with my Windows server.