Link to home
Start Free TrialLog in
Avatar of Member_2_2667525
Member_2_2667525

asked on

Westell DSL modem w/ Linksys WAP

I am attempting to make a Linksys wireless access point router work with a Westell 6100 DSL modem and haven't been able to do it after countless hours (well, just ~8 hours).  One PC is connected to the router with an ethernet cable and another PC will eventually be connected via wireless.  The DSL modem is replacing a cable modem, with which the computer could access the Internet normally (through the router).  It was not difficult to make the computer able to access the Internet normally if I left the router out of the chain (i.e., computer directly connected to the DSL modem).

I made snapshots of the, hopefully, informative device configuration screens, which I put at http://www.trustworthycomputer.com/snapshots

The directions for making the modem and router work together basically just said to put the router into "Bridge" mode and turn the modem's DHCP off.  It didn't say anything about making the router have a static address, but I tried that anyway.

On my own I changed the IP address of the router to 192.168.1.2 because the modem and router both had 192.168.1.1 as their addresses.  That allowed the computer to ping the modem through the router--but http would not work.

Can anyone take a look at these screens and tell me how they should be set up so it will work?  Let me know if I have not provided enough information.

Thanks.
SOLUTION
Avatar of Rob Williams
Rob Williams
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Member_2_2667525
Member_2_2667525

ASKER

I understood much of the above already, but I tried a couple things prompted by your posts, but made no progress.  It got fixed by talking to tech support on the phone for 1.5 hours, going to factory default settings, and reconfiguring everything the way they said.  

I'm going to ask that this question be closed.  Thanks, guys.
Ah, after learning more about awarding points from a moderator, I am handing out the points to you guys.  The B grade is because neither answer led to a solution.  However I learned a tidbit of information from each of you that I didn't know before, and more importantly, you took the time to go review my screens, which I appreciate.  :-)
Thank you GJanusz ,
--Rob