Windows Server 2012 networking issue
-
Friday, January 25, 2013 2:35 PM
I have a networking issue:
The Host (Server 2012) can get on the internet and I can remote to it as well, this is not on a Domain, it is on Workgroup. I am not sure if leaving a host on a workgroup is good practice.
I can’t get on the internet with the VM, can anyone see why that could be?
Host – Server 2012
IP Address: 192.168.0.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
..........................................
V-Switch
IP Address: 192.168.0.3
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
..........................................
VM1 – Server 2012 Essentials
IP Address: 192.168.0.4
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
Graham
- Edited by GrahamUK3 Friday, January 25, 2013 3:14 PM
All Replies
-
Friday, January 25, 2013 7:25 PM
It might sounds a little stupid but what's about DNS Servers?
If you not sure what to use take this two entries:
8.8.8.8 and 8.8.4.4
Add them and check if this will work.
-
Friday, January 25, 2013 8:04 PM
The DNS servers I have been using are:
194.168.4.100
194.168.8.100
I can ping both of these fine.
Graham
-
Friday, January 25, 2013 8:40 PM
Connect to the virtual Server and do:
ping 192.168.0.1
ping 192.168.0.2
pathping 8.8.8.8
Post the result here!
-
Saturday, January 26, 2013 12:13 AM
Your configuration description is a little sparse, so we need a bit more detail. Do you have two physical NICs on the host? It looks like one physical NIC (192.168.0.2) is dedicated to the host. I'm assuming from the name that v-switch is a physical NIC that has been configured as a Hyper-V virtual switch, and it was configured to be accessible by the host. You added an IP address to the virtual NIC that was created for the virtual switch. Is this the case? In other words, your host has two addresses assigned to it? I don't think thisi is the cause of your problem, but you should never (well, almost never) have two IP addresses in the same subnet on the same server. Strange things can happen.
As to what might be the cause (again guessing because of lack of information) is that you defined an internal or private virtual switch for the VM and you put the VM's NIC on that. Internal/private virtual switches do not have access to the outside network.
Bottom line is that it would be helpful to know your NIC and virtual switch configuration.
RE: leaving a host in a workgroup. No problem with that. It just makes it a little more challenging to manage, particularly if the rest of your environment is in a domain. But if this is a test system, leaving it in a workgroup should not make a whit of a difference.
.:|:.:|:. tim
- Marked As Answer by Jeremy_WuMicrosoft Contingent Staff, Moderator Thursday, January 31, 2013 6:15 PM
-
Tuesday, January 29, 2013 9:08 AMModerator
Hi GrahamUK3,
Based on my knowledge, it seems that you have created a Hyper-V Internal Virtual Switch. If so, you may need to enable ICS on the physical NIC.
Also, you can remove the Internal Virtual Switch and create an External Virtual Switch instead.
More information:
Hyper-V Virtual Switch Overviewhttp://technet.microsoft.com/en-us/library/hh831823.aspx
Hyper-V: Virtual Networking Survival Guide (en-US)
Hope this helps.
Jeremy Wu
TechNet Community Support
- Marked As Answer by Jeremy_WuMicrosoft Contingent Staff, Moderator Thursday, January 31, 2013 6:15 PM
-
Friday, February 01, 2013 10:52 AMMany thanks for the helps guys, I have got the network working using the links provided by Jeremy_Wu.
Graham
.png)
