Can't Communicate Between Wireless And Wired - Destination Host Unreachable
May 7, 2011
I have 2 brand new systems, a desktop running Windows 7 Pro connected with a had line, and a laptop running Windows 7 Home Premium connected wirelessly. Both can access the router, both can access the internet, both can be pinged from the router. However, they absolutely cannot see each other on the network. If I try to ping by name, the addresses don't resolve. If I try to ping by IP, I get either no reply or the "destination host unreachable."I've disabled firewall completely on both. I've double, triple, quadruple checked all sharing settings (network discovery is enabled on both, sharing enabled everywhere, etc. etc.). I've tried disabling all other network adapters on the laptop, no difference. I've tried all of the online tips about repairing winsock.
I have different types of network clients connecting to both bands of router (5 ghz and 2.4 ghz), and both bands set to WPA2 only. Everything has been set up and working for the past year with no problems.
Suddenly this morning, none of the 2.4 ghz clients can connect and get authenticated. When I attempt to ping them from a Windows 7 desktop connected by a LAN cable, I get Destination Host Unreachable.
The 5 ghz clients are fine and have had no problems. I tested this with the New iPad connected to the 5 ghz band.
Rebooted the E3000 router and the Comcast cable modem, then installed the newest firmware on the E3000 using the web access portal at 192.168.1.1, and still not working.
Changed the WPA2 Personal security mode for the 2.4 ghz band to WPA2 Personal/WPA Mixed Mode, and now all the clients are connected and authenticated and working OK, albeit slower.
What happened? And how can I fix this so I can change the security mode for the 2.4 ghz band back to WPA2 Personal?
P.S. The types of clients that connect to the 2.4 ghz band are 2 Windows 7 desktops, a Windows 7 laptop, and 5 Cisco Wireless N Internet Home Monitoring Cameras. The camera feeds have slowed down considerably using this Mixed mode.
I attempted to upgrade the firmware on the WRT54G2 V1 (the newer, slim black model) but it failed. I let the upgrade run for about 10 minutes and it just sat there and link to router disconnected I run ping for 192.168.1.1 but response is "DESTINATION HOST UNREACHABLE". The router is now completely unusable and the ALL LAN ports lights are ON and Internet light is also ON.
Im running 10 units of computers, anyhow my server has no internet connection, the other 9 units has net connection,when i ping the diagnosis is destination host unreachable.I'm using windows XP.
My old router recently died and my ISP was kind enough to offer this Thomson one free. But ever since I got it, my PCs cant see each other on the homegroup. They can all get onto the internet - and by using programs like Dropbox or Teamviewer I can share info from one to the other- but I'd like to get my homegroup working again, Both my PCs are running Win 7, connecting wirelessly to the network. When trying to tracert from one to the other it gives this message: Tracing route to GLaptop.lan [192.168.1.79] over a maximum of 30 hops: 1 GDesktop.lan [192.168.1.82] reports: Destination host unreachable. The problem persists when firewalls on both PCs are disabled, and I've attempted to delete the homegroup on both PCs and re-create it.
My internet connection started to disconnect after an office mate used my PC. I thought it was just the cables but it's not. I pinged my ip address and its okay (sent=4; received=4). But when i ping Yahoo! and other websites, it said that "Destination host unreachable" (sent=4;received=0;lost=4;100% loss). What should I do to make my connection okay? I didn't ask assistance from our IT personnel bcoz they said if i want to reconnect/reinstall connection, I have to get an approved request from our bosses. And I don't like being asked bcoz they are like tyrant bosses.
ping 10.0.0.1 -t give me destination host unreachable in the same time when i wright ping 192.168.1.1 -t it give me the correct reply but the net doesnt work
My company has a Cisco IAD 2400 which is handling our phones and the internet (from Service Provider). We are adding a second router, a Cisco 1921, to our network,I think I have everything set up correctly. One department is using the 192.168.2.0/27 subnet. I can ping each computer within that subnet. Also, within this subnet, I can ping the router interface at 192.168.2.1. I can ping 192.168.1.2 successfully as well. This is the interface on the 1921 that goes to the 2400. However, if I try to ping 192.168.1.1 (interface on 2400), I get "Reply From 192.168.1.236: Destination Host Unreachable" I get the same thing if I ping 8.8.8.8.Within the 1921, I can ping 192.168.1.1 and 74.125.224.72 (random google ip) successfully.
I am using the window server 2008 and configure tcp/ip properties correct ping locally reply successful when ping localy but when ping yahoo.com then reply destination host unreachable whereas gateway and dns ip is also correct configure so tell me solution about this problem because i am useing the internet.
i have my 9 computers 1 prolink modem/router h5200 and tplink switch...for 3 months my connection is quite good..but in the 4th month its starting to Reply 192.168.1.1 Destination net Unreachable..i called up a technician from the network..He changed my modem/router with the same model and it runs for an hour... 5-6 hrs..the problem starts again it begins to ping Reply 192.168.1.1 Destination net Unreachable...b4 my TCP/IP i configured it automatically but now i try to put it manually...my modem/router starts with 192.168.1.1 my first unit starts in 192.168.1.2 and so on.
I've tried everything that has been posted so far except for opening up the router itself which I will refuse to do.- Getting = Host Unreachable 192.168.1.20 (I am using 192.168.1.1 as the gateway)- No ping whatsoever even when turning on the router over and over.
Up until recently one of my sites was able to get to a postilion subnet. Then we started receiving "host unreachable" e-mails. Posting told us SMTP traffic was not getting let in. I've compared the current config to a config that was saved before the issue popped up and found really no noticeable difference.
I tried a packet tracer trace with no luck: SiteB- Firewall# packet-tracer input outside tcp 11.2.2.36 12345 65.19.0.0 25.
Phase: 1 Type: FLOW-LOOKUP Subtype: Result: ALLOW Config: Additional Information: Found no matching flow, creating a new flow [code]...
Result: input-interface: outside input-status: up input-line-status: up output-interface: outside output-status: up output-line-status: up Action: drop Drop-reason: (acl-drop) Flow is denied by configured rule
Attached is a sanitized config. I'm not entirely convinced it's a firewall issue, but I need to some successful testing to prove otherwise.
I am just confused over the fact that a router configured with 10.1.1.1 address (assuming it's got 255.255.255.0 mask) can communicate to a PC connected to one of it's LAN ports and manually setup to have 10.1.1.2/8 address. I was sure that since these are two different subnets they won't see each other. But they do and searched wiki and just googled to see why, but with no success. A friend of my friend says something about 'same range' but it makes little sense to me.
I just need a good article about it or a crystall clear explanation, because I feel my understanding of IP is not as good as I used to believe.
I am trying to get an XP machine to communicate with 2 printers that are wired via USB to a windows 7 machine. Peachtree accounting is running on both machines and the windows 7 machine holds all the data this works fine but when I try to share the printers I can not. When I go into the window 7 Home Prem. network share and choose to allow printer and file shareing and close out the window cut off the computer reboot and go back into file and printer shareing both are in the off position what's up?
Been using a BEFSR41 with a Speedstream 5200 modem for 7 years with 3 Apple computers. The modem is outdated for todays speeds. Windstream gave me a “new” modem Gagaset 4300. After configuring the 4300 I replaced the 5200 with the 4300. With this setup the computers are not able to connect to the internet. The LED lights on the router do light up and the computer’s networks show there is an ethernet connection but no joy when I try to launch a browser or get email However I could connect the 4300 directly to one computer and get email and search the web. The Windstream tech (phone call) said the router needs to be reconfigured so it can “talk” to the 4300 modem. If this is true how can I configure the router if I cannot get to the Linksys -router web pg?
I have used this WRT54gl for several years and it's performed flawlessly both wireless and wired. Recently I've extended the reach of my home network by adding a second WRT54g cabled to the network. I also added another PC in a nearby home with a wireless dongle attachment to the network. In setting all this up I've just noticed that the 'Traceroute' and 'Ping' functions in the original WRT54gl do not work. That is, when in the Administration, Diagnostics window and select either function I get a 'Network is unreachable' message instead of the ping/traceroute information.
All other functions on the network seem to work fine, ie..., I can ping the router from anywhere. Both wireless and ethernet connections work fine through it. The newer WRT54G addition to the lan is setup identical and the ping/ trace router work fine with it.Both routers have DHCP disabled. My modem handles it.
I'm trying to configure an snmp notification reciever on WCS 7.0, so that critical alarms get reported to our central console. Following the configuration guide I was able to add the reciever as northbound, but after adding it I get an alarm saying that it is unreachable by WCS so all alarm notification will be suspended. I have tested snmp and ping connectivity between the WCS box and the notification reciever and it works ok, is there some other traffic that I might be missing?. I've seen some packets going from the WCS box to TCP port 7 on the reciever, which as far as I know is the echo service, is that what WCS uses to test connectivity?
I am getting an alarm on WCS where a one controller is down, unreachable from WCS, while the other one is reachable on the same WiSM module. Upon investigation, Status of controller is shown as "Oper-Up" for all controllers on Supervisory engine. Hardware platform is Cisco 6509-E.
WLAN Slot Controller Service IP Management IP SW Version Status ----+-----------+----------------+----------------+-----------+--------------- 2 1 192.167.10.11 172.19.47.65 6.0.196.0 Oper-Up 2 2 192.167.10.12 172.19.47.66 6.0.196.0 Oper-Up
However, I can not ping the managment interface of the down controller while the other controller management interface is pingable. All these interfaces are in the same VLAN.
ping 172.19.47.65 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.19.47.65, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)
Problem is fixed when I reboot the problematic Controller. However, this problem re-appears after some time. I am not able to figure out why controller is not able to ping its default-gateway which is an SVI interface on Supervisory card on the same chassis, and showing status UP/UP. Is it a software bug or backplane fault or any other reason ?
I have a host that can successfully connect to a PIX 515E (7.x OS) via VPN Client; however, I have no IP routing to the LAN from the remote host.The VPN IP pool works finem,The LAN default gateway is the inside interface on the PIX; the network is flat L2 behind it.The default route on the PIX points out; no other routes are defined,The VPN remote host can be pinged from LAN hosts, but the VPN remote host cannot ping any LAN host, not even the PIX inside interface.
Once in a while, I lose Internet connection and at the same time cannot reach my Siemens Speetstream 4100b DSL modem's setup page 192.168.0.1 ; it happened again this morning (from both wired and wirelessy connected computers). When I go to the router's setup page 192.168.1.1 , it would usually in that situation show that the router has not acquired the Internet IP Address; I power-recycle (a few times) both modem and router and eventually the router reports that it has acquired the Internet IP Address, but there is still no Internet, and the DSL modem's setup page 192.168.0.1 is unreacheable.The situation usually self-resolves only in an hour or so after the time the router has acquired the Internet IP Address: Internet starts working, and the DSL modem's setup page 192.168.0.1 becomes reacheable.
We have 2 aironet 1310 aps setup as infrastructure access points between 2 buildings. One went south on us & we placed it. Before the bad one went down, we were able to manage both remotely & could see them from the next device via CDP. Now, we can't connect or even ping either AP. And the weird part is that the switches that connected to each can see each other via CDP, but not the access points between them. I'm attaching the configuration. Before I make the 2.5 hour drive back to the site, what I may have misconfigured on either or both access points?
my WRT54G has been configured to block any and all incoming connections.continue to have disabled all port forwarding, port triggering, the DMZ, and QoS, via the applicable tabs under the [Applications & Gaming] Panel. The WRT54G continues to be configured to operate as a Gateway.No static routes are defined. The routing table show four entries, none of which are remarkable or match in anyway the partial address identified above.So I am under the impression that my WRT54G should be ignoring everything from the WAN-side.Even pinging the WAN-side of my router from the outside internet times out.My WRT54G ver 6 is at firmware level 1.02.8, which, as far as I can tell is the latest issued by Cisco.I am completely perplexed how such a connection is being established, and do not know if it is or has the potential of causing any harm. My own research indicates port 520 is typically used for RIP protocol, but I have almost zero knowledge of such.
I have a EA6500 with a hard drive connected to the USB port. When I try to copy a file to the drive VIA the network folder on my computer it says "Destination Folder Access Denied, You Need Permision To Perform This Action". I used to be able to copy files to the drive so I am sure it is just a setting on the router or something.
After reconfiguring my LMS 4.1 from snmp v2 to snmp v3 the endhost aren't reachable anymore. Before configuring the snmp v3 I have purged the endhost database in order to repopulate it. After the jobs run no endhost could be added to repository. It just says unreachable.
Could it really be a snmpv3 issue? Everytihng else is working as before. I'll have to go back to snmp v2.
Wireless on this laptop will not connect. Another laptop connects without problems.DDS (Ver_10-12-12.01) - NTFSx86 Run by Owner at 20:48:45.56 on Fri 02/11/2011
So we have a cisco asa 5505. Once a day now (random times) it will suddenly be unreachable along with the hosts connected. If I console in and ping a host from the asa, suddenly it becomes reachable from the outside world again. My job prohibits me from posting the configuration online.
I any running Cisco Works LMS 4.0 on Windows 2008 Enterperise Edition with SP2.I am facing 2 issue which are below:
1. Get message "You are using unsupported Version". As per Cisco document Windows 2008 Ent edition is support by LMS 4.0 2. All of my devices are showing unreachable. I already double check the Devices Credential include SNMP (Read and Write community) and Username and passwords.I can accessble all devices via telnet from the same Cisco Works Machine.
One of our laptops won't connect to the internet via wireless, gives a "Cannot communicate with Primary DNS Server (192.168.1.20)" error. It works fine when plugged in via ethernet, and all our other computers connect to wireless just fine.
The wireless is set to acquire DNS automatically in the TCP/IP IPv4 properties. I've tried to flush DNS, reset IPv4 and reset Winsock with no luck.
in my test LAB i have used a 5505 running 9.1.1.I have setup a DC (2008R2) and then AD Agent.I have configured and used Identity firewall rules which worked like a charm.I have also used LDAP Auth which also worked fine.I then disabled all the rules but kept the identity firewall checked.Since it was a lab environment, i had to remove the DC for other tests.A few hours later the ASA initially was stuck.I used the console and i saw it could ping noone! not even directly attached PCs or defgw (i was able to ping them before it stucked).No arp table also!the asa did no NATing so no xlate entries were vavailable.Then i sshed to it.I got a blank screen and from console i could see cpu-usage from ssh to 20%I opened a second ssh: nothing. Blank Screen again. cpu-usage from ssh to 40% (overall ~50%)I opened a third ssh: nothing. Blank Screen again. cpu-usage from ssh to 65% (overall ~75%)I issued reload from console! Nothing! it was trying to shut down!I issued reload quick-> that is when console was lost!!I have to unplug it.
The DC that was removed was also the DNS for the ASA.The only log message i could see, before it stuck was "AD Agent is out of reach".i have ttried this 4 times. Always the same. 100% reproducible.I disabled the identity firewall-> no problem! it worked for days.100% reproducable.I downgraded to 8.4.5--> the same for both above actions.
