Our home network consists of two laptops, two tablets, two mobile phones, a printer and a NAS for backups. All running off a wireless router that provides the IP addresses.
Suddenly, about three days ago, I can no longer connect to the NAS. The message I get says "Error code: 0x80070035 The network path was not found." This happens on my laptop only; my wife's laptop doesn't have a problem. I've also checked and the printer works from my laptop.
The probable cause (but unproven) was when I made some changes to protect me from the Wannacry ransomware. I received messages from both Malwarebytes and Avast telling me to do the same thing. That was to go into the advanced settings of Windows Firewall and add two inbound rules. I don't remember the exact details but one rule affected TCP and one affected UDP (I'm somewhat out of my depth here.)
It was after this that I first saw the problem, so first I disabled the rules and then deleted them, but that made no difference. I've tried switching off Windows Firewall but that makes no difference either. I've researched the problem via Google and found some advice to reset TCP/IP settings. I did that via the command prompt, but that didn't work either.
Any other suggestions that don't involve a hard re-install or throwing the whole damn thing out the window?
"error code 0x80070035 network path was not found"
it can be on Windows Vista and Windows 7 Computers.
You can solve your problem like this:
"START" > "CONTROL PANEL" > "DEVICE MANAGER" > "NETWORK ADAPTERS"
Then click on "VIEW", and select "SHOW HIDDEN DEVICES".
In the expanded view you will see a long list of numbered "MICROSOFT 6to4 ADAPTER". Right click "DELETE" on all but 1 of them. When you have only 1 left, restart computer.
"error code 0x80070035 network path was not found"
I had the same error with several PCs in my network. I could not open shared folders of these PCs with the computer name. It was ok when I write the IP address.
Finally I just deselected TCP/IPv6 checkbox on the connection properties and its all ok.
Related
Chromebooks at a certain facility will not work with static IPs, and they have reserved IP addresses, but for some odd reason they will not grab those from the DCHP server. By toggling Configure IP address automatically off for a few seconds and back on, the Chromebook gets its reserved IP and works fine. In about 6-8 months we will be changing the entire network and resolving this issue, but in the meantime if I could create a shortcut method for the end users to be able to do this easily it would be a big stone out of my shoe...
I had forgotten I posted this. In order to resolve the issue, I did use "code" and "programming" to create a script that would do what I described above. So, it wasn't a networking question, it was a programming question.
I can't enter "www.google.com" from my desktop on any browser. It always says "Error code 118 (net::ERR_CONNECTION_TIMED_OUT)".
But I can enter if I write www.google.com.tr (I'm from Turkey) or if I use VPN. Due to this reason, I can't open gmail too.
This also causes google captchas not opening too. Because of that I can't login into some web sites.
This isn't happening on my phone or tablet, they are all normal. So it's not a problem of my modem.
I have tried flushing dns with outher command prompt commands, uninstalling virus protection, turning off windows defender completely, using other dns etc.
I have tried pinging "google.com" and it works. But I can't ping "www.google.com". It again throws timeout error.
I don't want to reset my windows just for this.
Any ideas?
Found the fix. If anyone having similar issue, check this out:
My hosts file was containing "216.58.208.164 www.google.com" line. I deleted it and reset my ethernet adapter. After that, I'm able to enter google and open captchas.
Have you tried clearing cache and cookies? or closing every tab except the one you are using and uninstalling extensions that aren't needed, maybe it's a memory issue as it is simply timing out
edit: found this from google support that may help
https://support.google.com/chrome/forum/AAAAP1KN0B0kPkVzx_HQWI/?hl=en
I am running a RHEL 7.2 server and connecting to it by xrdp (using windows remote desktop). Is there a way to connect to the server and view it using both of my monitors? I've tried selecting the "use all my monitors for the remote session" box in Windows Remote Desktop Connection but that didn't make any difference.
I have (sort of) done this on Ubuntu. I don't know if it works for RHEL 7.2. I mostly got my info from here if you want more detail.
Edit the file here:
/etc/xrdp/xrdp.ini
Make an entry at the end of the file that looks like this:
[xrdp8]
name=Share-Screens
lib=libvnc.so
username=ask
password=ask
ip=127.0.0.1
port=ask
When the person you want to share screens with logs in, make note of the port shown in the connection log when they first log in. There will be two ports, make sure it is the second one. When you log in, change the module to "Share-Screens" and enter in the username and password to what the other person used and enter in that port that you took note of.
This works for me, but unfortunately I cannot share screens with a person remotely logged in and with me locally logged in. I hope this might help you, but this post is getting pretty old!
I running an Ubuntu VM via Vagrant on a Windows 10 host. On the Vagrant machine I am running a fairly standard PHP/nginx app.
Whenever I try to access the web app, it takes forever to load. Chrome network inspector shows this:
Chrome network timeline
This huge latency is completely gone on subsequent requests, but whenever I pop back into the browser and try again after a while, it crops up yet again.
I am using NFS.
I have disabled firewalls on both guest and host machines.
I increased keepalive_timeout in nginx which helped hide the problem, as it increased the time window for latency-free subsequent requests.
This latency occurs even when accessing static files, so I don't think it's a PHP-FPM/MySQL problem.
I successfully figured out what my problem was!
After looking at my Windows hosts file, it looked like my vagrant-hostmanager plugin had not been properly clearing out older IP entries (i.e. I had three seperate IP entries for myapp.dev even though only one IP was active). Probably because I'd forgotten to properly vagrant halt before shutting down my PC a few times.
Windows was clearly spending ages trying to resolve the two older entries before successfully resolving the 'real' one.
It's weird: you'd think this problem would cause the latency to show up in the DNS Lookup portion of the Chrome network timeline, rather than Initial connection, but oh well!
On my Win7-PC the network takes up to 10 minutes until it's shown as ready (through network icon). The weird thing is that even in the meantime (blue circle is spinning) network activities like mail, internet and access to network shares are working.
How does Win7 decide that a network is ready?
The issue is that one of my installed apps which uses the IP stack (runs on localhost) doesn't work until the network is in ready-state. I found out that if I disable the Windows Management Instrumentation service the network state switches to ready immediately. However, this prevents a couple of other services from starting what could lead to a security issue. (To me it seems like my PC waits until it gets a GO from our network... but no evidence here)
Any hints?
Try to apply this hotfix, sometimes it works:
http://support.microsoft.com/kb/2617858
When it happens to me I have to kill the process tree of two services:
SMS Agent Host
Winmgmt
(select the service, right click, select "go to process", right click on the process, select "end process tree"; if you cannot see the process remember to click the "show processes from all the users" button).
Finally delete the "c:\windows\system32\wbem\repository" folder as fast as possible.
The "repository" folder will be re-created and the network will start working properly.
This worked for me.
Click on run dialog and type msconfig.
In the pop up click on services.
Then check/tick Hide Microsoft services.
In the ensuing dialog uncheck/untick Nividia Network service.
Finally click Apply. restart computer.
Your problem will be solved.
Disabling NVidia Network services stopped that for me.
While updating drivers etc. is good practice, it is usually just a wild goosechase.