PXE Boot Issues
-
Actually, I read further into this thread (should have from the start)…
Why would an ISP control your internal DHCP? Are you [B]sure[/B]?
Or, is it just the home office that is running DHCP?
On a windows client, you can find out exactly where DHCP is coming from:
[CODE]ipconfig /all[/CODE]
There is a line item just for the DHCP server:
[IMG]http://i.stack.imgur.com/5ikMH.jpg[/IMG]
You can then take that IP and do a reverse lookup to give you a [U]name[/U].
[CODE]nslookup x.x.x.x[/CODE]
Sample output:
[IMG]http://files.cyberciti.biz/uploads/faq/2010/12/windows-nslookup-reverse-lookup.png[/IMG]
-
[quote=“Wayne Workman, post: 44027, member: 28155”]Actually, I read further into this thread (should have from the start)…
Why would an ISP control your internal DHCP? Are you [B]sure[/B]?
Or, is it just the home office that is running DHCP?
On a windows client, you can find out exactly where DHCP is coming from:
[CODE]ipconfig /all[/CODE]
There is a line item just for the DHCP server:
[IMG]http://i.stack.imgur.com/5ikMH.jpg[/IMG]
You can then take that IP and do a reverse lookup to give you a [U]name[/U].
[CODE]nslookup x.x.x.x[/CODE]
Sample output:
[IMG]http://files.cyberciti.biz/uploads/faq/2010/12/windows-nslookup-reverse-lookup.png[/IMG][/quote]
Hi Wayne,
My DHCP is run at the ISP’s site and under their control. Yes, I am sure. I know it seems odd and strange. It is.
You have no idea how much I don’t like this. Every time our connection to the ISP goes down (which is often in a third world country), I can’t even print on a printer on my LAN because the routing can’t be figured out anymore.Per your suggestion, I have done the ipconfig and so forth.
The address shown for the DHCP is not on my network. It is the ISP’s domain. Really, it is.
Screen prints here:
[ATTACH=full]1790[/ATTACH][url=“/_imported_xf_attachments/1/1790_dhcp info.jpg?:”]dhcp info.jpg[/url]
-
Well, that’s a whole new story but would you be interested to get rid of this dependency from your ISP? I don’t say that you should change your ISP but you could do DHCP yourself (using the exact same addresses) and ignore the external DHCP traffic completely. Feel free to start a conversation on this with me and we should be able to set this up for you…
-
[quote=“Uncle Frank, post: 44034, member: 28116”]Well, that’s a whole new story but would you be interested to get rid of this dependency from your ISP? I don’t say that you should change your ISP but you could do DHCP yourself (using the exact same addresses) and ignore the external DHCP traffic completely. Feel free to start a conversation on this with me and we should be able to set this up for you…[/quote]
Tom, the SVN version seems to be working. I haven’t done a truly scientific analysis, but I think we are consistently not having the problem. The few times it has blown past to Windows I think are due to a loose or bad Ethernet cable. If I remain on this SVN version, will I be cut off (orphaned) from regular product updates to Fog?
Uncle Frank, I am interested in the idea of running my own DHCP. From my perspective, I wouldn’t feel like I needed to use the exact same IP addresses, unless that is a requirement for your plan? I wouldn’t be able to shut down the ISP’s DHCP. So, whatever we did would have to be something I could completely affect / setup / configure from my side, on my own. The ISP is staff and service are worthless, at best.
-
[quote=“mkstreet, post: 44037, member: 24215”]Tom, the SVN version seems to be working. I haven’t done a truly scientific analysis, but I think we are consistently not having the problem. The few times it has blown past to Windows I think are due to a loose or bad Ethernet cable. If I remain on this SVN version, will I be cut off (orphaned) from regular product updates to Fog?
Uncle Frank, I am interested in the idea of running my own DHCP. From my perspective, I wouldn’t feel like I needed to use the exact same IP addresses, unless that is a requirement for your plan? I wouldn’t be able to shut down the ISP’s DHCP. So, whatever we did would have to be something I could completely affect / setup / configure from my side, on my own. The ISP is staff and service are worthless, at best.[/quote]
I think that Uncle Frank is planning on helping you configure your router & switches to block their DHCP altogether. It’s easily doable. Then, you can just set your own up (or let FOG handle it).
Also, you can upgrade from one SVN revision to another without any issues. I do it sometimes at my work.
Also, one more thing… Just want to see how far away your DHCP server is; out of pure curiosity…
[CODE]tracert 1.179.130.137[/CODE]
That will tell you how many routers are between your host & the DHCP server. -
[quote=“mkstreet, post: 44037, member: 24215”]If I remain on this SVN version, will I be cut off (orphaned) from regular product updates to Fog?
[/quote]SVN versions are almost always built one on top of another in a linear fashion. upgrading from a lower SVN to a higher SVN, or to a release version newer than your current SVN version, is almost always going to be possible. However, downgrades are not supported. Make sure you have backups or a snapshot you can revert to in case you have problems.
-
[quote=“Wayne Workman, post: 44051, member: 28155”]I think that Uncle Frank is planning on helping you configure your router & switches to block their DHCP altogether. It’s easily doable. Then, you can just set your own up (or let FOG handle it).
Also, you can upgrade from one SVN revision to another without any issues. I do it sometimes at my work.
Also, one more thing… Just want to see how far away your DHCP server is; out of pure curiosity…
[CODE]tracert 1.179.130.137[/CODE]
That will tell you how many routers are between your host & the DHCP server.[/quote]Hi Wayne,
I will run the tracert when I get back to the office in the morning, but I can pretty much tell you from memory what it will say.
It’s like this… the PC on my desk (for example) is 192.168.1.32.
Our LAN has a router box at 192.168.1.1 and that is local to me, though I cannot really do anything or affect it.
192.168.1.1 connects directly to 1.179.130.137 which is at the ISP’s central office for our area. -
Sorry for the delay… here is the tracert.
I believe the configuration is like this…
my pc (192.168.1.xxx) --> our gateway (192.168.1.1) --------> long cable ----> ISP’s box (1.179.130.137)
That 1.179.130.137 is the first box, our connection, at the ISP’s site.
[url=“/_imported_xf_attachments/1/1901_tracert.jpg?:”]tracert.jpg[/url]
-
Wow, you made it back!
And I find the “long cable” to be quite funny.
So, you have 2 options for getting FOG working on your network.
Option 1, try dnsmasq. [url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server[/url]
Option 2, block the ISP’s DHCP and run your own.
Either option is as viable as the other. If you’ve got access to your gateway, I’d recommend blocking the DHCP and running your own.
dnsmasq is something I could help you with setting up. You’ll find the walk-through above quite useful.Basically, dnsmasq just gives additional information to clients that ask for IP config from DHCP. Nothing to it really. You could get that going in a morning probably. Others would need to help you with blocking the ISP’s DHCP if you choose that route.
-
Sorry it took so long. We’ve been on new year’s holiday here for a couple weeks. But this week its blazing hot – like 40+ degrees – so we all want to stay inside with aircon and work.
Thanks for your reply. Uncle Frank has pointed out ProxyDHCP to me… I will look into that.
