move server to different physical network without changing ip addressHow much network latency is “typical” for east - west coast USA?Changing IP address of current serverHow do I say two IP address are in different networkHow to identify and differentiate networks so I can set location?Move single ip address accross network or virtual machinesDomain controller network profile starts as publicBridging host-only subnet on multiple Dom0sCreating a separate network without physical adapters on ESXiOutbound ip address of server keeps changingLooking for way to expose and extend 100s of USB connections from VM cluster(s)
Interview was just a one hour panel. Got an offer the next day; do I accept or is this a red flag?
How can I detect if I'm in a subshell?
Jam with honey & without pectin has a saucy consistency always
What does the "titan" monster tag mean?
What's the reason for the decade jump in the recent X-Men trilogy?
What publication claimed that Michael Jackson died in a nuclear holocaust?
Fastest way from 10 to 1 with everyone in between
In The Incredibles 2, why does Screenslaver's name use a pun on something that doesn't exist in the 1950s pastiche?
Opposite of "Concerto Grosso"?
What did the 8086 (and 8088) do upon encountering an illegal instruction?
Are athletes' college degrees discounted by employers and graduate school admissions?
Does WiFi affect the quality of images downloaded from the internet?
Must a CPU have a GPU if the motherboard provides a display port (when there isn't any separate video card)?
New Site Design!
Was the Lonely Mountain, where Smaug lived, a volcano?
Why is C++ template use not recommended in space/radiated environment?
Would a bit of grease on overhead door cables or bearings cause the springs to break?
SFDX force:org:clone not working
Why did the AvroCar fail to fly above 3 feet?
Is it possible to have battery technology that can't be duplicated?
Why can't we feel the Earth's revolution?
What is Gilligan's full name?
Idiom for 'person who gets violent when drunk"
How to turn a table by 90° and split variables in two or more lines
move server to different physical network without changing ip address
How much network latency is “typical” for east - west coast USA?Changing IP address of current serverHow do I say two IP address are in different networkHow to identify and differentiate networks so I can set location?Move single ip address accross network or virtual machinesDomain controller network profile starts as publicBridging host-only subnet on multiple Dom0sCreating a separate network without physical adapters on ESXiOutbound ip address of server keeps changingLooking for way to expose and extend 100s of USB connections from VM cluster(s)
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I have a set of 4 virtual machines (server 2008r2) that I need to move to a new data center which cannot have their IP addresses changed. I've tried for months to get the vendor to change them, but the software is so horribly designed that it's just not possible. At the moment, I'm exploring some network options but if I could handle this on the server somehow I'd prefer to do that.
Right now the servers are on the 192.168.0.0/24 network and they need to be moved to the 192.168.10.0/24 network. Is there any way to use a loopback adapter to accomplish this or perhaps some other method? I'm certainly open to all suggestions.
I should point out that the move is to a geographically different location.
networking windows-server-2008 virtual-machines ip-address
|
show 1 more comment
I have a set of 4 virtual machines (server 2008r2) that I need to move to a new data center which cannot have their IP addresses changed. I've tried for months to get the vendor to change them, but the software is so horribly designed that it's just not possible. At the moment, I'm exploring some network options but if I could handle this on the server somehow I'd prefer to do that.
Right now the servers are on the 192.168.0.0/24 network and they need to be moved to the 192.168.10.0/24 network. Is there any way to use a loopback adapter to accomplish this or perhaps some other method? I'm certainly open to all suggestions.
I should point out that the move is to a geographically different location.
networking windows-server-2008 virtual-machines ip-address
1
Connect them to a Layer 3 switch, configure a VLAN for the switch ports they're connected to, and enable/configure inter-VLAN routing?
– joeqwerty
May 30 at 0:20
They would be in different physical locations so I can't do that. I thought about stretching a VLAN across the WAN, but that would create more problems than its worth. I proposed this question a while ago somewhere else and someone mentioned they had a solution using a loopback adapter on Windows. Unfortunately they never replied after that so I have no clue what they were getting at.
– Cragmuer
May 30 at 0:29
I'm not understanding what the physical location has to do with it. Let's say, for example, that the provider is giving you a 10.0.0.0/8 address block to work with. You configure the L3 switch with a VLAN for these servers, enable/configure inter-VLAN routing on the switch, and route traffic to and from these servers in the switch to and from the provider network space that's been allocated to you. Why would a stretched VLAN even be in play?
– joeqwerty
May 30 at 0:32
OK, I wasn't quite getting the full picture without the diagram. Assuming that you need to move those servers and maintain connectivity/routability between them and every other network/device without changing the ip addresses of the servers, you might look into static host routes on the routers for those 2 servers and then configure a VLAN and inter-VLAN routing like I described.
– joeqwerty
May 30 at 0:51
How could I use inter-VLAN routing over 802.1q though?
– Cragmuer
May 30 at 17:35
|
show 1 more comment
I have a set of 4 virtual machines (server 2008r2) that I need to move to a new data center which cannot have their IP addresses changed. I've tried for months to get the vendor to change them, but the software is so horribly designed that it's just not possible. At the moment, I'm exploring some network options but if I could handle this on the server somehow I'd prefer to do that.
Right now the servers are on the 192.168.0.0/24 network and they need to be moved to the 192.168.10.0/24 network. Is there any way to use a loopback adapter to accomplish this or perhaps some other method? I'm certainly open to all suggestions.
I should point out that the move is to a geographically different location.
networking windows-server-2008 virtual-machines ip-address
I have a set of 4 virtual machines (server 2008r2) that I need to move to a new data center which cannot have their IP addresses changed. I've tried for months to get the vendor to change them, but the software is so horribly designed that it's just not possible. At the moment, I'm exploring some network options but if I could handle this on the server somehow I'd prefer to do that.
Right now the servers are on the 192.168.0.0/24 network and they need to be moved to the 192.168.10.0/24 network. Is there any way to use a loopback adapter to accomplish this or perhaps some other method? I'm certainly open to all suggestions.
I should point out that the move is to a geographically different location.
networking windows-server-2008 virtual-machines ip-address
networking windows-server-2008 virtual-machines ip-address
edited May 30 at 6:37
Stephen Rauch
221139
221139
asked May 30 at 0:12
CragmuerCragmuer
112
112
1
Connect them to a Layer 3 switch, configure a VLAN for the switch ports they're connected to, and enable/configure inter-VLAN routing?
– joeqwerty
May 30 at 0:20
They would be in different physical locations so I can't do that. I thought about stretching a VLAN across the WAN, but that would create more problems than its worth. I proposed this question a while ago somewhere else and someone mentioned they had a solution using a loopback adapter on Windows. Unfortunately they never replied after that so I have no clue what they were getting at.
– Cragmuer
May 30 at 0:29
I'm not understanding what the physical location has to do with it. Let's say, for example, that the provider is giving you a 10.0.0.0/8 address block to work with. You configure the L3 switch with a VLAN for these servers, enable/configure inter-VLAN routing on the switch, and route traffic to and from these servers in the switch to and from the provider network space that's been allocated to you. Why would a stretched VLAN even be in play?
– joeqwerty
May 30 at 0:32
OK, I wasn't quite getting the full picture without the diagram. Assuming that you need to move those servers and maintain connectivity/routability between them and every other network/device without changing the ip addresses of the servers, you might look into static host routes on the routers for those 2 servers and then configure a VLAN and inter-VLAN routing like I described.
– joeqwerty
May 30 at 0:51
How could I use inter-VLAN routing over 802.1q though?
– Cragmuer
May 30 at 17:35
|
show 1 more comment
1
Connect them to a Layer 3 switch, configure a VLAN for the switch ports they're connected to, and enable/configure inter-VLAN routing?
– joeqwerty
May 30 at 0:20
They would be in different physical locations so I can't do that. I thought about stretching a VLAN across the WAN, but that would create more problems than its worth. I proposed this question a while ago somewhere else and someone mentioned they had a solution using a loopback adapter on Windows. Unfortunately they never replied after that so I have no clue what they were getting at.
– Cragmuer
May 30 at 0:29
I'm not understanding what the physical location has to do with it. Let's say, for example, that the provider is giving you a 10.0.0.0/8 address block to work with. You configure the L3 switch with a VLAN for these servers, enable/configure inter-VLAN routing on the switch, and route traffic to and from these servers in the switch to and from the provider network space that's been allocated to you. Why would a stretched VLAN even be in play?
– joeqwerty
May 30 at 0:32
OK, I wasn't quite getting the full picture without the diagram. Assuming that you need to move those servers and maintain connectivity/routability between them and every other network/device without changing the ip addresses of the servers, you might look into static host routes on the routers for those 2 servers and then configure a VLAN and inter-VLAN routing like I described.
– joeqwerty
May 30 at 0:51
How could I use inter-VLAN routing over 802.1q though?
– Cragmuer
May 30 at 17:35
1
1
Connect them to a Layer 3 switch, configure a VLAN for the switch ports they're connected to, and enable/configure inter-VLAN routing?
– joeqwerty
May 30 at 0:20
Connect them to a Layer 3 switch, configure a VLAN for the switch ports they're connected to, and enable/configure inter-VLAN routing?
– joeqwerty
May 30 at 0:20
They would be in different physical locations so I can't do that. I thought about stretching a VLAN across the WAN, but that would create more problems than its worth. I proposed this question a while ago somewhere else and someone mentioned they had a solution using a loopback adapter on Windows. Unfortunately they never replied after that so I have no clue what they were getting at.
– Cragmuer
May 30 at 0:29
They would be in different physical locations so I can't do that. I thought about stretching a VLAN across the WAN, but that would create more problems than its worth. I proposed this question a while ago somewhere else and someone mentioned they had a solution using a loopback adapter on Windows. Unfortunately they never replied after that so I have no clue what they were getting at.
– Cragmuer
May 30 at 0:29
I'm not understanding what the physical location has to do with it. Let's say, for example, that the provider is giving you a 10.0.0.0/8 address block to work with. You configure the L3 switch with a VLAN for these servers, enable/configure inter-VLAN routing on the switch, and route traffic to and from these servers in the switch to and from the provider network space that's been allocated to you. Why would a stretched VLAN even be in play?
– joeqwerty
May 30 at 0:32
I'm not understanding what the physical location has to do with it. Let's say, for example, that the provider is giving you a 10.0.0.0/8 address block to work with. You configure the L3 switch with a VLAN for these servers, enable/configure inter-VLAN routing on the switch, and route traffic to and from these servers in the switch to and from the provider network space that's been allocated to you. Why would a stretched VLAN even be in play?
– joeqwerty
May 30 at 0:32
OK, I wasn't quite getting the full picture without the diagram. Assuming that you need to move those servers and maintain connectivity/routability between them and every other network/device without changing the ip addresses of the servers, you might look into static host routes on the routers for those 2 servers and then configure a VLAN and inter-VLAN routing like I described.
– joeqwerty
May 30 at 0:51
OK, I wasn't quite getting the full picture without the diagram. Assuming that you need to move those servers and maintain connectivity/routability between them and every other network/device without changing the ip addresses of the servers, you might look into static host routes on the routers for those 2 servers and then configure a VLAN and inter-VLAN routing like I described.
– joeqwerty
May 30 at 0:51
How could I use inter-VLAN routing over 802.1q though?
– Cragmuer
May 30 at 17:35
How could I use inter-VLAN routing over 802.1q though?
– Cragmuer
May 30 at 17:35
|
show 1 more comment
1 Answer
1
active
oldest
votes
If you'd prefer to don't touch configuration of the moving server at all, your best bet would be a LAN-to-LAN VPN (Using L2 Bridge)
One side of this VPN will be your original 192.168.0.0/24 LAN and another side will be LAN just from your server 192.168.0.100.
Pros of this solution will be that you don't need to touch network settings on your servers and clients. Everything will be totally transparent.
Cons are that all communications to your 192.168.0.100 server will be going through 192.168.0.0/24 router and VPN bridges - even for the servers in 192.168.10.0/24 segment. I.E. the 192.168.10.0/24 LAN and 192.168.0.100 server will not see each other directly, even being stationed on the same site.
Read more about this solution on the website of SoftEther VPN project.
Alternatively you could try implementing a dialup VPN from your 192.168.0.100 server to 192.168.0.0/24 network, but that would require additional configurations on the server itself.
Thanks for your answer Sergey, but I'm not sure if this is going to work for unfortunately. The performance impact would likely be too great. I might give it a shot none-the-less.
– Cragmuer
Jun 4 at 17:17
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969415%2fmove-server-to-different-physical-network-without-changing-ip-address%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you'd prefer to don't touch configuration of the moving server at all, your best bet would be a LAN-to-LAN VPN (Using L2 Bridge)
One side of this VPN will be your original 192.168.0.0/24 LAN and another side will be LAN just from your server 192.168.0.100.
Pros of this solution will be that you don't need to touch network settings on your servers and clients. Everything will be totally transparent.
Cons are that all communications to your 192.168.0.100 server will be going through 192.168.0.0/24 router and VPN bridges - even for the servers in 192.168.10.0/24 segment. I.E. the 192.168.10.0/24 LAN and 192.168.0.100 server will not see each other directly, even being stationed on the same site.
Read more about this solution on the website of SoftEther VPN project.
Alternatively you could try implementing a dialup VPN from your 192.168.0.100 server to 192.168.0.0/24 network, but that would require additional configurations on the server itself.
Thanks for your answer Sergey, but I'm not sure if this is going to work for unfortunately. The performance impact would likely be too great. I might give it a shot none-the-less.
– Cragmuer
Jun 4 at 17:17
add a comment |
If you'd prefer to don't touch configuration of the moving server at all, your best bet would be a LAN-to-LAN VPN (Using L2 Bridge)
One side of this VPN will be your original 192.168.0.0/24 LAN and another side will be LAN just from your server 192.168.0.100.
Pros of this solution will be that you don't need to touch network settings on your servers and clients. Everything will be totally transparent.
Cons are that all communications to your 192.168.0.100 server will be going through 192.168.0.0/24 router and VPN bridges - even for the servers in 192.168.10.0/24 segment. I.E. the 192.168.10.0/24 LAN and 192.168.0.100 server will not see each other directly, even being stationed on the same site.
Read more about this solution on the website of SoftEther VPN project.
Alternatively you could try implementing a dialup VPN from your 192.168.0.100 server to 192.168.0.0/24 network, but that would require additional configurations on the server itself.
Thanks for your answer Sergey, but I'm not sure if this is going to work for unfortunately. The performance impact would likely be too great. I might give it a shot none-the-less.
– Cragmuer
Jun 4 at 17:17
add a comment |
If you'd prefer to don't touch configuration of the moving server at all, your best bet would be a LAN-to-LAN VPN (Using L2 Bridge)
One side of this VPN will be your original 192.168.0.0/24 LAN and another side will be LAN just from your server 192.168.0.100.
Pros of this solution will be that you don't need to touch network settings on your servers and clients. Everything will be totally transparent.
Cons are that all communications to your 192.168.0.100 server will be going through 192.168.0.0/24 router and VPN bridges - even for the servers in 192.168.10.0/24 segment. I.E. the 192.168.10.0/24 LAN and 192.168.0.100 server will not see each other directly, even being stationed on the same site.
Read more about this solution on the website of SoftEther VPN project.
Alternatively you could try implementing a dialup VPN from your 192.168.0.100 server to 192.168.0.0/24 network, but that would require additional configurations on the server itself.
If you'd prefer to don't touch configuration of the moving server at all, your best bet would be a LAN-to-LAN VPN (Using L2 Bridge)
One side of this VPN will be your original 192.168.0.0/24 LAN and another side will be LAN just from your server 192.168.0.100.
Pros of this solution will be that you don't need to touch network settings on your servers and clients. Everything will be totally transparent.
Cons are that all communications to your 192.168.0.100 server will be going through 192.168.0.0/24 router and VPN bridges - even for the servers in 192.168.10.0/24 segment. I.E. the 192.168.10.0/24 LAN and 192.168.0.100 server will not see each other directly, even being stationed on the same site.
Read more about this solution on the website of SoftEther VPN project.
Alternatively you could try implementing a dialup VPN from your 192.168.0.100 server to 192.168.0.0/24 network, but that would require additional configurations on the server itself.
answered May 30 at 2:37
Sergey NudnovSergey Nudnov
702410
702410
Thanks for your answer Sergey, but I'm not sure if this is going to work for unfortunately. The performance impact would likely be too great. I might give it a shot none-the-less.
– Cragmuer
Jun 4 at 17:17
add a comment |
Thanks for your answer Sergey, but I'm not sure if this is going to work for unfortunately. The performance impact would likely be too great. I might give it a shot none-the-less.
– Cragmuer
Jun 4 at 17:17
Thanks for your answer Sergey, but I'm not sure if this is going to work for unfortunately. The performance impact would likely be too great. I might give it a shot none-the-less.
– Cragmuer
Jun 4 at 17:17
Thanks for your answer Sergey, but I'm not sure if this is going to work for unfortunately. The performance impact would likely be too great. I might give it a shot none-the-less.
– Cragmuer
Jun 4 at 17:17
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f969415%2fmove-server-to-different-physical-network-without-changing-ip-address%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Connect them to a Layer 3 switch, configure a VLAN for the switch ports they're connected to, and enable/configure inter-VLAN routing?
– joeqwerty
May 30 at 0:20
They would be in different physical locations so I can't do that. I thought about stretching a VLAN across the WAN, but that would create more problems than its worth. I proposed this question a while ago somewhere else and someone mentioned they had a solution using a loopback adapter on Windows. Unfortunately they never replied after that so I have no clue what they were getting at.
– Cragmuer
May 30 at 0:29
I'm not understanding what the physical location has to do with it. Let's say, for example, that the provider is giving you a 10.0.0.0/8 address block to work with. You configure the L3 switch with a VLAN for these servers, enable/configure inter-VLAN routing on the switch, and route traffic to and from these servers in the switch to and from the provider network space that's been allocated to you. Why would a stretched VLAN even be in play?
– joeqwerty
May 30 at 0:32
OK, I wasn't quite getting the full picture without the diagram. Assuming that you need to move those servers and maintain connectivity/routability between them and every other network/device without changing the ip addresses of the servers, you might look into static host routes on the routers for those 2 servers and then configure a VLAN and inter-VLAN routing like I described.
– joeqwerty
May 30 at 0:51
How could I use inter-VLAN routing over 802.1q though?
– Cragmuer
May 30 at 17:35