For example, let’s say we have a server called FILESRV on 10.0.0.4, we would add to the host file: 10.0.0.4 server1 10.0.0.4 server2 10.0.0.4 server3īy doing this we create N aliases for 10.0.0.4. There is another slick solution to this challenge proposed by Jeffrey Liedke of our partner company Kapa GmbHĮdit the hosts file (C:\Windows\System32\Drivers\etc) as administrator and add one entry for each network share on the same server. What can be done if you have more than two user names and shares on the same server that you want to connect to? That way Windows will interpret the IP address as a separate entry in its network connection list and there won’t be an issue. Instead of using the network name of the target server, use its IP address. The limitation in Windows is that you can’t connect to the same network server using two different sets of credentials (user name and password combinations). While Windows keeps track of separate network connection lists at the user session level, it also uses a global list. For example, the user administrator and local system and other sessions that appear in the Windows Task Manager. Each user session in Windows keeps track of the user’s network connections and there are several simultaneous user sessions in Windows. The origins of this error are as follows. Disconnect all previous connections to the server or shared resource and try again. When you try to connect to a network share you may encounter this Windows error 1219: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.
0 Comments
Leave a Reply. |