I followed your instructions except for setting static addresses. I don't know how to do that.
Without wdclouddrive attached. Computer 1 shows
Computer 2 in the Network. I have not yet re-installed the cloud drive...we'll see about that. I works as expected. Ah Ha!
Computer 2: Ah yes...
When I disconnected ethernet and re installed the adapter, I may have shot myself in the foot.
Background:
When I returned to ethernet, disconected the Net Adapter, the network now refers to the wireless name,"NG44 Connected" rather than "Network Connected". It appears to work and clicking on "NG44 Connected" takes me to the Ethernet window. I am unable to make the NG44 go away. I couldn't see Computer 1 and I couldn't access computer 1.
Back to the original issue:
The command "netsh int ip reset resetlog.txt" resulted in:
C:\WINDOWS\system32>netsh int ip reset resetlog.txt
Resetting Interface, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting , failed.
Access is denied.
Resetting , OK!
Restart the computer to complete this action.
The instruction "netsh Winsock reset" indicated success - no errors.
After the reboots:
??? I opened the computer and Network
showed the Computer 1! I couldn't access it because it wanted a password and no pass word would work. I went to computer one and the last upgrade had changed sharing to require a password. I changed computer 2 sharing to No pass word required for sharing.
Went back to computer 2 and now it did NOT show computer 1 in the Network screen. ?????
The Ping -a command timed out as below:
C:\WINDOWS\system32>ping 192.186.1.5 -a
Pinging 192.186.1.5 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.186.1.5:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
I added 3000 miliseconds to the wait time and:
C:\WINDOWS\system32>ping 192.186.1.5 -a -w 3000
Pinging 192.186.1.5 with 32 bytes of data:
Reply from 192.186.1.5: bytes=32 time=98ms TTL=44
Reply from 192.186.1.5: bytes=32 time=123ms TTL=44
Reply from 192.186.1.5: bytes=32 time=107ms TTL=44
Reply from 192.186.1.5: bytes=32 time=95ms TTL=44
Ping statistics for 192.186.1.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 95ms, Maximum = 123ms, Average = 105ms
Note, on my last try a normal ping of 198.186.1.5 timed out.
I realized that I was working on a rebuld image which did not have your earlier corrections. I added all of the previous corrections and received the same results.
Now, I cannot see computer 1 from Computer 2, but I can access it and it is functional. Using the Run Command, "\\computer 1" and "\\192.186.1.5" will not connect. Error says cannot find....
I will reinstall the Cloud drive and let you know what happened. I thought this was wordy enough and I am beginning to associate very large hammers with my computers!
Thank you again for your assistance
Bridge