| Your router's a DG834G, right? That's to say a wireless equipped version of the DG834. Do you have the WGE101 in infrastructure mode?
Firstly, I'd set the IP address of the WGE101 manually, to a unique address outside of the DHCP scope of your DG834G router. Leave the PC as automatically assigned. Restart the PC (or do an ipconfig /release then ipconfig /renew from a command prompt). See if your PC picks up an IP address then. The 169.<whatever> address is an APIPA (Automatic Private IP Addressing) address, which basically means "OK, I'm plugged in, but I can't see anyone handing out IP addresses, so I'll make one up". Your router should have an internal IP address which looks something like:
Address: 192.168.0.1
Subnet Mask: 255.255.255.0
Your gateway should have it's address set something like:
Address: 192.168.0.10
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
However, the docs for the DG834G indicate that the start of the default DHCP scope is .2 and goes all the way through to .254. If that's correct, it's dumb. Limit the DHCP scope to say .100 to .199. You are NEVER going to have more than a hundred devices hooked up to it, and that leaves you with everything from .2 through to .99 (and .200 to .254) available for static assignments (like for your bridge).
See whether your PC picks up an address in the correct range after that, and can ping your router. If so, great. If not, try setting its address manually (choose an address from the non-DHCP range as above that's different your gateway) and seeing if you can ping your router then.
|