/images/DellLatitudeE7440/ contains four files: d1.mbr, d1p1.img, d1p2.img, d1p3.img… I’m guessing that’s the master boot record and the three partitions on disk 1. Looks about the right size.

Just have to install a printer and I’ll PM you when I’m ready!

Maybe try adding a link on the fog server.

I’m assuming the /images directory is no longer available on that server, so you could try it like this:
[code]ln -s /media/ImageDisk /images[/code]

Then check to see if all is working.

After searching through the interface for the EA6400, it doesn’t appear to support PXE boot options. Just use DNSMasq as Jaymes advised. It will let your Linksys router serve DHCP, and just respond with PXE Boot information to those clients that request it, such as next server name and boot file name, no IP info.

Also, I assume Steam is up to date. Steam had an known issue mid to late last year that caused orphan files in many systems. They released an update that resolved the issue and cleaned up after its self.

[quote=“Tom Elliott, post: 22094, member: 7271”]This particular issue seems to me a problem with the switching equipment. Maybe you had a broadcast storm (a switch with a cable that plugged back into the switch forming a loop) and sending all the data in the wrong direction on the network. I’d start be removing as many variables as you can. Take that system and a mini switch and plug the fog server nic directly into the switch. Connect the computer to the switch and try imaging.[/quote]

Tom, I’ll see what I can come up with…it will be difficult for me to take it all completely off the network without totally building out a new lab type environment with dhcp, new fog server, etc. I can’t think of anything as far as the network goes that has changed all that much in the last 8-9 months but my sense is you are probably right with it being some quirky network issue.

I’ll keep digging and see what I can figure out.

Problem is solved!

I have updated the kernel (Other Information - Kernel Updates - 3.8.8 Core) and reverted the settings in /etc/exports and now the image is running …

Thnx very much for the advice!

It’s not the XP but the mini-Linux which is not working in 15.2.
I get this error:
[IMG]http://i61.tinypic.com/smru9t.png[/IMG]

If I summarizes, the NFS server export “/images” on FOG server and FOG Server export “/images” on Client, it’s correct?

It would seem I have nfs-common installed:

root@fogserver:~# locate nfs-common
/etc/default/nfs-common
/usr/share/nfs-common
/usr/share/bug/nfs-common
/usr/share/bug/nfs-common/control
/usr/share/bug/nfs-common/script
/usr/share/doc/nfs-common
/usr/share/doc/nfs-common/README.Debian.nfsv4
/usr/share/doc/nfs-common/changelog.Debian.gz
/usr/share/doc/nfs-common/copyright
/usr/share/lintian/overrides/nfs-common
/usr/share/nfs-common/conffiles
/usr/share/nfs-common/conffiles/idmapd.conf
/usr/share/nfs-common/conffiles/nfs-common.default
/var/cache/apt/archives/nfs-common_1%3a1.2.5-3ubuntu3.1_amd64.deb
/var/lib/dpkg/info/nfs-common.conffiles
/var/lib/dpkg/info/nfs-common.list
/var/lib/dpkg/info/nfs-common.md5sums
/var/lib/dpkg/info/nfs-common.postinst
/var/lib/dpkg/info/nfs-common.postrm
/var/lib/dpkg/info/nfs-common.preinst
/var/lib/dpkg/info/nfs-common.prerm
/var/lib/ucf/cache/:etc:default:nfs-common
root@fogserver:~#

But none in /etc/init.d. There is one in /etc/default, is this the one i’m looking for?

Did you ever figure this out?

If you have many of the same model of client, have you considered using the capone plug in for this.
You can associate a particular model with one (or more) image.
On the client you select capone from the menu choices, if there is only one image associated, it deploys with no registration required.
If there is more than one image associated, you select which one you want, and again it deploys, again no registration required.

This is my last day at this location. Giving up on this and moving on. Thanks to everyone who offered assistance along the way.

I think I see what you were referring to and have made the change, the next update will reflect this. Currently testing/fixing snapin deploys though so may be a minute.

And I thought this worked in 0.32.

What sort of code change are we talking about? The feature would be nice, but is not critical.

In windows, you need to configure the card. You can either go through device manager or network and sharing center, change adapter settings, properties of the NIC, click the “configure” button just below the “connect using” box. It may be on the advanced or power management tab.

“Wake on LAN” “Wake system from S5” “Allow this device to wake the computer” or similar. There may be other choices about only allow magic packet, just depending on the card and the driver.

If you’re using the default driver installed by Windows, your choices may be more limited. Try to get the board/chipset specific driver for the LAN card from the manufacturer.