Member Avatar for yowhat2002

Hi guys,

I seem to be having a bit of a strange problem, I think it may be a DNS issue but someone may be able to shed some light on it.

I have a pretty complex(for a home network) set up, where by im stretching my wireless internet across two buildings and a large area.

This is achieved by:

Phone Line > Belkin ADSL Router(Router 1) >Wifi> Wireless Repeater >Wifi> PC with the wireless and wired ethernet cards bridged >Ethernet Cable> Another router being used as an access point(Router 2)

After some tweeking this system has been working fine for a couple of weeks. However I occasionally now run into issues where the network goes down, and ping requests sent to the main router(router 1), appear as follows:

C:\Users\Charles>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.25: Destination host unreachable.
Reply from 192.168.1.25: Destination host unreachable.
Reply from 192.168.1.25: Destination host unreachable.
Reply from 192.168.1.25: Destination host unreachable.

Ping statistics for 192.168.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

With being the address of the pc im pinging from.

Can anyone see any reason for this? Its an intermmitant issue which makes it harder for me to track down.

Any advice would be very much appreciated.
Cheers

screenshot.jpg 87.82 KB
  • 2 Contributors
  • 3 Replies
  • 388 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by ipradip

Dani AI

Generated

Short version: when Windows shows a reply coming from your own IP with “Destination host unreachable,” the machine that sent that message (your PC) is telling you it cannot reach the target. It is not a mysterious DNS redirect — it means the PC either has no route to 192.168.1.1 or it cannot ARP for that address. That distinction is important for troubleshooting.

First, narrow the problem scope. Try pinging the router from another device/phone on the same network. If others reach the router OK, the fault is local to ’s PC or its bridge. If everyone fails, the problem is upstream (repeater / AP / router). On the PC, collect these quick facts:

ipconfig /all
arp -a
route print
tracert 192.168.1.1

What to look for: no ARP entry for .1, a missing or wrong default gateway in route print, or a route that points the subnet to the PC itself. Those point to local NIC/bridge misconfiguration. A duplicate IP or Windows Internet Connection Sharing accidentally enabled can also make the PC respond with that message.

Regarding ’s static-IP suggestion: setting a static address can help rule out DHCP issues, but it won’t fix an incorrectly configured bridge, duplicate-IP conflicts, or a repeater/AP that occasionally drops ARP. Because your setup chains a repeater, a bridged PC and a second router used as an AP, check these specifically: make sure the AP (Router2) has DHCP turned off, uses a unique LAN IP in the same subnet, and that the PC’s bridge has a single correct gateway. Temporarily disable the bridge or disconnect Router2 to see if the problem disappears.

If it remains intermittent, capture traffic with Wireshark during a failure to watch ARP and ICMP exchanges, or enable logging on the repeater/AP. Make one change at a time and test after each change; that will reveal which link in the chain is dropping.

Recommended Answers

All 3 Replies

Member Avatar for ipradip

are you using wireless? then it's not in the reachable position or if you are using lan then may be your cable is not working well so check the all connection and confirm that

Member Avatar for yowhat2002

The signal is fine, i get full bars, and have checked the exact strength with InSSIDer. The ethernet cable is also fine.

Member Avatar for ipradip

then why don't you use static ip instead of dhcp.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.