Bridge mode Host VM different subnet

jmanatee · Post by **jmanatee** » 23. Jul 2013, 17:45

I am renting a dedicated server. I have been assigned two static IPs from different C blocks
If I use NAT Everything works. When I switch to bridged and assign the static IP to the VM it stops

I suspect it has to do with the two assigned IPs
???.169.159.94 255.255.255.255 gateway ???.169.159.1
???.169.129.30 255.255.255.255 gateway ???.169.159.1

???.169.159.94 is assigned to host. win 2008 R2 webserver 64bit
???.169.129.30 is assigned to VM. win 2k3 R2 32bit (win2k3 wont let me assign 255.255.255.255 as subnet and complains about gateway)

VM has no access to the web (IP or DNS) NS Lookup fails etc..

Is there something special I have to do because they are assigned like this

Help

Thank you

Post by **BillG** » 24. Jul 2013, 01:35

I am not surprised. 255.255.255.255 puts the machine in a subnet all by itself! It cannot possibly have a default gateway when there are no other IP addresses in the same subnet. Where did you dream up that subnet?

My guess is that you have a VPN connection which would account for the 32-bit subnet (a VPN is a point to point connection, not a standard routed connection and does not need a default gateway).

jmanatee · Post by **jmanatee** » 24. Jul 2013, 04:20

BillG wrote:I am not surprised. 255.255.255.255 puts the machine in a subnet all by itself! It cannot possibly have a default gateway when there are no other IP addresses in the same subnet. Where did you dream up that subnet?

My guess is that you have a VPN connection which would account for the 32-bit subnet (a VPN is a point to point connection, not a standard routed connection and does not need a default gateway).

I didn't dream this up. It was assigned by the server farm. I am connecting to this server via RDP not VPN I assume the server has a direct connection to there router or vlan and then to there backbone.

Post by **noteirak** » 24. Jul 2013, 16:17

There shouldn't be anything special to do, but they might do a check on the MAC address and block what's not supposed to be there.
You should do some packet sniffing and see what's going on.
Bridge is definitly the good mode to use, so the issue seem to lie somewhere else and not with Virtualbox.

jmanatee · Post by **jmanatee** » 24. Jul 2013, 19:00

noteirak wrote:There shouldn't be anything special to do, but they might do a check on the MAC address and block what's not supposed to be there.
You should do some packet sniffing and see what's going on.
Bridge is definitly the good mode to use, so the issue seem to lie somewhere else and not with Virtualbox.

I have setup a couple VM so I am confused by this one. But I have never been issued IPs like this.

Not sure what would be the correct settings in the VM but nothing I have tried in bridge mode works.

Can I clone the mac address from the server?

Any ideas on what to try

Post by **Perryg** » 24. Jul 2013, 19:15

Given the addresses you have you will need to use NAT and port forward or ask the provider to do something on their end. As BillG said the subnet of all 255's leave no gateway. Most of the time places like GoDaddy and the like aren't keen on you setting up several machines. They want you to have a presence and pay for it.

virtualbox.org

Bridge mode Host VM different subnet

Bridge mode Host VM different subnet

Re: Bridge mode Host VM different subnet

Re: Bridge mode Host VM different subnet

Re: Bridge mode Host VM different subnet

Re: Bridge mode Host VM different subnet

Re: Bridge mode Host VM different subnet