Wrt54g v8 router not working

I am trying to use the wrt54g router. I have spent hours and hours on the phone with linksys, and finally got it to connect to my dsl. Now when I go to the internet, the msn page will come up, but if you try to go anywhere it sits in limbo. Maybe if I left it overnight it would come up! My dsl works fine if I plug it directly into the computer and not through the router. The dsl is a msn broadband dsl 1000, through qwest. Any ideas?

connect the computer to the router's port#1 .. access the router using http://192.168.1.1 .. the default password is admin
on the ui , change the "internet connection type" to PPPoE. Enter the username and password as provided by the ISP ..
click on the "mac add clone" subtab , enable it and click clone..save the settings and do a power cycle...
connect the modem to the router's internet port..do a power cycle..check whether it connects to the internet..

Similar Messages

Switched from DSL to CABLE. WRT54G Wireless Router stopped working.

When I switched from DSL to CABLE, my WRT54G Wireless Router stopped working. I am not able to access the router page (192.168.1.1) Also, when I use the set up CD for re-installation, the wizard aborts in the middle saying it can not connect.
I appreciate any help to resolve this problem.
P.S. The router acts like a one-port wired router.

Here is my favorite method for resetting a router to factory defaults, and trying to get it working again.
To reset your router to factory defaults, use the following procedure:
1) Power down all computers, the router, and the modem, and unplug them from the wall.
2) Disconnect all wires from the router.
3) Power up the router and allow it to fully boot (1-2 minutes).
4) Press and hold the reset button for 30 seconds, then release it, then let the router reset and reboot (2-3 minutes).
5) Power down the router.
6) Connect one computer by wire to port 1 on the router (NOT to the internet port).
7) Power up the router and allow it to fully boot (1-2 minutes).
8) Power up the computer (if the computer has a wireless card, make sure it is off).
9) Try to ping the router. To do this, click the "Start" button > All Programs > Accessories > Command Prompt. A black DOS box will appear. Enter the following: "ping 192.168.1.1" (no quotes), and hit the Enter key. You will see 3 or 4 lines that start either with "Reply from ... " or "Request timed out." If you see "Reply from ...", your computer has found your router.
10) Open your browser and point it to 192.168.1.1. This will take you to your router's login page. Leave the user name blank, and in the password field, enter "admin" (with no quotes). This will take you to your router setup page. Note the version number of your firmware (usually listed near upper right corner of screen). Exit your browser.
If you get this far without problems, try the setup disk (or setup the router manually, if you prefer), and see if you can get your router setup and working.
If you cannot get "Reply from ..." in step 9 above, your router is dead.
If you get a reply in step 9, but cannot complete step 10, then either your router is dead or the firmware is corrupt. In this case, use the Linksys tftp.exe program to try to reload your router with the latest firmware. After reloading the firmware, repeat the above procedure starting with step 1.
If you need additional help, please state your ISP, the make and model of your modem, your router's firmware version, and the results of steps 9 and 10. Also, if you get any error messages, copy them exactly and report back.
Please let me know how things turn out for you.

Linksys WRT54G Wireless-G Router Not working

I have a Linksys WRT54G Wireless-G Router and it has worked good for a couple months and yesterday it stopped. When I plug it in all the lights are lit even though there arent any ethernet cables connected and the power light blinks constantly. I tried holding the reset button on the back and it didnt help. Anyone know whats wrong or anything I can try to fix it?

You need to try again to reset the router to factory defaults.
To reset your router to factory defaults, use the following procedure:
1) Power down all computers, the router, and the modem, and unplug them from the wall.
2) Disconnect all wires from the router.
3) Power up the router and allow it to fully boot (1-2 minutes).
4) Press and hold the reset button for 30 seconds, then release it, then let the router reset and reboot (2-3 minutes).
5) Power down the router.
6) Connect one computer by wire to port 1 on the router (NOT to the internet port).
7) Power up the router and allow it to fully boot (1-2 minutes).
8) Power up the computer (if the computer has a wireless card, make sure it is off).
9) Try to ping the router. To do this, click the "Start" button > All Programs > Accessories > Command Prompt. A black DOS box will appear. Enter the following: "ping 192.168.1.1" (no quotes), and hit the Enter key. You will see 3 or 4 lines that start either with "Reply from ... " or "Request timed out." If you see "Reply from ...", your computer has found your router.
10) Open your browser and point it to 192.168.1.1. This will take you to your router's login page. Leave the user name blank, and in the password field, enter "admin" (with no quotes). This will take you to your router setup page. Note the version number of your firmware (usually listed near upper right corner of screen). Exit your browser.
If you get this far without problems, try the setup disk (or setup the router manually, if you prefer), and see if you can get your router setup and working.
If you cannot get "Reply from ..." in step 9 above, your router is dead.
If you get a reply in step 9, but cannot complete step 10, then either your router is dead or the firmware is corrupt. In this case, use the Linksys tftp.exe program to try to reload your router with the latest firmware. After reloading the firmware, repeat the above procedure starting with step 1.
If you need additional help, please state your ISP, the make and model of your modem, your router's firmware version, and the results of steps 9 and 10. Also, if you get any error messages, copy them exactly and report back.
Please let me know how things turn out for you.

Back To My Mac to a Time Capsule through a 3Com Router not working

I have a Mac Book Pro (10.5.7), Time Capsule (7.4.1), 3Com Office Connect Wireless Router (3CRWDR101A-75), a trial subscription to Mobile Me and a 2.5G iPhone (2.2.1).
I have been unable to get BTTM from my Mac on a remote wireless connection to my Time Capsule working - hence this post.
The set up of the Time Capsule was quite straightforward (as I would have expected from Apple) and I quickly established local and remote iCal / Address Book sync between my Mac, www.me.com and my iPhone. I have enabled and am the 2.4 and 5GHz bands on the Time Capsule and the wireless air interface on the 3Com router has been turned off. All of internet and email services on my Mac work well locally and Time Machine work. So far so good.
However, I am unable to 'see' my Time Capsule in Finder from any WiFi network that is not my home network. When at home I have full access to Time Capsule's disk.
My 3Com Office Router 3CRWDR101A-75 is not on the list of supported routers (nor is any other 3Com Router) but it does provide UPnP and NAT as required according to Mobile Sync notes including http://support.apple.com/kb/HT1552 and http://support.apple.com/kb/HT1552. Despite my best efforts, I have been unable to find out from Apple's MobileMe support if there are any minimum requirements for any router to work with Back To My Mac so can't check to see if my 3Com router will ever work with BTTM or not.
Does anyone have any similar experience with setting up a 3Com Office Connect router to work with Back to My Mac?
Do I need to check / Can I check if my Time Capsule has been registered with the Mobile Me servers?
Do I need to enable any specific ports on my 3Com Office Connect router?
Basic settings:
Time Capsule: green light - all OK
AirPort Utility>Internet: Connection Sharing: Off (Bridge Mode)
AirPort Utility>Advanced>Mobile me: account set up
AirPort Utility>Advanced>IPv6: IPv6 mode = Node, at the request of Apple Mobile Me support
System Preferences>Mobile Me>BackToMy Mac: On (green light).
3Com Office Connect Router: DCHP server: On
3Com Office Connect Router: Firewall level: High (default)
3Com Office Connect Router: Disable NAT: Off (default)
3Com Office Connect Router: Enable Universal Plug & Play: On
3Com Office Connect Router: Enable IPSEC-NAT pass through: ON, at the request of Apple Mobile me support
Com Office Connect Router: DMZ: enable 1-to-1 NAT: Off (default)
Any ideas?
Thanks.

Quick update on troubleshooting BTTM (or rather Back To My Time Capsule)...
Surprising;y, no 3Com products listed in http://support.apple.com/kb/TS1304. 3Com tech support stated that no OfficeConnect products have been qualified against BTTM and my specific router does not support IPv6 over IPv4 encapsulation.
MobileMe support were not able to help, citing the fact that I had an unsupported router.
I have made no change to my modem/router config since first posted but since an upgrade of my TC to 7.4.2 I have been able to use BTTM with my TC (bridge mode) and my OfficeConnect modem/router (802.11b WiFi disabled).
I have made limited testing from other remote locations from my MBP and also proved that it worked over a 3G/UMTS connection on the UK's 02 network also
MobileMe still reporting uPnP / NAT problem on my MBP when working remotely though.
http://discussions.apple.com/message.jspa?messageID=9733258 confirms that this has been solved and, apart from the anomalous Mobileme status message, I can agree.
Good news so now do not need to swap out my 3Com router. Also shows that this 3Com product does meet BTTM connectivity requirements.
Message was edited by: Elise49
Message was edited by: Elise49

ISE version 1.3 and static route not working

This command works without any issues with ISE version 1.1 and 1.2:
ip route 192.168.1.1 255.255.255.255 gateway 127.0.0.1
However, it does NOT work in ISE version 1.3. See below:
ciscoisedev/admin(config)# ip route 192.168.1.1 255.255.255.255 gateway 127.0.0.1
% Warning: Could not find outgoing interface for gateway 127.0.0.1 while trying to add the route.
% Error: Error adding static route.
ciscoisedev/admin(config)#
Any ideas anyone?

So it appears that there is no option to lock down access to the shell now that the command that you used to use is no longer valid. What is worse is that there isn't an option to create an ACL in the shell that you could attach to the interface. So I would recommend that you create a defect with Cisco TAC and get this re-added or request that ACL functionality is added.
For the GUI (in case you were not already aware of this), you can restrict access from Administration > Admin Access > Settings > Access > IP Access

Why is my router not working for my PS3, PSP, anymore and why isn't it working for my iPod touch?

I have the Linksys WRT54G wireless router, and for a while now it has worked well for my desktop computer, my sister's laptop, my PS3 and my PSP. Recently I got an Ipod touch and tried to set up my wireless connection and nothing worked, so I checked on my PS3 and PSP and they aren't connecting either. It always says something like exchanging key information, and still doesn't work. I'm getting very aggravated, I've reset the router several times and nothing. Keep in mind that my desktop computer, and my sister's laptop still works just fine, all the others devices don't work anymore. What can I do to fix this?

Upgrade the firmware on the router to the latest one and then set up WEP security on the router and change wireless channel to 11.

WRT54GS V7 suddenly not working

Perhaps it was internally damaged during my long, recent move Basically, 1. trying to access the router from my connected computer using the 192.168.1,x wont work 2. using the manual reset button on the back wont work. it doesnt have any effect 3. pressing down the orange button on the front has no effect either any suggestions are greatly appreciated - thank you

Hi,
You might need to check on the power adapter of your router. When I moved from my hometown to Oregon, I setup my old router. I was worried that my router was not working properly at that time. My router acted pretty strange power light blinking and computers were not connecting. I tried reset, ping but still it is working.
I even tried assigning static ip on the pc and forced the card speed to 10 half duplex of my Ethernet. I was doing all these troubleshooting steps only to find out that I used the incorrect power adapter for my router.
This silly incident happened to me. I laughed at myself because my power adapters are all mixed up when I moved.

WRT54GS v6 "router not supported"

My router has been working fine for months and now when I try and setup my home network it tells me "router not supported". I've tried the reset thing for 30 secs, power on, power off, hold my tongue right and still nothing. I'm about to throw it out the door.
Can anyone help me out with this please?

You need to re-configure your router...
If your Internet Service Providor is Cable click here
If your Internet Service Providor is DSL click here

WRT54G Port forwarding not working

Ok this is an odd problem. Ever since I got this router I have had issues with the port forwarding.
I am forwarding 3389 TCP to 192.168.1.101 check box is enabled. The .101 address is given out by DHCP ( only set to give out 4 IPs). The forwarding did not work at all. I have configured dozens and doezens of routers with no issues except this one . It is Version 8. After a lot of reading on the net someone posted a similar issue where they could not forward ports to static IP addresses ONLY IP's given out in the DHCP range. Strange? yes you bet. So I decided to try it and sure enough I changed my 2 internal computer IP's to use DHCP and forwarded the ports to the IP of the computer I wanted ( 192.168.1.101) and it worked! How silly is that, it wouldn;t forward to static IP's. Well now the problem is back. Except this time if I forward to static IP's OR IP's given out in DHCP nothing works. As a test I moved the .101 computer into the DMZ and still nothing. This is beyond annoying. problem is this is sitting at a clients house in another city and I only have access to it via the web admin. I tried backing up the configuration and then restoring it. The restore worked but didn't fix my issue. I still can't get the forwarding to work. Resetting the defaults is not really an option cause I am not in the same city as the router.
I have about 7 other SMC routers that have been working happily for 5 years straights. Why is this thing so mental? I did upgrade to the latest firmware before installing the router. Ayone have any suggestions as to why the forward doesn't work?.
By the way I enabled the logs and watch them as I was trying to remote into the computer ( 3389) and sure enough it's hitting the router ok as it shows up in the logs. The web server is not working either, nothing is getting forwarded.
No there are no firewalls at all installed on the computer I am trying forward to. Can anyone shed some light on this?

Access router setup page ...uncheck block WAN request under security tab .... also check the updated firmware on the router ....

Safari routing not working

Hello all,
I have a very strange problem and I'm looking for suggestions. Recently, I tried using my work place VNP which I log into using a web browser. This event seemed to have completely broken safari.
At first I thought it was my routing table, but when I check it with netstat -ar, it looks ok. Nother weird. My other applications are still working (mail, iChat). Opera works correctly too, but Safari always tells me that I am not connected to the internet. I have tried restarting and Resetting Safari but so far that does not work. I searched my disk using spotlight for all the files that changed today and got rid of the safari related files but this does not work either.
It's a very strange problem and I'm looking for suggestions on what else to try.
Thank you in advance.

You're welcome. Sometimes the little things can be the most confounding.
Thanks for the and Aloha from Big Island.

WRT54G 3.1; Not Working

I am having problems with my wireless router (WRT54G 3.1). I was able to work on my computer from home with no problems. Today, I'm unable to connect to my wireless connection. I tried to Easy Connect to reinstall and I get an error message that my wireless router isn't supported. I am able to connect to the internet via the DSL (Cable) modem. How do I get my router to work? Do I need to reconfigure? Any assistance is greatly appreciated.

first off , configure the DSL modem in a bridge mode...then connect the router and set up a PPPoE connection on the router...you need to know the username and password from the ISP in order to set up a PPPoE connection on the router...

Wireless router not working

I have a WRT54G Wireless-G Broadband Router. I know next to nothing about computers. The router has worked fine, broadcasting signals to two other computers for over a year. But suddenly last night it stopped working for one computer, and then 30 minutes later it stopped working for the other. Neither computer could find the signal.
I went to the 192.168.1.1 website and found that some settings had changed. I restored the Network Name (SSID) and the WEP key. After that, one of the wireless computers could "see" the signal. But I still can't connect to the internet on either wireless computer.
Does anyone have any suggestions?

What error message you are getting while connecting to the wireless network....?
Which operating system you are using on the computer...?
Make sure that you are typing the correct security key on the computer..If you are using WEP then,use Key1 as the security/network key.The security key is case sensitive.
Message Edited by Wizzard on 02-19-2010 07:13 AM

Wireless router not working after Windows update

I have a WRT54G V.5 wireless router. Windows Vista Home Premium did an auto update. Now wired connection works, wireless does not. Asks for key, but when entered nothing happens. Diagnosis states action was canceled. I have disabled and enabled, does not fix. Any help will be appreciated!
Solved!
Go to Solution.

Take not of the Wireless Settings(SSID and WEP/WPA Key) on your Router...
To know the Wireless Settings follow this link
Once you know the Wireless Settings attempt to connect to your Wireless Network...
XP :
Click on Start and goto the Control Panel and double click on Network Connections, right click on Wireless Network Connection and click on Properties.
Now on this window, click on the second tab Wireless Network and give a check mark on "Use windows to configure my wireless" and then remove all the network names present in the Preferred Networks Window. Then click on OK...
Right click on the Wireless Network Connection again and click on View Available Wireless Networks and try to re-connect to your network...
Now it will give you the opportunity to put the network/wep key, make sure you enter the correct network key and confirm it...
It will connect...
Vista :
Click Start >> Control Panel >> Network and Sharing Center >> Manage Wireless Networks, here remove all the networks present and close the Window...
Click on Connect to a Network and try to re-connect to your Network, it should ask for your Network Key/Password, enter the correct password/network key and click Connect...
It should connect...Once you are connected you should restart the computer, it should connect to Internet...

Dual nat instance in an router (not working)

Hi Guys,
I'm having a problem w/ the design i'm currently working on. As you can see in the diagram below, I was trying to somehow perform load balancing on WAN links. What I'm trying to do is basically for all VLAN 1 users to use the WAN 1 link as their primary wan connection while VLAN 2 users must use WAN 2 link as their primary wan connection. To achieve this, I've configure a PBR on each subinterfaces on my router indicating that VLAN 1 subnet must use the WAN1 as next-hop and VLAN 2 subnet must use WAN2 as next hop for their respective WAN traffics.
In relationship to my PBR configurations, I've also included "track" command to monitor whether each WAN link still active. Everything works fine until I've defined two "ip nat inside" command on my router. I noticed that only one vlan subnet could communicate on WAN. I don't know if there's an effect for using two NAT instance on the router.
Hope you could help me on this.
Thank you so much
Rex

A lot of the 960's don't have 2 DVI's. However most have an additional HDMI and DisplayPort. I recommend you get an adapter from amazon or something. Just make sure that it will convert HDMI or DP to DVI. Usually amazon products have a good amount
of questions already answered by buyers.
Interesting that they'd go that route, I guess I just assumed since my 760 has two.
I've set up dual monitors using one DVI and one HDMI before, but I ran into issues with screen sizing. Despite having two identical monitors set at the same resolution the mouse would not transmit over to the second monitor at the same height as it was on
the first, so I had to buy an adapter like Joshua suggested.

Dynamic Routing Not Working

I'm attempting to use dynamic routing (Dynamic Routing Action) to route to another proxy service and I keep getting "BEA-382000: Error preparing message for dispatch".
I'm using a lookup table:
<routingTable>
<route>
<relative-uri>/destination_1</relative-uri>
<route-to>DestinationOne</route-to>
</route>
<route>
<relative-uri>/destination_2</relative-uri>
<route-to>DestinationTwo</route-to>
</route>
</routingTable>
"DestinationOne" and "DestinationTwo" are local protocol proxy services that reside in two different projects.
To get the correct route-to value, my XQuery statement is:
routingTable/route/route-to[../relative-uri='{relative_uri}']
and I know it works.
At this point, the first proxy service (the one that does the routing) does nothing but use content from the $inbound variable to lookup the route-to information.
What am I missing?
Many thanks,
-Mark

We do this often.
I'm sure it can happen in other ways, but I see the error you're describing commonly in two scenarios:
1. An error occurred in the second proxy but you don't have an error-handler on that proxy (I've found it really helps to make sure there is an error handler on every proxy that at least logs the $fault and then does Reply with Success, otherwise ALSB sometimes loses the fault details). I think I usually get a BEA-38000 in that case, not a 38200, but off the top of my head I'm not sure.
2. If an AnySOAP proxy is calling an AnyXml proxy, I get this error. Recently we switched out endpoint to AnySOAP, and I had to go through and recreate all of the proxies to AnySOAP because previously they'd been AnyXml. Even adding error-handling to every possible level didn't give me any better details, I just happened to try the Any SOAP switch on one proxy and learned it fixed the error.
Hope that helps you track it down, at least there are some examples of what causes this error.
Meghan

Wrt54g v8 router not working

Similar Messages

Maybe you are looking for