NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
rdlm
Dec 25, 2013Aspirant
Unable to access remote path
I've been running a backup job between my NV+ and my Win8.1 PC without problem. It ran successfully as recently as yesterday. Today, I started getting "Unable to access remote path" on all backup j...
rdlm
Dec 25, 2013Aspirant
I've discovered where the .102 address was coming from! Somehow, the wireless adapter on the PC (StThomas) got re-enabled -- perhaps when I upgraded to Win8.1 recently. This was associated with 192.168.1.102, while the Ethernet port was associated with 192.168.1.70. I've now disabled the wifi adapter, and the DHCP table on my router isn't showing that entry anymore.
However, the problem still persists, with backups failing, and ping resolving to the wrong address. And as per the log in my last post, "arp -d" doesn't appear to remove the routing information. I've tried "arp -d 192.168.1.102", "arp -d StThomas", and "arp -d STTHOMAS". But "arp -a" still shows the bad entry.
However, the problem still persists, with backups failing, and ping resolving to the wrong address. And as per the log in my last post, "arp -d" doesn't appear to remove the routing information. I've tried "arp -d 192.168.1.102", "arp -d StThomas", and "arp -d STTHOMAS". But "arp -a" still shows the bad entry.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!