• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Can't connect to wireless bridge

eflat

Platinum Member
So here is the setup:

Linksys WET 54G v. 3.1 Wireless bridge ---> netgear switch --- > PC and MAC

Using the PC setup guide, it never finds the bridge.

All the correct lights are on both the bridge and wireless bridge so it appears that everything is working fine. Except that it does not work..
 
Don't you have to configure the bridge( put in the ssid, network security type, security key or pass phase)?
 
You have to explain better.

Wireless source?

What is wired and what is Wireless?

What is providing the IPs?
 
Originally posted by: JackMDS
You have to expiain better.

Wireless source?

What is wired and what is Wireless?

What is providind the IPs?

OK. Lets see:

Wireless source: Router in living room connected to internet and used via wifi throughout the house.

Three computers are wired together in a separate room via Gigabit Lan and a linksys switch (this is all wired but not configured). These are the ones I am trying to provide with internet and Ethernet through the switch.


As for the IP's, I'm ignorant. We have Comcast cable internet connected to the main router.

 
First You have to connect the WET to a single computer and configure it to match the Wireless Network.

Put it on a single computer that has a static IP that is on the same subnet as the default IP of the WET.

Connect to the WER and configure it to match the Wireless Network.

 
Originally posted by: JackMDS
First You have to connect the WEP to a single computer and configure it to match the Wireless Network.

Put it on a single computer that has a static IP that is on the same subnet as the default IP of the WEP.

Connect to the WEP and configure it to match the Wireless Network.

:Q

Do you know of any good networking guides that could help translate that?
 
These were the install directions:

Configuring the bridge to join an existing 802.11g network is easy and takes about five minutes. Just attach the device via Ethernet to a computer or hub on your network, load the accompanying CD into your computer, and let the CD's installation wizard take over.
 
A typical private IP would be 192.168.x.y

The X is the subnet number. E.g. all computers and network devices that have an IP 192.168.1.y (y=0 to 255) are on the same network subnet.

All Linksys instructions assume that you are using Linksys devices which are configured with the same subnet.

You did not mentioned the model of your main Router. So assuming that it is Not on Subnet 192.168.1.y


However, if your Main Router IP is (example) 192.168.0.1 and the WET default IP is 192.168.1.226 they cannot talk since they are on a different subnets.

In such case the IP of the WET has to be change (example) to 192.168.0.10
You have start with a single computer that have a static IP of 192.168.1.1 log to the WET and change the core IP.

Linksys support is here, http://www.linksys.com/servlet...per&lid=0122345678B517

P.S Figure 7-2 on page 23 of the pdf manual shows the menu thta let you configure the WEY core static IP.
 
OK, well they all do have an IP address of 192.168.1.y

When I plug the bridge into the router I can get to the configuration page by going to 192.168.1.226:80

Not really sure what to do from there. Can I do this over wireless or do I need to connect my computer via Ethernet to the main router as well?
 
OK I'm stumped:

Do I select Auto Config - DHCP

or enter a static IP address?

I notice my notebook connects via DHCP - don't know if that matters.


And then what do I do about security? Does the network type and password have to be the same one used on the existing wireless network?

The default gateway is 192.168.1.1 by the way.


And I keep doing something that causes an IP conflict and shuts down the entire network.



Man this is such a pain in the ass I swear it would be less work to tear down the walls and run Ethernet cable through the house.
 
Back
Top