Hyper V Server R2 cannot ping out

In troubleshooting Remote Management to a Hyper V Server 2008 R2 machine, I notice that I cannot ping out anywhere from the server.  Not the default gateway, not the DC, nothing.  I can ping the server and RDP to it, and I know that before I could download updates for it using the config tool.  The network adapter is a static address, DHCP is disabled, the Preferred DNS server is the DC, the Alternate DNS server is the router.  I have temporarily disabled the windows firewall with no luck.  No extra firewall or virus is installed.  I have flushed the DNS. Why can I not ping anywhere?  
LVL 1
RadRichieAsked:
Who is Participating?
 
RadRichieConnect With a Mentor Author Commented:
It looks like manually disabling NETBIOS over TCPIP solved the issue.  Will confirm a little later.
0
 
RadRichieAuthor Commented:
Note when running ipconfig /all the Autoconfiguration IPv4 address is 169.254.103.167.  The IPv4 address is 192.168.2.198 (Duplicate).  In the HyperV config tool I set the static IP of 192.168.2.198.
0
 
MCSA2003Commented:
Have you installed the integrated tools package? If not, do so and test it. Go actions then click on insert integration tools while you are connected to it in Hyper V Manager. Also check out this link for setting up the network adapter in hyper v. http://blog.baeke.info/blog/_archives/2007/12/16/3413344.html
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
RadRichieAuthor Commented:
Hi, where can I get the "integrated tools package"?  I have only used the server configuration screen so far.  Thanks.
0
 
MCSA2003Commented:
0
 
RadRichieAuthor Commented:
Hi thank you, partial points at least for that.  But I am talking about the bare Hyper V server connectivity.  I don't have any VMs on it yet.  Note that I can no longer RDP to the server.  It says You are alerady connected to the console of this computer, which is not true.  Something is amiss and I wonder if its because of the APIPA.  I have installed the lastest NIC driver with no change in ability to ping out of the server.  Autoconfiguration Enabled is set to "yes"  and the 169.... address is still there in ipconfig /all.
0
 
RadRichieAuthor Commented:
That was the silver bullet for all 3 issues:  Pinging out, RDP in, and Server Management in.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.