[SOLVED] Hyper-V Windows XP x64 Professional - Internet Connection

[AceInfinity]

I am unable to get an internet connection in HyperV for my XP setup for some reason. It's been a few years since I have done anything in XP, so even on that end, I am feeling a bit out of place. Even the legacy adapters don't seem to be working for me... :confused2:

So far I have Linux Mint, Windows 7, Windows 8, and Windows Server, in addition to the XP, but the only one I have had troubles with is this XP VM.

Edit: Okay I found this: myITforum.com : Windows XP x64 in Hyper-V - Network Drivers

Looks like I need to spend time setting Vista up first before I can do anything in XP x86-64. Time to wait an hour to download Vista ISO from MSDN, set it up, create an ISO containing the files so I can mount it and view from the XP VM, just to install the drivers. :thumbsup2:

 

[Digerati]

I was going to say you still need 64-bit drivers, as that edit link suggests - 64-bit drivers are often not easy to find for XP. Many legacy hardware makers never provided 64-bit drivers, and many new hardware makers don't provide any XP drivers (32 or 64-bit).

You say you cannot connect to the Internet, but in actuality, you cannot connect to your network, right? Your router is not seeing this NIC, thus will not assign an IP. Right? I wonder if you tried to install 32-bit XP instead of 64-bit if you could connect?

It's been a few years since I have done anything in XP, so even on that end, I am feeling a bit out of place.

Yeah, every time an XP system comes across my bench now, I stare at the screen wondering why it looks so foreign and "clunky" to me now. Then, once the cobwebs clear and I remember what to do, I agonize at how slow XP is. Amazing for an OS I was so happy with for so many years (I never migrated to Vista because XP with SP3 was so solid - and Vista sucked).

 

[Trouble]

Not sure what the actual problem might be that you are currently experiencing but I thought I would test, since I do love my Hyper-V.
So off I went to technet. Downloaded the ISO and installed into a new VM.
Then back to the internet to download SP2 for Windows XP Pro 64bit and installed as the Hyper-V integration service would not install with out SP2
Then installed the integration services and it just worked. No issues. And no work-arounds needed.

 

[cluberti]

You need a few things - one, you must have the correct Integration Components installed. Once you get those installed (assuming you do), you'll need the right driver from a Vista or 2008 install - I may have an install lying around I can grab from if you need it:
Working with Legacy NIC on Hyper-V with MDT - Venkat's Blog - Site Home - TechNet Blogs

Note that this is for the "legacy" NIC, which is less performant than the Synthetic NIC (the normal network card you use with Hyper-V), so unless there's a specific reason you need the legacy NIC, I wouldn't recommend using it (which would resolve this issue for you just by switching).

 

[AceInfinity]

I was going to say you still need 64-bit drivers, as that edit link suggests - 64-bit drivers are often not easy to find for XP. Many legacy hardware makers never provided 64-bit drivers, and many new hardware makers don't provide any XP drivers (32 or 64-bit).

You say you cannot connect to the Internet, but in actuality, you cannot connect to your network, right? Your router is not seeing this NIC, thus will not assign an IP. Right? I wonder if you tried to install 32-bit XP instead of 64-bit if you could connect?

It's been a few years since I have done anything in XP, so even on that end, I am feeling a bit out of place.

Yeah, every time an XP system comes across my bench now, I stare at the screen wondering why it looks so foreign and "clunky" to me now. Then, once the cobwebs clear and I remember what to do, I agonize at how slow XP is. Amazing for an OS I was so happy with for so many years (I never migrated to Vista because XP with SP3 was so solid - and Vista sucked).

Well, I guess I need to connect to my network to connect to the internet as I want to connect by bridging my ethernet connection to the VM environment, but true. :) I'm not a network guy though... So all the help I can get here is appreciated. I'm assuming that I probably could connect if I didn't install the x64 edition... As even as the article says, it's an issue with "x64" XP and "x64" Windows Server 2003? From what I can remember without looking again...

All the VM's I have installed so far are 64 bit versions of the OS itself, and all worked until yesterday.

Not sure what the actual problem might be that you are currently experiencing but I thought I would test, since I do love my Hyper-V.
So off I went to technet. Downloaded the ISO and installed into a new VM.
Then back to the internet to download SP2 for Windows XP Pro 64bit and installed as the Hyper-V integration service would not install with out SP2
Then installed the integration services and it just worked. No issues. And no work-arounds needed.

Hmm, I don't have SP2 I don't believe. So I definitely wouldn't have the integration service. Perhaps this will work for me, so I'll give it a test.

You need a few things - one, you must have the correct Integration Components installed. Once you get those installed (assuming you do), you'll need the right driver from a Vista or 2008 install - I may have an install lying around I can grab from if you need it:
Working with Legacy NIC on Hyper-V with MDT - Venkat's Blog - Site Home - TechNet Blogs

Note that this is for the "legacy" NIC, which is less performant than the Synthetic NIC (the normal network card you use with Hyper-V), so unless there's a specific reason you need the legacy NIC, I wouldn't recommend using it (which would resolve this issue for you just by switching).

Looks like I am already missing the first thing, without having SP2 yet... I wanted to do a real quick test on an XP machine, so I honestly can say that I didn't bother with installing updates or anything. I just wanted the OS on a core level to fiddle with... Looks like making a "shortcut" doesn't always suffice.

I'll give the suggestions a shot though as I don't see why they wouldn't work. Especially if Trouble has tested on a clean XP install for the same edition and through those steps it worked for him. Integration services is installed on my other main VM's though, but I seem silly now that I forgot it for XP.. :banghead:

 

[cluberti]

I have a set of XP and 2003 x64 VMs on a 2012 Hyper-V server that both work just fine, drivers and all, but yes - they must be at the SP2 level, and if you want to use the legacy NIC you must use Vista's x64 DEC drivers from an installed source. I would recommend XP x64 SP2 + Integration Components + regular (non-legacy) NIC and you will have no issues.

 

[AceInfinity]

I have a set of XP and 2003 x64 VMs on a 2012 Hyper-V server that both work just fine, drivers and all, but yes - they must be at the SP2 level, and if you want to use the legacy NIC you must use Vista's x64 DEC drivers from an installed source. I would recommend XP x64 SP2 + Integration Components + regular (non-legacy) NIC and you will have no issues.

Yes, that seems like the easiest route, and since I do not need SP1 to be testing on, I would say that I am willing to go with the SP2 + Integration services route. I'll probably end up with SP3 after some time on this VM anyways... But I have no need for SP1. Thanks!

You guys have all definitely helped me out.

:beerchug2:

 

[Trouble]

Especially if Trouble has tested on a clean XP install for the same edition and through those steps it worked for him.

Yes.... Installing service pack 2 was a little awkward as I had to download it and burn it to a CD and point the VM at my physical drive X:\WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe
but after that the Integration Services installed without issue and the network device passed from the host and everything was right with the world. No need to install any legacy NIC or anything. It just worked.
Hope it works for you as well.

NOTE: And there is no SP3 for the 64bit Version of XP Pro that I could find anywhere.

 

[cluberti]

Trouble beat me to it - no SP3 for XP x64 or 2003 x64. XP x64 is built off of the same codebase that 2003 x64 was built off of, and not XP x86. Thus, only SP2.

 

[AceInfinity]

Especially if Trouble has tested on a clean XP install for the same edition and through those steps it worked for him.

Yes.... Installing service pack 2 was a little awkward as I had to download it and burn it to a CD and point the VM at my physical drive X:\WindowsServer2003.WindowsXP-KB914961-SP2-x64-ENU.exe
but after that the Integration Services installed without issue and the network device passed from the host and everything was right with the world. No need to install any legacy NIC or anything. It just worked.
Hope it works for you as well.

NOTE: And there is no SP3 for the 64bit Version of XP Pro that I could find anywhere.

It must be because I haven't used XP in a few years...

That's exactly what I'm doing though. Except I am sparing a CD as I can just format the file for SP2 into an ISO and mount that lol. I think you wasted a CD there. :)

Trouble beat me to it - no SP3 for XP x64 or 2003 x64. XP x64 is built off of the same codebase that 2003 x64 was built off of, and not XP x86. Thus, only SP2.

Yeah, I don't know much about XP anymore which is apparent haha. SP2 will do however, It is being installed right now.

 

[Digerati]

I'm assuming that I probably could connect if I didn't install the x64 edition...

I was merely "guessing" that might be your problem based on the description of your problem. But I would not assume connection is a given with 32-bit. "Assume" is not a word I get along with very well.

 

[AceInfinity]

I'm assuming that I probably could connect if I didn't install the x64 edition...

I was merely "guessing" that might be your problem based on the description of your problem. But I would not assume connection is a given with 32-bit. "Assume" is not a word I get along with very well.

Well, "guessing" and "assumption" are almost in the same category when it boils down to definition :lol:. Although instead of sticking with an assumption the whole time, there may be a reason why I would need the x86 edition of XP, but at this point I only really want one XP VM on my HyperV, so it can only stay as a guess or an assumption until I do decide to see how it goes with XP 32 bit at a later date. Thanks for your help though! :thumbsup2:

~Ace

 

[Digerati]

Well, "guessing" and "assumption" are almost in the same category when it boils down to definition

Sorry, but no way does "assume" and "guess" have anything close to the same meaning. This is especially true when dealing with electron flow in circuits!

 

[AceInfinity]

Well, "guessing" and "assumption" are almost in the same category when it boils down to definition

Sorry, but no way does "assume" and "guess" have anything close to the same meaning. This is especially true when dealing with electron flow in circuits!

guess - definition of guess by the Free Online Dictionary, Thesaurus and Encyclopedia.

1. b. To assume, presume, or assert (a fact) without sufficient information.

"This is especially true when dealing with electron flow in circuits! " - If you didn't mean in a literal sense, then perhaps. :thumbsup2: I can understand how making a guess and making an assumption might be different for someone, but conceptually and not theoretically, these are closely related.

Whether it is in the definition or not however, like you, I too think they are somewhat different. Assumption sounds like a guess that someone has made which has turned to a "fact" somehow, whereas a guess might stay as a guess, and the person admitting making that guess may be more apt to understand that it is a guess and may not be fact by common logic.

:beerchug2:

 

[Trouble]

Interesting debate.
I kind of always thought that the words assume or assumption were more generally applied to or direct towards something more along the lines of an inference from someone else's implication and that a guess might be something that I might randomly generate on my own and not necessarily associated with any previous data. But that's just me.
I'm certainly glad that we got the Hyper-V issue resolved though.
I guess
Randy

 

[AceInfinity]

Interesting debate.
I kind of always thought that the words assume or assumption were more generally applied to or direct towards something more along the lines of an inference from someone else's implication and that a guess might be something that I might randomly generate on my own and not necessarily associated with any previous data. But that's just me.
I'm certainly glad that we got the Hyper-V issue resolved though.
I guess
Randy

Interesting point, I think this classifies an assumption as a specific type of a guess then as uncertainty is still involved, but less of it? And yes, this is solved. I got both XP and Vista working by attempting the suggestions above. Yours was the main one that solved it though, that's all I really did was install SP2 (no SP3 exists for x64 XP), and installed the HyperV Integration Service.

:beerchug2:

 

[Digerati]

But that's just me.

And me too. I might make a guess based on an assumption, but I would never assume based a guess. While guess, assume, take for granted, suppose, presume are often used interchangeably in informal speech, a good technician will never assume something is good, or guess that something is bad without verifying the facts.