+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 17
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 ...
  1. #1

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,737
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505

    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.

    Any ideas?

  2. #2
    Crispin's Avatar
    Join Date
    Dec 2008
    Location
    Essex
    Posts
    361
    Thank Post
    76
    Thanked 28 Times in 25 Posts
    Rep Power
    20
    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.

  3. #3

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,737
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505
    Quote Originally Posted by Crispin View Post
    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.

  4. #4

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,737
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505
    Guess I could have missed something in the answer file so something is not right in mini-setup?

  5. #5

    Join Date
    Dec 2006
    Location
    Preston, Lancashire
    Posts
    126
    Thank Post
    13
    Thanked 12 Times in 11 Posts
    Rep Power
    18
    That would be my guess. Prob best to not add the ans file & see how it goes when you run through mini setup manually.

  6. Thanks to f21970 from:

    sparkeh (26th June 2009)

  7. #6
    morganw's Avatar
    Join Date
    Apr 2009
    Location
    Cambridge
    Posts
    816
    Thank Post
    46
    Thanked 132 Times in 126 Posts
    Rep Power
    39
    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.

  8. Thanks to morganw from:

    sparkeh (26th June 2009)

  9. #7

    Join Date
    Aug 2005
    Location
    London
    Posts
    3,154
    Thank Post
    114
    Thanked 527 Times in 450 Posts
    Blog Entries
    2
    Rep Power
    123
    Might just be worth doing a reset of the IP settings:
    Code:
    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.

  10. Thanks to srochford from:

    sparkeh (26th June 2009)

  11. #8

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,737
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505
    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

    Quote Originally Posted by morganw View Post
    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.

    Quote Originally Posted by morganw View Post
    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.

    Quote Originally Posted by morganw View Post
    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.

  12. #9

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,737
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505
    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.

  13. #10

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,737
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505
    Static IP address can't connect to network either

  14. #11

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    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.

  15. Thanks to Michael from:

    sparkeh (30th June 2009)

  16. #12

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,737
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505
    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.

  17. #13

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,568 Times in 1,250 Posts
    Rep Power
    340
    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.

  18. #14

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,737
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505
    Quote Originally Posted by Michael View Post
    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!

  19. #15
    box_l's Avatar
    Join Date
    May 2007
    Location
    Herefordshire
    Posts
    427
    Thank Post
    68
    Thanked 90 Times in 75 Posts
    Rep Power
    61
    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
    Last edited by box_l; 30th June 2009 at 11:22 PM. Reason: added link

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Imaging (or not!)
    By chrbb in forum How do you do....it?
    Replies: 23
    Last Post: 19th June 2009, 11:10 AM
  2. imaging problem
    By lionsl2005 in forum Windows
    Replies: 5
    Last Post: 16th June 2009, 03:41 PM
  3. Imaging Machines
    By MatthewL in forum O/S Deployment
    Replies: 28
    Last Post: 15th December 2008, 07:21 PM
  4. Station Imaging And Network Traffic Saturation
    By DaveP in forum Wireless Networks
    Replies: 10
    Last Post: 31st January 2007, 09:35 PM
  5. Imaging onto network
    By witch in forum Hardware
    Replies: 32
    Last Post: 10th July 2006, 12:04 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •