PXE Server
 

Anyone know how to configure one?

Yes.

Sweet.


This is my problem. I am an IT guy here at school, and we are trying to set up a pxe server for ghost. There is a main dhcp server for the school, and the labs that I am working with is on its own subnet. Is there a way to get the labs to talk to a pxe server on the same subnet?

</smart a$$ mode>

Here's a link for OpenSUSE that is pretty close to what I have set up. Most of the stuff in there is not distribution specific. I'm running two PXE installation servers - one at home, one at work. Strictly Linux and DOS installs (for BIOS flashing purposes), but it's possible for Windows as well.

The trickiest part is the DHCP config, necessary to direct requests to the TFTP server. I can't comment on the method used in the article above, as my DHCP server is part of my firewall, and the setup is different. If you're interested in how to do it using m0n0wall, I can provide details on that setup.

I cannot change anything that has to do with the dhcp server. is it posible for me to install an application of a sort that just has authority over my given subnet? Like a tftp application?

I've run into this problem as well, as I use PXE at work for our Linux server installs. Normally it works fine. as we do the initial config on servers on the same subnet as the tftp proxy server. However, we've recently had an occasion to install OS's from a WAN site, on a different subnet - no worky as is.

No direct experience, but from what I've read, you need to tweak your DHCP server to forward the tftp request to the PXE server. If your DHCP server admins won't do this for you, I'm out of suggestions...short of running your own DHCP server, which will no doubt piss them off. :D

Whoops - replies crossed, ignore the DHCP info above.

You might be able to setup a tftp proxy server on your subnet, which would answer only to the PXE requests - thus, avoiding messing up the DHCP. Again, I've seen reference to this in the Linux world, but no direct experience setting it up.

would you be able to point me in this direction?


Also, thanks for you help!!!!


What part of No Cali are you in? I would be more than happy to buy you lunch if your around...

First, I mis-spoke - it's been a while since I set this up, and the terminology was being quoted mostly from memory. What you need is not a tftp proxy service, you need a DHCP proxy service. This is different than a DHCP server (although a DHCP server can perform the same function), and can co-exist with a DHCP server without messing up the "normal", non-PXE clients.

Do a Google search on "proxy dhcp server" - that should get you headed in the right direction.

Sorry, don't have much else for you. At work where I have a DHCP proxy configured, it's not something you likely have access to - Netware. And to make it worse (for you), the DHCP proxy service is a component of ZenWorks, a pricey product.

At home, I have no need for a dhcp proxy server, as I have control over the DHCP server, and have configured it to assign addresses and forward requests to the TFTP server for PXE hosts.

Bay Area...thanks for the offer, but nothing I wrote above really deserves it. Just paying back what little I can, having sucked free info out of others for years... :D

aHahahha. We had netware, and we got rid of it about a year ago...

Hey - I know it's hip to knock Netware, but many of us older-timers are getting a little misty-eyed watching it being retired. :D

I've supported it at work for the last 15 years. Netware and ZenWorks has served our 2,000+ users/PC's on 30 servers - we're on the small end of Novell installations. I can count unplanned downtime on one hand. With the exception of our other dinosaur (IBM mainframe), it's been far more stable and reliable than anything else in house - SGI's, HP-UX, Suns, Linux, and of course that other steaming pile of crap some people think is server-worthy.

And most importantly, all of the above has been managed by one full-time position. Our Exchange system takes 2.5 FTE's - for farkin' mail and calendering! And it's down more than Richard Lewis.

Our move to Linux is being driven by a few factors - none of them, having anything to do with reliability or feature set in Netware. First, it's getting very difficult to find folks like me who know the system - all the youngsters are Linux Heads, something I'm on board with. Most importantly, Novell has made it clear Linux is THEIR future...so it makes sense not to go down with the ship. And finally....Novell services are the real gem, Netware just sits underneath. With 99% of Novell's services ported over to Linux, we get the best of both worlds.

So listen up, you young whipper-snapper...don't be knockin' the platform that's made me look so good for the better part of my career. I just might have to come over, and smack you with my cane...:silly: