I have a project where multiple developers are using a copy of the same windows Virtual PC image (W2K3 SE SP2). Because our solution is tied to the machine-name (less than ideal, i know) all of the developers have the same machine name.
我有一个项目,其中多个开发人员正在使用相同的Windows Virtual PC映像(W2K3 SE SP2)的副本。因为我们的解决方案与机器名称相关(不太理想,我知道)所有开发人员都拥有相同的机器名称。
We use a VPN to connect to a remote system, upon connection we get the "Windows Error: A duplicate name exists on the network" error.
我们使用VPN连接到远程系统,连接后我们收到“Windows错误:网络上存在重复名称”错误。
Since all development is happening locally, we're not dependent on other machines connecting to us -- only outbound connections.
由于所有开发都在本地进行,因此我们不依赖于连接到我们的其他机器 - 仅限出站连接。
I know it's best practice to change the machine name, but what's the reasoning behind this? What impact would this have?
我知道更改机器名称是最佳做法,但这背后的原因是什么?这有什么影响?
3 个解决方案
#1
0
If you are doing all work locally on the VM, there is no reason why the machine name needs to stay the same.
如果您在VM上本地完成所有工作,则没有理由说机器名称需要保持不变。
I have run into a similar situation where I work. We were using Microsoft's trial version of SharePoint 2007 VM. Same error, no issues with development. The only thing I ran into was when I opened Internet Explorer to view the pages on the server by typing http://servername/page.aspx, I would hit another developer's VM. I had to use http://ipaddress/page.aspx to hit my own machine.
我遇到了类似的情况,我工作。我们使用的是Microsoft的SharePoint 2007 VM试用版。同样的错误,没有开发问题。我遇到的唯一问题是当我打开Internet Explorer以通过键入http://servername/page.aspx来查看服务器上的页面时,我会遇到另一个开发人员的VM。我不得不使用http://ipaddress/page.aspx来打我自己的机器。
#2
0
The machine name in this case is used mostly for SMB/CIFS file sharing purposes. The problem with duplicate names is if you try to share files, there is no way to identify which host is which.
在这种情况下,机器名称主要用于SMB / CIFS文件共享。重复名称的问题是,如果您尝试共享文件,则无法识别哪个主机是哪个主机。
There may also be some other related effects, but I think if you are only working locally you shouldn't have any problems.
可能还有一些其他相关的影响,但我想如果你只是在本地工作,你应该没有任何问题。
#3
0
Well besides goofing up AD, DNS, Netbios or Netbeui...nothing.
除了搞砸AD,DNS,Netbios或Netbeui之外......什么都没有。
Duplicate machine names is not a best practice. It can mess with file sharing, pinging, group policies, etc.
重复的机器名称不是最佳做法。它可能会混乱文件共享,ping,组策略等。
You have to ask yourself WHY they're doing this in the first place.
你必须问自己为什么他们这样做是首先。
#1
0
If you are doing all work locally on the VM, there is no reason why the machine name needs to stay the same.
如果您在VM上本地完成所有工作,则没有理由说机器名称需要保持不变。
I have run into a similar situation where I work. We were using Microsoft's trial version of SharePoint 2007 VM. Same error, no issues with development. The only thing I ran into was when I opened Internet Explorer to view the pages on the server by typing http://servername/page.aspx, I would hit another developer's VM. I had to use http://ipaddress/page.aspx to hit my own machine.
我遇到了类似的情况,我工作。我们使用的是Microsoft的SharePoint 2007 VM试用版。同样的错误,没有开发问题。我遇到的唯一问题是当我打开Internet Explorer以通过键入http://servername/page.aspx来查看服务器上的页面时,我会遇到另一个开发人员的VM。我不得不使用http://ipaddress/page.aspx来打我自己的机器。
#2
0
The machine name in this case is used mostly for SMB/CIFS file sharing purposes. The problem with duplicate names is if you try to share files, there is no way to identify which host is which.
在这种情况下,机器名称主要用于SMB / CIFS文件共享。重复名称的问题是,如果您尝试共享文件,则无法识别哪个主机是哪个主机。
There may also be some other related effects, but I think if you are only working locally you shouldn't have any problems.
可能还有一些其他相关的影响,但我想如果你只是在本地工作,你应该没有任何问题。
#3
0
Well besides goofing up AD, DNS, Netbios or Netbeui...nothing.
除了搞砸AD,DNS,Netbios或Netbeui之外......什么都没有。
Duplicate machine names is not a best practice. It can mess with file sharing, pinging, group policies, etc.
重复的机器名称不是最佳做法。它可能会混乱文件共享,ping,组策略等。
You have to ask yourself WHY they're doing this in the first place.
你必须问自己为什么他们这样做是首先。