| Mailing List os2-wireless_users@2rosenthals.com Archived Message #3923 |
back to list |
|
|---|
On 01/06/2005 05:36 pm, Kris Steenhaut thus wrote :As it is now yes. But I began the message with: "Prior to bothering you", remember? (incidentally, for some messages it took a weird long time before the appeared here).
<snip>
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.
dhcpstrt -i lan1
However, I don't think this will make a difference...The correct interface was specified indeed. To specify to correct interface, that's one of the few things within the scope of simple human beings.
Should have worked, shouldn't it?Well, assuming the correct interface is specified, yes, it should.
Which again leads me to believe that this is software-related (somewhere),
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).
and probably in the DHCP client and not the router (good news, actually).I think the router does see the card. If it were otherwise, there would be no way wlanstat could tell me "connected to SMC", couldn't it. (SMC is the router's SSID, in protoco.,ini just is stated "Any")
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 |