O/S Deployment Thread, No network after imaging in Technical; I am trying to deploy an image, built in Virtualbox, to an NEC Powermate VL350 using FOG.
The image appears ...
25th June 2009, 06:40 PM #1
No network after imaging
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.
25th June 2009, 07:10 PM #2
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.
25th June 2009, 07:29 PM #3
Yeah reinstalled drivers, both the version that was on the machine before it was imaged and the latest version. Same effect.
Originally Posted by Crispin
25th June 2009, 08:55 PM #4
Guess I could have missed something in the answer file so something is not right in mini-setup?
25th June 2009, 09:13 PM #5
- Rep Power
That would be my guess. Prob best to not add the ans file & see how it goes when you run through mini setup manually.
25th June 2009, 09:16 PM #6
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.
25th June 2009, 09:20 PM #7
Might just be worth doing a reset of the IP settings:
The logfile contains lots of info which is probably not helpful but this has fixed a few odd problems for me in the past.
netsh int ip reset resetlog.txt
Thanks to srochford from:
26th June 2009, 10:42 AM #8
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
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.
Originally Posted by morganw
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
Originally Posted by morganw
Will also try imaging the physical machine.
Yeah that was my thinking. I have the machine saved just before sysprep so its dead easy to restore, make changes, sysprep again.
Originally Posted by morganw
30th June 2009, 11:29 AM #9
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.
30th June 2009, 12:18 PM #10
Static IP address can't connect to network either
30th June 2009, 02:02 PM #11
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.
30th June 2009, 02:41 PM #12
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.
30th June 2009, 06:11 PM #13
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.
30th June 2009, 08:43 PM #14
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.
Originally Posted by Michael
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!
1st July 2009, 12:19 AM #15
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!
Last edited by box_l; 1st July 2009 at 12:22 AM.
Reason: added link
By chrbb in forum How do you do....it?
Last Post: 19th June 2009, 12:10 PM
By lionsl2005 in forum Windows
Last Post: 16th June 2009, 04:41 PM
By MatthewL in forum O/S Deployment
Last Post: 15th December 2008, 08:21 PM
By DaveP in forum Wireless Networks
Last Post: 31st January 2007, 10:35 PM
By witch in forum Hardware
Last Post: 10th July 2006, 01:04 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)