On Wednesday 12 October 2005 21:46, Ian Marlier wrote:
(Note: this is assuming a static IP setup. If you're letting Linksys' DHCP server touch the client, things get all messy.)
So, you imply that the LinkSys DHCP server is doing more than dishing out IP addresses in the range that I specify? I've only got three computers, so I could just go all-static, but I thought that if I specified static addresses for some computers, outside the range allowed for DHCP, then the DHCP server would ignore the computers that had the static addresses. Is there something else that it diddles besides just numeric IP addresses?
Why not try an experiment?
First, configure a computer with DHCP and see what works. Then, change to static config, including default route & DNS and see if everything still works.
Because I'm not entirely sure what "see what works" and "see if everything still works" actually refers to. I'm browsing freely, and KMail can get and send mail to/from my ISP. Those two functions work fine with _either_ static or dynamic addresses on the PCs, as long as I ensure that the static addresses are outside the range that the LinkSys thinks it owns for dynamic allocation (learned that the hard way just a couple of days ago). Other than that, I'm not sure I _have_ anything working that I could try under the two addressing regimes. I have not yet started configuring fetchmail and IMAP, or Samba... which is why I question your "everything", above... there is no "everything" yet, to "still work". :-) Tonight, perhaps, I'll spend a couple of hours and a ton of calories dashing up and downstairs as I try to get the two SuSE machines seeing each other's files via Samba. I probably won't get so adventurous as to boot the wife's system into Windows 98 and see if _that_ works with a Samba server. That fountain of disappointment can wait for another night. Assuming I haven't goofed something while sniffing about the Samba stuff, I'll spend part of the weekend futzing with the e-mail server stuff and trying to read mail on it from my old iBook. Yes, I know that this stuff is all pretty well bullet-proof, and to most people it's as simple and natural as breathing. But I have a talent for misinterpreting. When it's applied, it puts up obstacles that other people wouldn't even think could exist, because it would never occur to them to interpret a term or an instruction the way that I did. Keeps life... interesting. Kevin The information contained in this electronic mail transmission may be privileged and confidential, and therefore, protected from disclosure. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer without copying or disclosing it.
mlist@safenet-inc.com wrote:
On Wednesday 12 October 2005 21:46, Ian Marlier wrote:
(Note: this is assuming a static IP setup. If you're letting Linksys' DHCP server touch the client, things get all messy.)
So, you imply that the LinkSys DHCP server is doing more than dishing out IP addresses in the range that I specify? I've only got three computers, so I could just go all-static, but I thought that if I specified static addresses for some computers, outside the range allowed for DHCP, then the DHCP server would ignore the computers that had the static addresses. Is there something else that it diddles besides just numeric IP addresses? Why not try an experiment?
First, configure a computer with DHCP and see what works. Then, change to static config, including default route & DNS and see if everything still works.
Because I'm not entirely sure what "see what works" and "see if everything still works" actually refers to.
I'm browsing freely, and KMail can get and send mail to/from my ISP. Those two functions work fine with _either_ static or dynamic addresses on the PCs, as long as I ensure that the static addresses are outside the range that the LinkSys thinks it owns for dynamic allocation (learned that the hard way just a couple of days ago). Other than that, I'm not sure I _have_ anything working that I could try under the two addressing regimes.
I assume that when you're using DHCP, you can connect to the internet, using host names, instead of IP addresses. This means that both default route and DNS configurations are OK. Make note of both of those, and use them when configuring a static address. Then verify you can still get to the internet. Incidentally, some firwall/routers allow you to permantently assign a DHCP address to a computer.
participants (2)
-
James Knott -
mlist＠safenet-inc.com