Networking Problem

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Networking Problem

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Topic # 160037 21-Dec-2014 11:53

Ok there are 2 windows 8.1 laptops, both acers.

Annoying thing is that all of a sudden we can see each others computers but when we try and connect it will not let us with the \\<computer name> network path error.

Its pissing me off since my laptop is the main one that gets all the newer things like software then everyone else gets it from me.

Im not sure what else to do and even the Homegroup is not working.

Things that I have already tried:

Making sure that IPv4 and 6 are on auto
Resettings cards
Registering DNS
Cleared the temp folders
Rebooted router and laptops
Made sure the correct services are running
Virus scanned
Malware Scanned
Renamed the network and done it on all computers.

Im just straight out stuff. It seems to be a problem with windows 7/8/8.1 yet no one really has a decent permanent fix for it. Can you please help me?

freitasm

BDFL - Memuneh
60995 posts

Uber Geek
+1 received by user: 11836

Administrator

Trusted

Geekzone

Lifetime subscriber

Reply # 1201436 21-Dec-2014 12:00

Did this ever work on these machines?

Any existing cached credentials maybe wrong? Firewall set to block incoming connections from this network?

Tried with firewall off to rule it out?

Router security configuration blocking communications between devices?

Backblaze cloud backup (personal and business) | Geekzone broadband switch | Amazon (Geekzone aff) | MightyApe (Geekzone aff) |

My technology disclosure | Business Transformation | Enterprise Content Management |

nathan

4956 posts

Uber Geek
+1 received by user: 1318

Trusted

Microsoft

Reply # 1201455 21-Dec-2014 12:44

does \\ip.address work?

Dratsab

3108 posts

Uber Geek
+1 received by user: 938

Trusted

Lifetime subscriber

Reply # 1201475 21-Dec-2014 13:42

Suggestion. Open the Credential Manager on each machine and make sure the credentials for them talking to each other
a. exist and
b. are set to Persistence: Enterprise.

If they don't exist, manually add them. If they do exist but the persistence is not enterprise, delete them then manually re-add.

Edit: I had a similar problem to what you describe some time ago, except it was my computers talking to the two NAS' I have here. Making sure of enterprise persistence fixed it.

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Reply # 1205985 30-Dec-2014 12:32

freitasm: Did this ever work on these machines?

Any existing cached credentials maybe wrong? Firewall set to block incoming connections from this network?

Tried with firewall off to rule it out?

Router security configuration blocking communications between devices?

Yes its always has worked till when I posted this.

I removed kaspesrky and then tried it, and still the same thing. So I reinstalled it.

What am I looking for in the router to check this? I have the Orcon Genious white router.

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Reply # 1205986 30-Dec-2014 12:34

nathan: does \\ip.address work?

I have entered 180.xx.xx.xx and that part worked, I enter the correct details then it said that I dont have permission to access it YET its the Admin account details.

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Reply # 1205987 30-Dec-2014 12:35

Dratsab: Suggestion. Open the Credential Manager on each machine and make sure the credentials for them talking to each other
a. exist and
b. are set to Persistence: Enterprise.

If they don't exist, manually add them. If they do exist but the persistence is not enterprise, delete them then manually re-add.

Edit: I had a similar problem to what you describe some time ago, except it was my computers talking to the two NAS' I have here. Making sure of enterprise persistence fixed it.

I have windows 8.1 standard, not pro, or ent

SepticSceptic

1735 posts

Uber Geek
+1 received by user: 348

Trusted

Reply # 1206717 1-Jan-2015 09:22

When it asked for the Username and password, did you try using the name of the computer you are connecting to, then the admin account, ie computername\adminaccount, then password ?

My thoughts are no longer my own and is probably representative of our media-controlled government

Dratsab

3108 posts

Uber Geek
+1 received by user: 938

Trusted

Lifetime subscriber

Reply # 1206734 1-Jan-2015 09:55

Kiwiprobie:
Dratsab: Suggestion. Open the Credential Manager on each machine and make sure the credentials for them talking to each other
a. exist and
b. are set to Persistence: Enterprise.

If they don't exist, manually add them. If they do exist but the persistence is not enterprise, delete them then manually re-add.

Edit: I had a similar problem to what you describe some time ago, except it was my computers talking to the two NAS' I have here. Making sure of enterprise persistence fixed it.

I have windows 8.1 standard, not pro, or ent

Your version/level is not relevant when it comes to persistence. I have Windows 7 Home Premium and this is what fixed the problem. You can't set the persistence yourself but when you manually add the credential it's persistence level is automatically set to Enterprise.

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Reply # 1206793 1-Jan-2015 11:15

SepticSceptic: When it asked for the Username and password, did you try using the name of the computer you are connecting to, then the admin account, ie computername\adminaccount, then password ?

Yes I do, both mums and my laptop are Admin accounts.

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Reply # 1206796 1-Jan-2015 11:21

Dratsab:
Kiwiprobie:
Dratsab: Suggestion. Open the Credential Manager on each machine and make sure the credentials for them talking to each other
a. exist and
b. are set to Persistence: Enterprise.

If they don't exist, manually add them. If they do exist but the persistence is not enterprise, delete them then manually re-add.

Edit: I had a similar problem to what you describe some time ago, except it was my computers talking to the two NAS' I have here. Making sure of enterprise persistence fixed it.

I have windows 8.1 standard, not pro, or ent

Your version/level is not relevant when it comes to persistence. I have Windows 7 Home Premium and this is what fixed the problem. You can't set the persistence yourself but when you manually add the credential it's persistence level is automatically set to Enterprise.

Ok persistence is set to on for it, still puzzled.

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Reply # 1206800 1-Jan-2015 11:27

Ok, so I had redone my laptop yesterday cause I had heaps of old crap on my laptop and its good to do a reset everything (aka reinstall windows) and reinstalled KTS. and still the same crap.

Jase2985

7684 posts

Uber Geek
+1 received by user: 2531

Subscriber

Reply # 1206803 1-Jan-2015 11:33

do you have to login to the laptop when its turned on?

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Reply # 1207115 2-Jan-2015 11:50

Jase2985: do you have to login to the laptop when its turned on?

Of course, We dont want everyone in the house on them.

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

Reply # 1207154 2-Jan-2015 13:57

I have found the problem, it was on mums laptop. "Media Sharing" has to be active even if you are not sharing movies and music.

SepticSceptic

1735 posts

Uber Geek
+1 received by user: 348

Trusted

Reply # 1207543 3-Jan-2015 10:22

Kiwiprobie: I have found the problem, it was on mums laptop. "Media Sharing" has to be active even if you are not sharing movies and music.

Well done. Useful bit of troubleshooting there :-)
Wonder if it's anything to do with "Use Sharing Wizard". Check out http://windowstechies.com/using-the-advanced-sharing-feature/

I vaguely recall WinXP had something similar - Simple Network Sharing, or similar. You could enable/disable this setting ( same place as referenced in the URL above), and could resolve a number of network sharing issues.

My thoughts are no longer my own and is probably representative of our media-controlled government