Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 | 3 
gorringS
71 posts

Master Geek
+1 received by user: 6


  #1362631 11-Aug-2015 09:46
Send private message

I still say it would of been more likely internal dns having issues. I've had my own NAS do same thing it came down simply clearing stale dns records firstly by disabling the lan port pc then enable and then flushing dns several times and then repeat disable and enable of lan port. This trick fix my own NAS. But other point as  I tried to highlight at start was to make sure you using correct login details . Seems what I said didn't get done at start as you wouldn't of need anyone to use team viewer if you actually did as I said. Hense why didn't bother doing any further posting as I could see I was wasting my time explaining







1101
3141 posts

Uber Geek
+1 received by user: 1143


  #1362677 11-Aug-2015 10:52
Send private message

Ive seen similar issues
Try using net use ,and map the share, with login & pass switches

There is a network bug thats been there since vista, its rare but when it pops up the only way is
using net use.
On one network with Win8 & a NAS  had to use a net use batch file & put the bat file in scheduled tasks to
run on startup.

1 | 2 | 3 
View this topic in a long page with up to 500 replies per page Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.