Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[random404]

This probably isn't a DNS 323 question, but perhaps someone has done the same thing with their DNS 323 and might now how to fix this.

I plug my DNS 323 directly into my computer using an ethernet crossover cable. I also access the internet from my computer using wireless. For some reason, when I'm plugged in directly and the DNS 323 is on, I can't access the internet through wireless. The wireless connection still shows as active and connected, but nothing downloads/uploads from the internet.

I've set up a static IP address on the DNS 323, and set the IP address of my computer's ethernet interface to be on that same private network.

I'm using Windows XP. I don't know what other information I could give that might help explain what's going on, but it's a really weird problem. Has anyone else had it, or does anyone know what I could do to fix it so I can be plugged into my DNS 323 and be access the internet over wireless at the same time?

[scaramanga]

You need to set-up you XP to be a network bridge. It's also called ICS - Internet Connection Sharing:
http://www.practicallynetworked.com/sharing/xp_ics/networkbridge.htm

[fordem]

I strongly suggest you fix the root problem rather that attempt a rube goldberg style work around using ICS - and for what it's worth ICS does not setup the computer to be a "network bridge", it turns it into a rudimentary NAT router/DHCP server.

If you have two network interfaces in your computer, they should be on two different networks - for example 192.168.0.x & 192.168.1.x, and only one of them should have a default gateway entry (in your case the wireless one).

The network connection you are using for the DNS-323 needs only an ip address and subnet mask, no DNS server entries and no default gateway entry.

[random404]

Thanks guys. I went with the solution of fordem, simple and it works!

Just for my own curiosity, could you explain why the network connection shouldn't have a DNS server entry and default gateway entry? Is this why I can't do a 'ping google.com' through a telnet connection to the DNS 323?

Is a 'network bridge' the only way to be able to accomplish that (I asked that question a while back and that's what was suggested). Is there a way to be able to access the internet from the DNS 323 with a direct ethernet connection but using fordem's simple solution (i.e. no network bridge). I'm using newbie reasoning here lol

Thanks.

[fordem]

The direct ethernet connection should not have a DNS entry because there is no DNS server on that network and no gateway through which it can reach another network to contact a DNS server, it should not have a default gateway entry because it has no gateway throughh which it can reach another network.

You can't ping www.google.com from the DNS-323 because the DNS-323 cannot reach a DNS server and therefore cannot resolve the name to it's ip address, and even if it could, it is on an isolated network with no access to the internet and is therefore unable to reach www.google.com.

A network bridge is a device tha links two networks together.  Since I have no knowledge of how your wireless internet service is setup, I would strongly recommend that you do NOT attempt to bridge your "private LAN" to the wireless connection - there are significant security implications.

Using ICS - as suggested by Scaramanga - would allow your DNS-323 to reach the internet using your computer's wireless connection, but would not allow access from the internet to the DNS-323 (for example use as an ftp server), and would require your computer to be on at any time the DNS-323 was required to have internet access, making use of the DNS-323's internal features (for example bit-torrent) somewhat redundant - if you have to leave the computer on you might as well use it to download the torrent.