No I have not tried turning on PW protection yet and logging in. Will try that tonight.
Also I guess I could add that Autodisconnect setting but since it did not exist I assumed it was already set to 0...or maybe it doesn't apply since I don't have a User/Pw
So frustrating with homegroups never had to do any of this mess!
Thanks all for the help I will try using a Login/PW tonight after work.
Each system is a little different. I never used Homegroup, just user and password and it connects immediately and I only logged in once.
Hope this gets resolved..... soon. Good luck tonight.
When I turn on Password it does not ask me to setup a name/pw... so when I try to login I have no login info?
That didn't seem to work anyway, even getting to the pw screen is being difficult..it always acts like the shares are not there..as if the sharing computer is down or offline..but it's not...
Really frustratingIt's not even popping up this time.
Another site mentioned using the IP instead...I did so and now the IP and Server name is listed...
However the IP works but the FILESERVER name does not...so it deems it's something to do with the assigned name that is malfunctioning...any ideas? the name is right because it works off and on...
Very annoying!!!
Weirdly, some have reported that changing the name can fix things. Try changing FILESERVER's name - then change it back again...
Soooo - I had an idea to change my computer name, and that seemed to have solved the issue completely. (Oh..I see Bree you just posted that same thing)
This may have been the whole issue..problem with win10 update that broke the name and links. Woo! hope this works!
Excellent news.
I'm wondering if the command
nbtstat -RR (release and refesh NetBIOS names)
would have accomplished the same thing.
So now that it is working is there any delay?
Darn wish I could have tried that :)
It is working now, no delay, AND I renamed it back to it's old name.
Edit://
Actually renaming it back broke it again..odd..lol
So I ran the command above and that seemed to fix it. Interested to see if it persists this time :)
Will report back.
If that doesn't persist, try this: go to c:\windows\system32\drivers\etc then copy the hosts file to your desktop. Open the hosts file and type in the IP address and computer name on one line. Save the file and drag it back to c:\windows\system32\drivers\etc folder. You'll get a UAC prompt, allow it to overwrite the original. Try accessing the computer again and you shouldn't have any problem.
Quote
