Welcome to the Virtual Iron Forums!
Here you'll find information to help you get the maximum value from your Virtual Iron software.
Community |
Topic Title: node rediscovers as new node when rebooted... can't move vs over to new node Topic Summary: Created On: 01/31/2007 02:44 PM |
Linear : Threading : Single : Branch |
- jodys | - 01/31/2007 02:44 PM |
- cbarclay | - 01/31/2007 03:35 PM |
Topic Tools
|
01/31/2007 02:44 PM
|
|
Got my fist VS running, but when i restart the physical server and the ip changes, it gets rediscoverd as a new node. Is there any way to prevent this? I tried working around it by moving the VS I had created to the new node, but it won't even let me do that b/c when I try and copy it over, it's in fact trying to copy to itself and all the disk space is allocated. Am I missing something obvious?
|
|
|
|
01/31/2007 03:35 PM
|
|
It's not clear whether you're using a shared network or a dedicated network. If it's shared, you may need to check the lease time on your DHCP server.
Either way, we'd be happy to help. Please register for a free support incident. |
|
|
FORUMS
:
How-tos
:
General Q&A
:
node rediscovers as new node when reboot...
|
Topic Tools
|
FuseTalk Standard Edition - © 1999-2007 FuseTalk Inc. All rights reserved.
Copyright © 2003-2007 Virtual Iron Software, Inc. | Privacy Statement | Terms of Use | Site Map