Clever Geek Handbook

What impact does the "Duplicate name on the network" error have on a virtual machine?

I have a project where multiple developers are using a copy of the same Windows Virtual PC image (W2K3 SE SP2). Since our solution is tied to a machine name (which is not ideal, I know), all developers have the same machine name.

We are using VPN to connect to the remote system, when connecting we get the error "Windows error: duplicate name on the network".

Since all development takes place locally, we do not depend on other machines connecting to us - only outgoing connections.

I know it is best to change the machine name, but what is this reasoning? What impact would this have?

+1


source to share


3 answers


If you're all running locally in a virtual machine, there is no reason the machine name should remain the same.



I faced a similar situation when I am working. We used a trial version of Microsoft SharePoint 2007. Same error, no development issues. The only thing I ran into was when I opened Internet Explorer to browse the pages on the server by typing http: //servername/page.aspx , I would hit another VM developer. I had to use http: //ipaddress/page.aspx to get to my own machine.

0


source


The hostname in this case is mainly used for SMB / CIFS file sharing. The problem with duplicate names is that if you are trying to share files, there is no way to determine which one is the host.



There may be some other related effects as well, but I think if you only work locally you shouldn't have any problems.

0


source


Well, other than goofing up AD, DNS, Netbios or Netbeui ... nothing.

Duplicate machine names are not best practice. This could be due to file sharing, ping, group policies, etc.

You have to ask yourself WHY they are doing this in the first place.

0


source






More articles:


All Articles