Another “Network Path was not found” gotcha

Posted on June 19th, 2012

When testing Overseer 5.0, I got stuck on a “Network Path is not found” issue. I was testing with workgroup-based computers instead of domain-based computers, and I was quite certain it was due to this setup that the problem was happening– as my domain based computers continued to work fine, even connecting to workgroup-based computers…

Eventually, I tracked this down to using usernames such as “.\administrator”… Sometimes Windows uses these, so you’d think it’d be OK– but when connecting FROM a workgroup-based computer to another workgroup-based computer(and maybe domain computer; I didn’t test that), you’ll get a “Network Path was not found” error– totally useless for an obvious **username** issue… While there are many causes of the network path was not found error, this is one that I didn’t know about until today.

Oddly enough, I did a network tap when trying to figure this out, and I saw Windows attempting to connect **on port 80** to the computer, versus using SMB ports(139, 445, etc.)… This was crazy, yet I could find no information online about this– obviously, it’s using the WebClient service instead when it sees a username like this…I’m still not sure why.

So, bottom line– if you’re receiving a “network path was not found” error, and you’ve gone through the checklist, make sure you’re not using .\username when logging in.

If you’re using Overseer network monitoring software, Overseer will automatically change a username without a domain qualifier into the appropriate MACHINE\username– so simply enter the username, and you’ll be OK.


Overseer 3.0->4.x upgrade pricing ends June 30th– free upgrade to 5.0!

Posted on June 8th, 2012

Overseer Network Monitor 5.0 is scheduled to be released June 2012. With the release of 5.0, all customers who purchased or upgraded to 4.x after June 30th, 2011, will receive a free upgrade to Overseer 5.0.  With this release, the special upgrade pricing we have offered for 3.0 customers will end. Customers who purchased Overseer 4.x prior to June 30th, 2011 will receive special pricing to upgrade to 5.0.  If you have a 3.0 license you’d like to upgrade, please upgrade by June 30th, 2012 to receive your free upgrade to Overseer 5.0!  Also, if you’re planning on purchasing 4.1, go ahead– you’ll also get a free upgrade to 5.0!

You can purchase upgrades at http://www.overseer-network-monitor.com/pricing.aspx