Virtual PC 2007 on Server 2008 RC0 - Network trouble
I'm running RC0 succesfully on a Dell PE2905, and now I need to run a virtual machine on it.
I don't wan't to install Hyper-V because I read that it will ruin my upgrade path to 2008 RTM.
So after a little research I've found out that VirtualPC 2007 is not supported but it works for
most people. But when I install VPC 2007 my network card / connection goes crazy. The connection
becomes extremly slow, in 7 cases of 10 I can't even connect. If I have a remote desktop connection
up it will quit in a matter of minutes and leave me an error like saying somthing like "Network connection lost due encyption failure". When I uninstall VPC2007 everything is fine.Is there any solutions or idea´s that could help me, I would be really greatful.
Antworten
Is there any chance that you could try VPC on Vista on this hardware? That would help to identify whether this is an OS issue or a hardware issue.
Cheers,
Ben
- I don't think Virtual Server/Virtual PC are supported on Win 2k8.
Alle Antworten
Is there any chance that you could try VPC on Vista on this hardware? That would help to identify whether this is an OS issue or a hardware issue.
Cheers,
Ben
- I don't think Virtual Server/Virtual PC are supported on Win 2k8.
Hi Ben & Taylor Brown[MS] thanks for you answers.
Ben
I wish I could try it on Vista with the same hardware, but this is our only machine with that hardware and I won't install Vista on it.Taylor Brown[MS]
I know it's not supported but I've read here that it works for many people. I quess I have to wait for the Hyper-V in Server 2008 RTM then.I have the same issue on one of my server 08 boxes. The one sitting under it in the rack works perfect. The official 08 hit my mvls today so I guess I'll upgrade from the rc and use hyper-v.
- Virtual PC replaces your network driver (replace might be harsh - it does definately modify it and its behavior in creating the virtual networks) so you could easily run into a compatibility issue involving the NIC driver.
WS08 has the ability to create internal virtual networks as well (clustering and hyperv take advantage of this) so the possibility of a WS08 box having the NIC flake out after trying to install VirualPC is a real possibility and the most likely incompatibility to happen.
BrianEh wrote: Virtual PC replaces your network driver (replace might be harsh - it does definately modify it and its behavior in creating the virtual networks) so you could easily run into a compatibility issue involving the NIC driver. WS08 has the ability to create internal virtual networks as well (clustering and hyperv take advantage of this) so the possibility of a WS08 box having the NIC flake out after trying to install VirualPC is a real possibility and the most likely incompatibility to happen.
Sure this is understandable. The strange thing is the nics are both netxtream II and running the same drivers. The problem must lie somewhere different. Anyways onto hyper-v.
I've been having the same issues as you. At first I thought I was seeing some unexplainable network issue in WS2008. But after heavy testing I discovered that if I disabled the "Virtual Machine Network Services" on the NIC in question, everything worked fine from a network standpoint. However, this of course killed networking for the Virtual PC.
There definately seems to be some incompatibility issues with WS2008 and Virtual Machine Network Services, atleast with the Broadcom BCM5708C NetXtreme II GigE NIC.
I have actually been noticing not only intermittent connectivity, but also packet syncing problems. I am receiving data packets from the WS2008 server(the physical host machine) out of order at random intervals while VM Network Services is enabled.
Interestly enough, while VM Network Services is enabled, I can communicate with the Virtual PC flawlessly. I have WS2003 installed on the virtual machine, and there is no packet loss or connectivity issues of any kind. This only seems to affect the host network.
- I ran into this problem as well on my PE2950 w/ Win2k8 x64 and Broadcom NetXtreme II NICs. To resolve it open the Broadcom Advanced Control Suite and disable IPv4 Large Send Offload and your problem will be solved.
- Als Antwort vorgeschlagenBratac Freitag, 25. Juli 2008 15:11
TRAFSTA,
YOU HAVE NO IDEA, I have spent nearly 3 straight days working on this exact problem with Microsoft including a 14 hour phone call yesterday with a "Windows Server 2008", IIS & Networking specialists as well a 5 hour call today. After hours of doing multiple Network Monitoring captures and examining them I was finally asked to remove VirtualPC which solved the problem immediately without even having to restart the server and VirtualPC uninstalled in seconds. I reinstalled it without a restart and the problem comes back immediately. I then searched for the exact term "network trouble Windows Server 2008 Virtual PC 2007" and up came this post, your 2 sentence post at the bottom did for me what a half of dozen at Microsoft and another at Dell along with myself couldn’t figure out in hours upon hours.
Your SOLUTIONS worked for me. I’m saying that screaming because I hope it saves many other hours of aggravation as well.
Thank you - you are the man...
Marc
Your Post:
trafsta
Posts 8Re: Virtual PC 2007 on Server 2008 RC0 - Network trouble (Virtual Machine Network Services)
I ran into this problem as well on my PE2950 w/ Win2k8 x64 and Broadcom NetXtreme II NICs. To resolve it open the Broadcom Advanced Control Suite and disable IPv4 Large Send Offload and your problem will be solved.
- Als Antwort vorgeschlagenMadhu_Sify Mittwoch, 8. Juli 2009 16:06
One other comment, I wonder if this will make Hyper-V work on my server which that was 2 weeks of trying befor I gave up on it and tried VirtualPC only to find problems there. If anyone has had luck with Hyper-V on a Dell PE 1950 with Braodcom NetExtrem II's let me know as it would be nice to have my virtual server start up as a service and not have to log in to get it up and running.
Reagrds,
Marc
- where can i change this setting , i could not see it in bacs ?
- I also have been working on this issue: Asus P5K 2.4Ghz Quad CPU, 6Gb mem - Attansic L1 Gigabit enet 10/100/1000 attached to d-link di-624 with Verizon Fios
I also had trouble with the vlans - but co-worker told me - only use those when you have cisco vlans not at home. I saw this post and tried to turn off the IPv4 Large Send Offload - but that was not listed
on the nic connection but the VM Switch connection - I turned it off and saw some changes - the other virtual systems that were running started to appear and it found other systems on my home network - that had not happened yet (looking at the network host screen).
The error is that I cannot get an outbound connection to the internet from the virtual system - the host works fine and I can remote control into the vm - both the firewall on the host (win200864bit) and vm (win200864) are off. I also created a new vm with 200364bit and have the same network issues. I have tried to run repair but it says it cannot ping the dhcp - but it obviously has the correct information with ipconfig /all - dhcp provides an address and I can see it on the router. The mac address for the host and the virtual system are listed on the dlink router. The system will not ping the router but pings other systems.
Has anyone found anything else to change to get the outbound connections working within the virtual machine.
Thanks
Teleman
rmoos - Trafsta, your tip works perfectly :) :) :)
Thanks a lot ! ! ! - trafsta,
Just encountered this. You are a star! - Here's another thing TRAFSTA's solution fixes.
I have been experimenting with W2K8 Std and Ent for about a month. Trying to learn about HV. I have admin rights on the network but after a few days I can no longer log in with my user account. If I create a new admin account or use Administrator it works fine, although I never used those accounts long enough to see if they got cut off. Since I'm still in experimental mode I just used those accounts to instal and test various features and roles. Eventually I would just blow up the machine a do a reinstall.
Howevr, TRAFSTA's fix has solved the the account cut off problem.
Good job and thanks
West Just wanted to say thanks Trafsta. Since I have installed symantec endpoint security version 11, I would not be able to use RDP on server 2008. Uninstalling the software rectified the issue. I was getting an error (DRP - Because of an error in data encryption, this session will end. Please try connecting to the remote computer again). I searched hundreds of different forums and I am happy to find a solution here just on the second day of troubleshooting the issue. Many thanks!!
Hi
I have a similar problem. I've waded through this tread and it is all about Servers.
I have a user that from home is logged ion her XP-pro machine at work via VPN. This worked fine till this error appeared some 3 months back.
This is a simple external desktop login used by several users at my installation. And it works from XP Pro to XP Pro machines. Except the one machine.
Is there in this thread a simple fix for this problem?
Help would be appreciated.
I havae the error message, but it is Norwegian and wouldn't be much help. And there is no error message number.
RealPommyHi Again
I checked my card and there is now Advanced Flow Control. On the server yes.
I tried to Disable the flow control on the card built in Broadcom 440x 10/100 Integrated controller.
Rebooted and the same result. I put the flow control back on.
Now, I'm not getting the encryption error, just an error saying it you cannot connect. You can ping the machine. From the machine you can use the Remote Desktop to other machines and everything else works.
Any ideas?
Yours truly,
RealPommy- Thanks very much trafsta.
Almost a year avter you found a solution Dell, Broadcom, and Microsoft have still have not made changes to this "perfect storm" error.
I'm sending an email to my database vendor giving them a nudge to them to light a fire. They recomend a Dell 2900III with WS2K8. I don't know what sort of damage this would have caused to my data.
Regards,
PCOX007 - This fix seemed to work for me as well.
PowerEdge 840 with a broadcom Netextreme gigabit embedded
Driver Version 10.10.0.1
Windows 2008 Server running hyper-v
After many many many hours of troubleshooting, replacing cable modems routers, i reinstalled the OS.
It was only when hyper-v is installed that the trouble starts.
In my case it was only traffic over VPN that i had most trouble with. I had similar problem with Virtual Server on Server 2008 64-bit and Trafsta's solution appears to be working so far.
I am just curious how did you find this solution? I would really appreciate some insight on this.
I must admit, I doubt I would have reached this solution on my own and I consider myself really good :)I ran into this problem as well on my PE2950 w/ Win2k8 x64 and Broadcom NetXtreme II NICs. To resolve it open the Broadcom Advanced Control Suite and disable IPv4 Large Send Offload and your problem will be solved.
Your solution appears to be working for me so far.
I hope you give us some insight of how you arrived to this solution, which is not among the obvious.
lol I have no idea how I figured it out over a year ago. I totally forgot about this thread and that I had posted this resolution here. I likely found a forum post/thread about it via google, thats my guess...I had similar problem with Virtual Server on Server 2008 64-bit and Trafsta's solution appears to be working so far.
I am just curious how did you find this solution? I would really appreciate some insight on this.
I must admit, I doubt I would have reached this solution on my own and I consider myself really good :)
I just rediscovered this thread now while trying to get a similar issue resolved... when I try to do a "remote control" through "Terminal Services Manager" to 'shadow' a users terminal services session I immediately get disconnected as soon as the 'shadow' remote control session is started...
This started happening today after, which, coincidentally, is the day that I upgraded the servers to Windows Server 2008 SP2. I haven't used the shadow function in about a month so I am not sure if this problem started happening because of SP2 or not, but it used to work fine in the past...
The IPv4 Large Send Offload mysteriously was back on after I just checked the 3 servers (all running Hyper-V) so I disabled it and retried but the problem still exists. I will test it some more later, perhaps after a server reboot... hmmm
If anyone has any ideas on how I might fix this I would be much obliged, google hasn't turned up any results (perhaps because service pack 2 for Windows Server 2008 is still relatively new).
The error I get on the client's remote desktop (terminal services) session right after accepting the shadow (remote control) request is:
Title: "Remote Desktop Disconnected"
"Your Remote Desktop session has ended."
"Your network administrator might have ended the connection. Try connecting again, or contact technical support for assistance"- After a reboot everything worked again (meaning it was the IPv4 offload, just needed a reboot for the changes to take effect on the Hyper-V Win2k8 x64/x86 virtual server clients).
EDIT: Well I tried it out again this morning, and it is once again not working, the session gets terminated right after the shadow session is accepted by the user.
Strange thing is it works in some situations, and in others it does not. For example, if I remote desktop in connect from one system, and then shadow it, it works. From another, it does not. So it seems to be a client related issue (somehow?!), not a server side issue...
I'll report back if I ever figure this one out... so far I am totally stumped... - I had a similar problem with IBM x3550 server installed with Windows 2008 x64. I have a similar Broadcom NetXtreme II NICs in the server. Your suggestion has really helped me in solving my problem within seconds.My Sincere Thanks to you !!!!!
- "To resolve it open the Broadcom Advanced Control Suite and disable IPv4 Large Send Offload and your problem will be solved".
I just have to say "THANK YOU". I discovered this problem about 3 hours ago, and it was causing endless problems and stopping me from being able to do my job.
This saved my bacon.
Thanks Again!
