I have been playing with a test box (Dell OptiPlex 170L w/ 512 ram & 60gig of hdd). I have Ubuntu 10.04 and FOG 0.32 installed with all updates and have been imaging machines fine over the past few months.

Since the testing has gone so good I purchased a new box to increase my storage and speed. It has an Intel mATX LGA 1155 motherboard w 4gig ram. I started off with Ubuntu 11.x but had all sorts of trouble with the video card so I moved to 10.4 and the video has been fine, however the on-board nic did not work w/ 10.4 so I dropped a Netgear nic and things are fine now.

The problem that I am having is across the board with all my machines. When I PXE boot they are all getting:
PXE-E11 - ARP Timeout
PXE-E11 - ARP Timeout
PXE-E38 - TFTP Cannot open connection

I can point them back to the old fog server and everything works great. I have tried everything that I have been able to find on-line from the Ubuntu group, FOG group, Spiceworks group, Google over the past 9 days with no avail.

I can schedule a task on the FOG server such as inventory and the client machine receives the command and displays the message on the client machine and will reboot to perform the command but then I receive:
PXE-E11 - ARP Timeout
PXE-E11 - ARP Timeout
PXE-E38 - TFTP Cannot open connection

The client is now in a loop trying to do the task at hand until I delete the task on the FOG server.

I am in a domain environment using DHCP from the domain controller. Option 66 & 67 are correct (which work fine on the old server). I have added Option 60 ClassID PXEClient and Option 43 Vendor Specific Info 01 04 00 00 00 00 ff based upon a good many sites but still nothing.

I am able to ping, TFTP, and connect to the FOG webserver on the new box from any machine. I have verified that my user names and password are all synced.

Any help would be great appreciated.

Basically 0 Linux knowledge on my side so please forgive my ignorance, but I am trying

Looking through the Wireshark packets the first time I did not see anything that just stood out. Then when Mike asked "what exactly do you see…", I went back in and noticed that the ARP (request) in the "Target IP address" had the old IP of my test machine.
With that information I went to my DC to verify all the information for DHCP (options 66, 67) which were correct. BUT when I check my secondary DC option 66 still had the old IP. Corrected the entry on secondary DC and the test machine started its scheduled task.

10 Replies

I would probably lay odds that it's the network driver on the ubuntu box. If you have another NIC I would probably try that or try to get a later version of ubuntu running. There is normally loads of good information on the net about installing linux of various hardware.

Try googling linux and the exact model of your dell and then try ubuntu and the model of your dell. You will probably find loads of usful information.

Thank you for your reply - I have tried additionl nics in the system. I just did not mention all of them. I defaulted back to a 3Com 3C905-TX-M and received the same errors. Thinking the 3Com card was too old I tried an Intel card with the same results. So this past Friday I went out and purchased the NetGear GA311. With all three cards I receive the same errors.

The nic worked on Ubuntu11.10 however the video did not thus the reason for going down to 10.4. I have been unable to find the driver for the video for this MB, but I will keep looking for it.

1st Post

No everything is wide open. I can move the wire to the old machine it everything works fine.

I bet it's driving you wild. With linux when it works it is excellent ! but when it doesn't its flipping frustrating beyond belief !

Do you have a spare video card? Also I think that sometimes in the bios you can change settings on built in video (e.g. legacy support options) that might help. It is probably better going for a later version of linux rather than earlier ones especially with the next LTS edition of ubuntu around the corner and it's likely that if you get it working you will be using it for years.

"I bet it's driving you wild. With linux when it works it is excellent ! but when it doesn't its flipping frustrating beyond belief !", truer words have never been spoken.

Im currently moving my ubuntu fog box, onto more reliable hardware and will be attempting to virtualize it, as I have had so many updates etc take down for, I want to be able role back in the future when this happens.

You could always try putting it on a different distro, it might play better with your hardware?

I was having issues getting the virtual stuff last week, im sure someone who knew more about linux wouldn't of have had a problem, but with time not on my side, I called it quits and started trying different distros eventually I found one that just worked straight away with no hassle.

Update - I have gotten the video drivers to work on a 11.10 build of Ubuntu. I wiped the server and did a fresh install and nic and video are working fine. I did a new install of FOG 0.32 and I am still getting these errors:

I have beat my head against the wall to the point the blocks are starting to chip away and I don't think my head can handle many more. I am a one man shop so this setup is really going to help if I can just get it working. Since I have spent the past week and a half on this I am starting to get behind on other things so I have got to find a solution.

Leif2251 - what did you finally get to work? My test machine I had up and working in about 45 minutes - this one . . . .

It was virtualization I finally got to work, I could not xen or kvm to work with opensuse and centos (A lot might be due to me not having any experience with it) in the interest of time with virtaulbox, wouldnt work again on the prementioned distros, then tried vitual box again on unbuntu on it worked like a charm. Not related to you, the point was different distros might work. Anyway back to a solution, Im preety sure this has come up before and yep it has

Looking through the Wireshark packets the first time I did not see anything that just stood out. Then when Mike asked "what exactly do you see…", I went back in and noticed that the ARP (request) in the "Target IP address" had the old IP of my test machine.
With that information I went to my DC to verify all the information for DHCP (options 66, 67) which were correct. BUT when I check my secondary DC option 66 still had the old IP. Corrected the entry on secondary DC and the test machine started its scheduled task.

Thanks for everyones help!

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.