| Mailing List os2-wireless_users@2rosenthals.com Archived Message #3926 |
back to list |
|
|---|
Hmm, may I remind you, before you bothering all, I already have done the obvious, that is:Actually, your wireless adapter is lan1 (according to the data you posted from netstat), so the command should be:
just the Artem driver in the config.sys
just in setup.cmd: dhcpstrt -i lan0 and the loopback etc.
Should have worked, shouldn't it?Well, assuming the correct interface is specified, yes, it should.
But the answer was "dhcp server didn't get parameters".Which again leads me to believe that this is software-related (somewhere), and probably in the DHCP client and not the router (good news, actually).
The same exercise with the Genprism drivers do give exactly the same result ""dhcp server didn't get parameters".
It is always like that when dhcp is set to a wireless lanx (jacaranda). OTOH, dhcp works as it should when set to a wired lanx (onboard intel nic).
I have checked with Frank Vos, he has exactly the same card as I have, and at his Laptop, a T23 IIRC, DHCP is working with Artem drivers as well as with Genprism (remember, Artem drivers don't work here at all, except for the flashing lights).
I still wonder whether the internal wireless nic (intel) of my T41 couldn't be in the game. After all, there is no option in the bios to disable the intel onboard nic. Meaning it is always powered on. A radiating device that is powered on, always radiates, doesn't it?You're obviously able to connect with a ststic address, so there's no interference from the internal card. As IP isn't bound to the internal card (for obvious reasons), it can't be interfering with obtaining an address. The router obviously doesn't see the card, either.
|
Subscribe: Feed,
Digest,
Index. Unsubscribe Mail to ListMaster |