Reply
larrycook99
Posts: 3
Registered: ‎01-15-2012

Problem getting WES610N to actually bridge

I recently bought a WES610N Bridge to allow me to connect a WD TV Live Hub to my network wirelessly. It has only an ethernet port and I did not want to run a cable 30-40 feet across several rooms (though I am beginning to rethink that). My network consists of: 1. Cable modem from ISP 2. Linksys BEFSX41 with a 16 port workgroup switch attached 3. WRT54G2 Router connected to the BEFSX41 being used as an access point to provide wireless capability with WPA-2 Personal security 4. WES610N talking to the WRT54G2 Currently the WRT54G2 and WES610N are talking to each other. From any computer connected to the network on the WRT54G2 side I can see both devices and access their web pages. The problem is that I cannot see anything that is connected to the ethernet ports on the WES610N. Devices that are connected to the WES610N can see each other but they cannot see or be seen by the rest of the network across the bridge-access port connection. I do not understand why. I do not see any settings that would seem to affect this on the WES610N which is where I assume the problems lies.
binky
Posts: 2,613
Registered: ‎09-07-2006

Re: Problem getting WES610N to actually bridge

What I understood from your post is that the computer connected to WRT54G2 is not able to see any device connected to the WES610N. Did you ever try to ping the IP address of the device connected to the WES610N. Inorder to check what IP address has been assigned by the router to the devices connected to the WES610N please click on the following link: http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=70ecb8dfd38e43308e615fbc0c30672b_17346.xml&pid=80&... If you are not able to ping the IP address of the device connected to the WES610N then try to ping the same IP address from the router. Open the router's setup page and click on the administration tab. Under that you will find a sub-tab that says diagnostics. Click on the box that says ping, enter the IP address on the box provided and then click on ping. If you get replies with some TTL values then the result is positive. To know more about pinging an IP address please click on the following link: http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=f557cb9b8e304b979cfb43aeb38054ca_KB_EN_v1.xml&pid=...
larrycook99
Posts: 3
Registered: ‎01-15-2012

Re: Problem getting WES610N to actually bridge

I cannot ping the WD Hub from either the BESX41 router or the WRT54G2.

 

Below is a diagram of the network:

 

Home Network.jpg

 

Note that in th eis configuration the laptop is essentially bridging the two segments that I want to bridge with the WES610N. It is attached to the WRT54G2 via wireless as 192.168.1.104 and it is attached to the WES610N via one of its ethernet ports. With that configuration I can move/copy files from 192.168.1.101 to 192.168.1.105, albeit very slowly. If I disconnect the laptop from the WES610N ethernet port, I have no path between 192.168.1.101 and 192.168.1.105, which is teh ultimate goal.

larrycook99
Posts: 3
Registered: ‎01-15-2012

Re: Problem getting WES610N to actually bridge

WES610N is now working and I am uncertain as to why.

 

After reading various posts about this bridge or that bridge not seeing both sides of the network, I decided to have the WD TV Hub try to get a new IP automatically and lo and behold, it worked. I don't know why it worked.

 

The one thing that comes to mind is that before I connected the WD TV Hub to the WES610N it had been connected to the network directly in anothe room so I could just play with it and the DHCP had set its IP then to 192.168.1.105 and when I moved it to the WES610N, I left the IP unchanged. Now that it is connected the DHCP gave it 192.168.1.109.

 

While I am glad it is connected I still want to know what may have happened just in case I get in that situation again.

 

 

musicmanohyeah
Posts: 179
Registered: ‎07-29-2010

Re: Problem getting WES610N to actually bridge

Some tech stuff needs to be rebooted for it to work.  Maybe the DHCP lease for the first time you hooked it up has already expired and you need to renew the IP lease.