sparkeh Posted June 25, 2009 Posted June 25, 2009 I am trying to deploy an image, built in Virtualbox, to an NEC Powermate VL350 using FOG. The image appears to install fine and all drivers are installed correctly. However the NIC, a realtek 8169, can't get an address from DHCP. I think I can rule out the NIC as the issue as its works with a CD install and during the imaging process. It only refuses to work when imaged. So I guess its an issue with the image, perhaps something up with TCP/IP stack, but it works ok when deployed to other machines...so I'm scratching my head. Any ideas?
Crispin Posted June 25, 2009 Posted June 25, 2009 Have you tried reinstalling the NIC driver? I would build a basic image on a physical machine, image it and see if the same problem occurs.
sparkeh Posted June 25, 2009 Author Posted June 25, 2009 Have you tried reinstalling the NIC driver? I would build a basic image on a physical machine, image it and see if the same problem occurs. Yeah reinstalled drivers, both the version that was on the machine before it was imaged and the latest version. Same effect.
sparkeh Posted June 25, 2009 Author Posted June 25, 2009 Guess I could have missed something in the answer file so something is not right in mini-setup?
f21970 Posted June 25, 2009 Posted June 25, 2009 That would be my guess. Prob best to not add the ans file & see how it goes when you run through mini setup manually. 1
morganw Posted June 25, 2009 Posted June 25, 2009 What happens if you image to another instance of virtualbox? Does the networking work then? I've only ever made images on the actual hardware, I would guess that issue is down to the driver initally being installed on a fictional nic to start with. I've never considered building images on virtual machines before, i guess it's a good way to keep a library of pre-syspreped drive images though. 1
srochford Posted June 25, 2009 Posted June 25, 2009 Might just be worth doing a reset of the IP settings: netsh int ip reset resetlog.txt The logfile contains lots of info which is probably not helpful but this has fixed a few odd problems for me in the past. 1
sparkeh Posted June 26, 2009 Author Posted June 26, 2009 Thanks for the help guys, unfortunately I'm not in that school again for a bit - one of the downsides of working across multiple sites What happens if you image to another instance of virtualbox? Does the networking work then? Yes it does...which I guess rules out the answer file problem? But I will still try without an answer file to see what happens. I've only ever made images on the actual hardware, I would guess that issue is down to the driver initally being installed on a fictional nic to start with. Yeah I thought about that, but I would expect XP to find the new network card and install the drivers, which actually it does do, just won't get an IP. Should have tried a static IP Will also try imaging the physical machine. I've never considered building images on virtual machines before, i guess it's a good way to keep a library of pre-syspreped drive images though. Yeah that was my thinking. I have the machine saved just before sysprep so its dead easy to restore, make changes, sysprep again.
sparkeh Posted June 30, 2009 Author Posted June 30, 2009 Ok back on this now. I played around with the settings on the card (offload checksum etc) and it gets and ip address! Just for testing I reset the settings and alter them again and limited connectivity again. I am really tearing my hair out now.
sparkeh Posted June 30, 2009 Author Posted June 30, 2009 Static IP address can't connect to network either
Michael Posted June 30, 2009 Posted June 30, 2009 If you have a look in Device Manager, I presume the driver is loaded/installed correctly? I recently had a similar problem whereby a system would work in a Bart PE setup, but once imaging had complete and Mini Setup attemped to join the domain it failed. Looking in Device Manager, the network card had a question mark and was conflicting with another hardware device, which in the end I never managed to fix. I then disabled the onboard NIC and installed an Intel 10/100 card which worked perfectly. 1
sparkeh Posted June 30, 2009 Author Posted June 30, 2009 Thanks for the idea Micheal but nothing is awry in Device Manager. If I give it a static IP, it can ping its own IP address and access its own workgroup but cant see or ping any others machines on the network. Just running up a copy of xp on the machine in question to see what happens if I image it, then image it back.
Michael Posted June 30, 2009 Posted June 30, 2009 It sounds as though the driver is loaded, but something isn't quite right. Are you sure it's the same model/make of motherboard? It can vary sometimes when buying in batches. I've seen it happen before (co-incidentally with Realtek's) that an available driver gets loaded, but the actual model of the NIC varies by one digit 8168 or 8169. They do require a different set of drivers.
sparkeh Posted June 30, 2009 Author Posted June 30, 2009 It sounds as though the driver is loaded, but something isn't quite right. Are you sure it's the same model/make of motherboard? It can vary sometimes when buying in batches. I've seen it happen before (co-incidentally with Realtek's) that an available driver gets loaded, but the actual model of the NIC varies by one digit 8168 or 8169. They do require a different set of drivers. Another good idea, however I took the driver off the machine before it was imaged, and the same driver works when doing a straight install from CD. Anyway, thanks for everyones input but (and although I would love to get to the bottom of this) I have decided to call it a day with this as its taking too much time. I took an image from the physical machine rather than virtualbox and this is deploying correctly with the same drivers. Thanks again guys!
box_l Posted June 30, 2009 Posted June 30, 2009 (edited) i had this once, i had to to rebuild winsock to get it all ok again. cant remember the commands but ill look in my notes. it was this http://support.microsoft.com/kb/811259 check out microsofts "fixitforme" tools at the bottom of the page, very handy! BoX Edited June 30, 2009 by box_l added link
sparkeh Posted July 1, 2009 Author Posted July 1, 2009 i had this once, i had to to rebuild winsock to get it all ok again. Yeah, I did rebuild winsock as per the MS instructions, but no cigar. Thanks for the input though. Anyway I have gone back to physical machines rather than virtual. The benefit of doing it virtually was to quickly snap back to pre sysprep state, I mean it only takes about 2 mins to restore the physical machine but its seconds with virtual.
sparkeh Posted July 1, 2009 Author Posted July 1, 2009 Actually, one thing I have noticed, is that after using a physical machine to build the image, the imaged machine runs significantly faster than when using the virtual image, both booting and when logged in. I am wondering if there are more underlying problems and the NIC is a symptom.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now