Computer Learning Message Board

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

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: Guy Gadois who wrote (42573)	8/13/2004 1:51:34 PM
From: Graystone	Read Replies (1) 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 $.

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next