Wrt54g v3 network suddenly cannot ping/traceroute

I have a wireless network set up that has been up and running w/out problems for several years. After installing skype on a new machine (but one that had been successfully using my wireless network for 1+ week), I suddenly cannot resolve hosts.
Here are the details:
1) wrt54g v3 w/ latest firmware
2) secure network, non-broadcasting
3) been working for years
4) 2 different laptops on the network: both running windows XP & successfully using the network for some time
5) I just installed skype on the newer laptop & suddenly lost internet access
6) I can connect to the router and ping & traceroute successfully using the diagnostics tools on the router.
7) When trying to ping/traceroute the same addresses from the laptop, I cannot find the hosts.
8) The other laptop that I have not touched is experiencing the same problems.
9) I have power cycled everything (modem, router, laptops) multiple times to no avail.
Any help would be appreciated.
Thanks,
Jason

Well , you can try to reset the router and reconfigure it ..
1. Press and hold the reset button for 30 seconds.
2. Then, unplug the power keep holding down the reset button for
another 30 Seconds.
3. Plug back the power back in, and keep holding down the reset button
for 30 Seconds.
4. Release the reset button.

Similar Messages

Ospf in small network and cannot ping remote subnet

OSPF all interfaces would be network 0.0.0.0 255.255.255.255 area 0

Attached you can see a diagram of my small network. Both PC's can ping each interface on the router they are connected to. The two routers can ping each other. There are no acl or nat statements. All interfaces are up,up.All subnet masks are /24 unless identified as another.Using ospf, I wanted to advertise the all networks so the node on the left 192.168.2.50 can ping 192.168.3.50.On router4 I did:#router ospf 1#network 10.11.12.1 0.0.0.0 area 0On router5 I did the same but with network of 10.11.12.2Both routers took the ospf, but I still couldn't ping from laptop to laptop. I thought by doing those commands the other interfaces on the router would see the advertised network and would be able to route across it?
This topic first appeared in the Spiceworks Community

Cannot ping outside private network

I can currently ping my internal network, but cannot ping anything beyond
that. This is causing problems too because payroll need to connect via
dns name or ip address.
If someone can help.
Mike

That worked! Thank you!
Mike
> Mike,
>
> > When I go into inetcfg, the bindings for both cards are set to
dynamic.
> > Nothing has changed from when it was working until now.
>
> Make sure that in you've enabled Network address translation for the
> PUBLIC iP address only (10.x.x.x). This is in inetcfg/bindings/select
> the public IP address/go to expert bind options/network address
> translation and have it configured to Dynamic only.
> Also, in inetcfg/protocol/tcpip make sure that packet forwarding is
enabled.
> Try again with IPFLT unloaded and let me know.
>
>
> --
> Cat
> NSC Volunteer Sysop

Cannot ping by name

I have one system on my network that cannot ping any workstations or servers by name but can ping by IP Address. I get error Ping request could not find host tt-data. Please check the name and try again.
I tried the following troubleshooting steps but nothing fixed it
-Tried a static ip and dns address
-Added an entry in the host file and tried to ping the server name and it failed as I got same error as above
-Reinstalled network card driver as well as updated it
-Did an ipconfig /flushdns and ipconfig /registerdns
-Stop and Started Browser, Computer and DNS Client services
-Rebooted pc multiple times
-No errors in application or system logs
-Windows firewall service started but all profiles disabled
-Stopped windows firewall
-Cannot ping localhost
-netsh interface ipv4 reset
I am not sure what the issue is as I am stumpped as DNS is clearly not working but I do not understand why the host file entries are not working either when you ping by name but IP Addresses work fine. All other workstations work fine so it has to be something
on this machine.
Any assistance would be greatly appreciated.

Well you might follow the steps on this article to reset TCP/IP on the host, otherwise I am stumped.
http://support.microsoft.com/kb/299357
Use a manual method to reset TCP/IP for Windows Vista and Windows 7
Note This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, ask someone for help or contact Support. For information about how to contact Support, see the Microsoft Help and Support contact information
Web site:
http://support.microsoft.com/contactus
The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually:
To open a command prompt, click Start and then type CMD in the Search programs and files.
Right-click CMD.exe icon in Programs and choose Run as administrator.
When the User Account Control box pop up, click Yes.
At the command prompt, copy and paste (or type) the following command and then press ENTER:
netsh int ip reset c:\resetlog.txt
Note If you do not want to specify a directory path for the log file, use the following command:
netsh int ip reset resetlog.txt
Reboot the computer.
When you run the reset command, it rewrites two registry keys that are used by TCP/IP. This has the same result as removing and reinstalling the protocol. The reset command rewrites the following two registry keys:
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\
SYSTEM\CurrentControlSet\Services\DHCP\Parameters\
To run the manual command successfully, you must specify a file name for the log, in which the actions that netsh takes will be recorded. When you run the manual command, TCP/IP is reset and the actions that were taken are recorded in the log file, known as
resetlog.txt in this article.
The first example, c:\resetlog.txt, creates a path where the log will reside. The second example, resetlog.txt, creates the log file in the current directory. In either case, if the specified log file already exists, the new log will be appended to the end
of the existing file.

Cannot ping windows 2008 r2 while it is possible for another machine in the same network

Hi,
Recently I have set up a new server with windows 2008 r2 enterprise OS which is a domain member server.
At network layer I have two networks one with 192.168.1.0/22 and another with 10.0.0.0/24 network IDs.
My problem is that I cannot ping the newly installed server from a specific machine. Server's IP address is 192.168.1.56 and the specific machine's IP address is 10.0.0.12 and it is a windows XP machine. Of course I have to say that this problem belongs
only to this WinXP machine and all the layer 3 issues are tested and correct. This issue happens while at the same time I can ping domain controller which also is a windows 2008 r2 enterprise box and its IP address is 192.168.1.53. It turns more complicated
when I learned I can ping the winxp machine and connect to it from new server through remote desktop. Firewall also is not the obstacle because I turned it off completely.
Can anybody help me fix the problem?
TIA
Bijan

Hi,
Check the path ping from xp machine to server its timing out after reaching 192.168.1.254 , What kind of a device is 192.168.1.254 IP belongs to.
Tracing
route to sp45newfs.ph45.local [192.168.1.56]
over
a maximum of 30 hops:
0 B15-333.PH45.LOCAL [10.0.0.12]
1 192.168.1.254
2 * * *
Computing
statistics for 50 seconds...
Source to Here This Node/Link
Hop
RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 B15-333.PH45.LOCAL [10.0.0.12]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% (192.168.1.254)----------(Which device has this IP)
100/ 100 =100% |
2 --- (100/ 100 =100% )---(100% loss) 0/ 100 = 0% B15-333.PH45.LOCAL [0.0.0.0]
Trace
complete.
Regards,
Srivishnu.K

Solaris 10 network status shows 'disconnected' & cannot ping out

Hi,
In my solaris 10 sparc t4-1 server, the network status shows 'disconnected'
I cannot ping to any servers in the lan.
Please help
thanks

Sounds like it's either infrastructure or faulty hardware. Are you sure the port is turned on that you are plugging into?

Is there any other ways to check whether is my phone faulty or my sim card issue. I can only use it for call, my network to 3G or 4G suddenly cannot use.

Is there any other ways to check whether is my phone faulty or my sim card issue. I can only use it for call, my network to 3G or 4G suddenly cannot use. This happen since yesterday, suddenly can use but suddenly cut off. Called Telco and they reset account but still same.

See this
http://support.apple.com/kb/TS4148

I suddenly cannot connect to any wifi with my ipad 1. In settings my wifi is turned on. My home connection shows up under Choose a network and has a strong signal.

I suddenly cannot connect to any wifi with my ipad 1. in settings my wifi is turned on. My home connection shows up under Choose a network and has a strong signal. I have reset the Wifi under General. But when I type in my password it still says, "Unable to join the network."

1. Turn router off for 30 seconds and on again
2. Settings>General>Reset>Reset Network Settings

IPhone can join WRT54GS network, but cannot connect to internet

I've got a WRT54GS v.1.1 router w/latest firmware (4.41.4). My wired and wireless computers (windows XP) can connect just fine and see the internet. My iPhone 3GS can join the network, but cannot see the internet. The phone can join the network, gets a DHCP address/gateway/DNS info just fine. Other machines on the local network can see the phone and vice-versa. However, any time the iPhone tries to reach out to the internet, a message pops up saying "Safari cannot open the page because it is not connected to the internet".
Again, other machines on my network can connect without issue. My iPhone has no trouble connecting to other WiFi networks.
I've tried all different wireless encryption schemes, including no password/encryption, with the same results each time. I've also tried using a static IP address on my phone. No luck. MAC filtering is disabled, as is any other access restrictions.
Finally, I've reset the phone's network settings, reset the router to its factory defaults, and tried everything else I can think of.
I've only seen one similar message one these boards with this problem, but it was never responded to. Anyone seen this before of have other suggestions?
Thanks in advance for any help.
David

Thanks for your response!
IP: 192.168.1.100 (DHCP-assigned)
Subnet: 255.255.255.0
Gateway: 192.168.1.1
DNS: 66.218.44.5, 66.218.44.90 (the DNS's of my ISP)
Router's (local) IP address is 192.168.1.1
Router's internet-facing address is the one assigned by my ISP via their DHCP
All looks right to me.
-David

WRT54G Cannot Ping localhost

I have been using this router for some time now (v. 6), and it has given me no problems. (There was a period in time I tried to update the firmware to use dd-wrt; but that failed and I reverted it back to linksys firmware.)
I have set it up for DDNS with dyndns.org. This has been working fine for months.
All of a sudden, for no apparent reason, it could not resolve 'dyndns.org'. So, I was playing around with the ping tool, and found it could not ping dyndns.org, and actually, it could not even ping localhost!
I just did a master reset (hold the back button for 30 seconds). It still cannot ping 'localhost' (though 127.0.0.1 is okay). However, strangely enough, the ddns settings work again.
I'm afraid this will not last long. Has anybody else experienced this before?
Thanks!
-Matt

Try to upgrade the router's firmware. There's a newly posted firmware that worked for me.
To download the firmware, click here.
To learn how to upgrade your router's firmware, click here.
Firmware upgrade should optimize the performance of the router.

Cannot ping and scan ports of network printer

Hello,
I installed an Archlinux to my work place computer, and I configure everything, network is working I can ping Dns and other local hosts, but I cannot ping and scan ports of network printer HP Laserjet 1320n which is connected on same network in which all computers ip's are 10.0.2.X like and the priter IP is 169.254.154.167.
Cups is configured and working, I also install and configure according to wiki's avahi, nss-mdns, I try with dnsmasq, but nothing helps. The hp-setup and system-configure-printer is detecting printer, I add it and configure it, but I cannot print. Cannot connect and communicate with printers Jetdirect port.
Along with the Arch I have Ubuntu and WindowsXP installed, with them everything is working, I also install Manjaro but there was the same problem like in Arch.
Please help me! Thank you in advance.

^ These addresses are known as autoconfiguration addresses
Addresses in the range 169.254.0.0 to 169.254.255.255 are used automatically by most network devices when they are configured to use IP, do not have a static IP Address assigned and are unable to obtain an IP address using DHCP.
http://www.iana.org/go/rfc5735 You shouldn't consider this problem fixed
Last edited by Spider.007 (2014-01-17 18:12:29)

Wireless Network Printing; "Network is Busy", Cannot ping printer from my Macbook Pro

I have a MBP (Mac OSX 10.6.8, Intel i7) connected wirelessly to a Actiontec Q1000 wireless router. The wireless router has a printer connected via a LAN ethernet cable. I am able to log in to the router (192.168.0.1) and see the printer (192.168.0.8), and from the router's Utilities I can ping the printer using the router's ping tool. I am unable to ping the printer from my MBP. I am unable to log into the printer's IP address by typing in 192.168.0.8 in my browser window.
I also have a Windows laptop connected to the same wireless network. From the router, I can see the Window's laptop (192.168.0.10) and the Windows laptop can ping the printer (again, 192.168.0.8). Additionally, from the Windows laptop I can log into the printer's IP address by typing in 192.168.0.8 in my browser window.
The printer is a Dell 1700n and I am using the "Generic Postscript Printer Driver". I am able to delete the printer, and then add it back in as a USB connected printer and print fine. I then delete the printer and add it back in as a network printer (192.168.0.8) and am then unable to print. I am getting an error that says "Network is busy, will retry in ___ seconds". I then get a error message that says the "Printer is busy".
Using the MBP's "Network Utility's" ping tab, I am able to ping the router (192.168.0.1), the other Windows laptop (192.168.0.10), my Roku (192.168.0.7), etc. I am unable to ping the printer (192.168.0.8).
From my Window's CMD prompt, I am able to ping the router (192.168.0.1), my MBP (192.168.0.5), my Roku (192.168.0.7) and the printer (192.168.0.8). I am also able to print wirelessly from my Window's laptop (192.168.0.10).
I have looked for a CUPS printer driver for my Dell 1700n printer, but there is only a CUPS printer driver for the Dell 1710n printer (which is different).
I have also googled around and found that the Dell 1700n is an old Lexmark E322 printer, so I installed the CUPS Lexmark E322 printer driver. I then try to print wirelessly from my MBP and nothing.
This is clearly a network MBP issue, and I have searched the forums but have been unable to track down a solution. I would appreciate anyone's help to enable me to:
1. Be able to ping my printer (192.168.0.8),
2. Be able to log in to my printer via a web browser (http://192.168.0.8), and
3. Be able to print wirelessly to the printer from my MBP.
Does anyone have any thoughts?
Thanks in advance,
MC

So I spent almost 3 hours on a share session with Lexmark, who I must say I was incredibly impressed with their patience. Long story short, my wife and I have the exact same MBPs. Her MBP was printing fine to the same printer. The tech and I verified that all of our network settings were identical. At the end of the day, the solution was power cycling the router. Poof. Magic. No idea why the power cycle worked, but it worked and I now have a solution. Let me know if anyone has any questions about all of the steps in between.
MC

Cannot Ping IP available to PC on same network

I cannot ping/access an IP address that I can ping/access on a PC using the same WiFi connection.
Any idea on what may be causing this?

GuRoo wrote:
I do not have a firewall turned on at all.
Hi Pete, welcome to the club! I'm no IT expert, but if your Windows PC and Macs are both using the same LAN, I can't see this having anything to do with a firewall. I have a similar issue on my home LAN, though I recently made a change in my router settings which may resolve it if I work on it again. (I have an HP Laserjet plugged into the same router as my Mac Mini G4... I couldn't get my wife's Wintel notebook to find it when I tried before, while it had been only too simple via the Mac, so my LAN issue is really just the opposite of yours).
GuRoo wrote:
This is the first thing ever to make me question my switch to Mac and it's one that has me about to throw it out the window and go back to buggy (but fixable) Windows.
LOL ... If you give us your address, I'm sure there'll be someone there to catch it! Seriously, though, I'm sure you'll have a solution shortly if your start your own thread on this issue. From my interpretation of the original poster's issue, I think this thread has to do with accessing a particular remote IP, a problem I'm also trying to resolve.
best of luck,
Lowell

Cannot ping from zone or ping zone from another server

Hi all,
I've just setup a zone, configured the OS on it and booted it.
1) From the global zone I can ping the zone
2) From another server(s) I cannot ping the zone although I can ping the global zone
3) From the zone I cannot even ping the global zone let alone anything else
Any ideas whats gone wrong. the zone xml looks like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE zone PUBLIC "-//Sun Microsystems Inc//DTD Zones//EN" "file:///usr/share/lib/xml/dtd/zonecfg.dtd.1">

<zone name="ivcp0.lon.oss.colt.net" zonepath="/zones/ivcp0.lon.oss.colt.net" autoboot="true">
<inherited-pkg-dir directory="/lib"/>
<inherited-pkg-dir directory="/platform"/>
<inherited-pkg-dir directory="/sbin"/>
<inherited-pkg-dir directory="/usr"/>
<inherited-pkg-dir directory="/opt/sfw"/>
<filesystem special="/home" directory="/home" type="lofs"/>
<network address="212.74.77.211/25" physical="bge1"/>
</zone>
zoneadm list -vc
ID NAME STATUS PATH
0 global running /
2 ptl1.lon.oss.colt.net running /zones/ptl1.lon.oss.colt.net
3 ptl1.dev.lon.oss.colt.net running /zones/ptl1.dev.lon.oss.colt.net
7 ivcp0.lon.oss.colt.net running /zones/ivcp0.lon.oss.colt.net

Might help to send along the "ifconfig -a" and "netstat -rnv" output from both the global zone and the local zones that are having problems.
Traceroute might also help you isolate the problem

Cannot ping LAN IP Address but can ping WAN IP Address. Please help

I have LinkSys Wireless Access Point Router, after I upgrade the firmware from another router I can ping the WAN IP ADdress but I cannot ping the LAN IP address, please help.
thanks

I have two Networks here.
1st Network (6th Floor)
-- I have Cisco VPN Concentrator, Cisco Router and 3Com Switches
-- My PDC Server also located
-- IP Range 10.11.10.x
-- Gateway 10.11.10.6
2nd Network (10th FLoor)
-- I have Linksys Wireless (WIreless G Broadband Rotuer w/4 Port Switch Model: WRT54G)
-- I have 3Com Switch
-- The Internet Port of the Linksys is connected directly to 6th floor 3com switch
-- The Lan Port of the Linksys is connected to the 10th FLoor 3com switch then the server and workstations all connected to the 10th Floor 3 Com Switch
-- IP Range 192.168.85.x
-- Gateway 192.168.85.1
-- Internet IP Address of the Wireless
  IP: 10.11.10.11
SM: 255.255.255.0
  GW: 10.11.10.6
-- Local IP Address of the Wireless
  IP: 192.168.85.1
SM: 255.255.255.0
Firmware: 4.21.1
This what happen
1) Users, SErvers, computers located at 10Th Floor dont have a problem connecting to the servers and computers at 6th Floor (10.11.10.x)
2) Users, Servers and computers located at 6th Floor CANNOT CONNECT to the Servers, computers located at 10th FLoor
3) After firmware upgrade, servers and computer can ping Linksys Internet IP of 10.11.10.11
What we require.
WE NEED TO CONNECT COMPUTERS, SERVERS FROM 6TH FLOOR TO 10TH FLOOR AS WELL. MEANING WE WANT BOTH NETWORK PING OR SEE EACH OTHER
YOUR HELP IS GREATLY APPRECIATED
THANKS A LOT
CYNTHIA

Wrt54g v3 network suddenly cannot ping/traceroute

Similar Messages

Maybe you are looking for