Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Guy Gadois who wrote (42573)	8/13/2004 12:01:46 PM
From: shadowman	Read Replies (1) \| Respond to of 110653

Does this help? 64.233.161.104

To: Guy Gadois who wrote (42573)	8/13/2004 12:34:57 PM
From: Graystone	Read Replies (1) \| Respond to of 110653

169.254.nnn.nnn or DHCP Server Unavailable Hi jon The DHCP service is going to be a configuration option on the AEBS. You can use the winipcfg command in the Run box on your Dell to check your current setup and release/renew your IP requests. From the error description it sounds like your Dell has a properly configured network interface card. If the card is running properly it should obtain an address in the 169.254.nnn.nnn range, showing that everything is fine but no routable IP can be obtained because the NIC does not find the DHCP server. Check your Device Manager to make sure that the USB port is set up properly with no exception (no area with an Other Device heading and an unidentified device). Download the latest USB driver for the SB5100 for your Dell. Here is a link broadband.motorola.com Check you AEBS to make sure the DHCP is being served over the USB as well as the Ethernet, I am not familiar with the SB5100 but it should have an area to configure the USB port and the DHCP service. If you can use a USB device on your Dell then the problem will probably be with the SB5100, if you can't, it is your Dell. Early USB implementations were sometimes buggy in many laptops, like early IBM parallel ports configured to 3BC instead of 378, good luck jon.

To: Guy Gadois who wrote (42573)	8/13/2004 1:51:34 PM
From: Graystone	Read Replies (1) \| Respond to of 110653

Sorry jon or Bad advice I have just been out doing some work related tasks and I was thinking about the advice I gave you. Upon rethinking your problem I have come to the conclusion that you are likely SOL, it isn't going to work, buy another wireless card. It is probable that your provider is serving up a single IP to your SB5100 which in turn is being cloned to the WAN port of your AEBS. The Dell is being connected to the SB5100 directly via the USB, it is unlikely that a DHCP request incoming on the USB port will be transmitted to the Ethernet port on the same device (highly unlikely). You are probably getting 192.168 addresses for your home network but they are being served up by the AEBS, which your Dell cannot see or communicate with. Your DHCP request on the USB port is probably being ignored by the ISPs DHCP server because you have an assigned IP already, you may be able to pay a fee to the provider to allow a second IP address. It is probably cheaper to get a new wireless NIC for your Dell, it will then join the happy family of 192.168.nnn.nnn machines on your network. 192.168 addresses are non-routable which is an added level of security and your ISP cannot see them, so you cannot be charged extra $.