Network Boot Problems/Computer won't communicate with Ubuntu/FOG
-
What are you seeing in the pxeboot sequence?
-
That the computer can’t find FOG. It says that it is booting from PXE and it waits for a bit then goes back to booting to the HDD
-
Did you set the PXE boot options in the DHCP ? I had an issue like this at a remote site were I put in one IP address for boot server and its IP was not set to a static address and it got rebooted and pulled another IP which caused the other computer to stop PXE booting.
-
This is what it says:
[ATTACH=full]170[/ATTACH][url=“/_imported_xf_attachments/0/170_2012-09-08 17.17.45.jpg?:”]2012-09-08 17.17.45.jpg[/url]
-
The FOG server does have a static address of 10.0.175.162. Do I make a FOG server a DHCP server? So the FOG server gives each machine an IP?
I am new at this
Thanks for the help
-
Do you have another device that is a DHCP server? This could be a computer, router/firewall just depends on how your network is set up.
-
Our main Novell server setup as DHCP…This is in a school with about 5 48port switches. Could this be the problem. And the firewall is unblocked on the FOG server…
-
Did you set the options for all the DHCP scopes? Because if they are not all the same some computers won’t know anything about the PXE server. Also with 5 switches are you forwarding DHCP request? Is your network flat or do you have Vlans that separate the network? Sorry just trying to get a handle on how your network is configured.
-
Oh gosh…
I have no idea.
The switches have a static address and as far as I know the switch gives the computers a DHCP address.
How do I check if my FOG server is giving the address’s?
I would assume the switches give the computers an IP address, so why can’t the computer find the FOG server when I boot from the NIC?
-
Well First you need to figure out what is giving out DHCP addresses on your network. Unless you configured FOG to handle DHCP it more than likely is not doing it. Go to the command line on one of the computers and do an ipconfig /all and look for the DHCP server line and it should tell you the IP address of your DHCP server. Once you have that its part of the DHCP config that hands our the boot server IP and the pxelinux.0 file on boot.
-
Here we go
[url=“/_imported_xf_attachments/0/172_ip.JPG?:”]ip.JPG[/url]
-
What device is 10.0.0.2? I would think it was your router as its your default gateway too. You need to configure the DHCP scope with the boot server IP and the pxelinux.0 file to get them to PXE boot.
-
I agree with djm79. Find out what that device is and if it supports dhcp options for next server and boot file name. If the device doesn’t support the options or you just can’t change its configuration, there is always proxydhcp.
-
I think it is our CipaFilter(so the students don’t go on naughty sites). And it does support DHCP every computer in the school has a DHCP address with the exception of the teacher computers, they are unblocked
-
Who manages that device? Get the to add the dhcp options for next-server and boot filename.
-
Our Network Administrator.
What do we have to change in the CIPA Filter to get it to work?
-
[QUOTE] Get them to add the dhcp options for next-server and boot filename.[/QUOTE]
-
OK. I will let Administrator know. Thanks for the help
If he says that’s not the problem, then what??
-
Bonk him on the head or get a new administrator?
You can only have one DHCP server in a subnet, otherwise they enter a race condition to see who answers first, and you can get IP address lease overlaps. So FOG cannot be the DHCP server if any other device is doing DHCP.
If you cannot, or will not modify your existing DHCP server to give out the required PXE boot options, then you can implement ProxyDHCP. ProxyDHCP does not give addresses, but listens for DHCP requests that need PXE boot information and responds with the necessary data, without interfering with your existing DHCP server.
-
I have no idea what OS is on the CIPA Filter and sniffing around on the web makes it seem to me that it’s a linux based proprietary OS.
If you can get to a dhcpd.conf file on it the options you would be looking for would be as follows:
next-server 10.0.175.162;
filename “pxelinux.0”;Note the filename end of .0 is a zero.
If you find you can’t get to it then you could use proxydhcp as chad-bisd suggested… which you can run from your fog server.