Solved

Windows 8.1 not connecting to a Windows 7 server

Posted on 2014-04-03
12
268 Views
Last Modified: 2014-04-04
I have a customer who has a Windows 7 server and windows 7 clients attached to it.  Not using a Homegroup option. We just shared the folders and mapped the drive. And everything has been working fine for several years now.

Now they add a Windows 8.1 computer and with a new user name and password added and we can not setup a mapped drive.  All the computers can see each other and the are on the same network name WORK.

The new user name is the same on the server as it is on the Windows 8.1 computer.
0
Comment
Question by:Alpha4043
  • 7
  • 5
12 Comments
 
LVL 90

Accepted Solution

by:
John Hurst earned 400 total points
Comment Utility
Make sure File and Print sharing is enable on the Windows 8.1 computer.

Make sure password protected sharing is enabled both places.

Then you can share the Windows 7 drive to the username of the Windows 8.1 computer and then you should be able to connect.

I connect my Windows 8.1 Pro laptop to my Windows 7 Pro desktop without issue.

I assume the Windows 8.1 machine is Pro and not Home (no designation on Windows 8.1 if Home).
0
 

Author Comment

by:Alpha4043
Comment Utility
The Windows 8.1 is NOT Pro.
0
 
LVL 90

Expert Comment

by:John Hurst
Comment Utility
That may be the reason. Windows pro sharing (not Homegroup which you are not using).

You may need to upgrade the Windows 8.1 system to Pro,
0
 
LVL 90

Expert Comment

by:John Hurst
Comment Utility
Also make sure you do not have more than 5 connections to the Windows 7 box. It is, after all, not a server.

If the number of connections is 5 or less, then the issue is probably the non-Pro machine.
0
 

Author Comment

by:Alpha4043
Comment Utility
I thought it was 10 connections to a Windows 7 Pro acting as a server.

"Windows 7 has a limit of 10 concurrent user sessions (if upgraded from XP) or 20 in clean install. It's possible that some connections are left open after the user exits or multiple connections are being opened and therefore you reach the limit. When this problem occurs, check the logs in the Win7 computer that acting as the file server and post back the exact error message to make sure that this is in fact what is happening.

A single computer can open multiple connections, file and print services, applications, surfing can all use connections. Malware and viruses can exhaust your connections as well.

I would suggest no user should use the server Windows 7 PC, leave it strictly as a dedicated server. Not using it will maximize the number of connections it has available for the network users.

If the problem still persists, consider upgrading to Windows Server. It's the right tool for the job."
0
 
LVL 90

Expert Comment

by:John Hurst
Comment Utility
If you are under 10 (I had thought it was five), then you probably need to upgrade the Home machine to Pro.

Pro can connect to Home (I have done that) but the other way (which is what you are trying to do) does not work (never has for me).
0
How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

 

Author Comment

by:Alpha4043
Comment Utility
I should have clarified the Windows 7 is Pro.  We are upgrading to 8.1 Pro now. Waiting for it to finish.
0
 
LVL 90

Expert Comment

by:John Hurst
Comment Utility
Thanks. I assumed the Windows 7 machine was Pro as it was being used for connections.
0
 

Author Comment

by:Alpha4043
Comment Utility
It will connect but only when I access the drive and authenticate with the user name and password again.  I get a red x on the network drive but a pop up box will ask me for the user name and password.
0
 
LVL 90

Expert Comment

by:John Hurst
Comment Utility
Make sure you do not have persistent drives.

Open a command prompt and see what drives are in use by typing NET USE

Then delete any drives.   NET USE X: /Delete for all drives.

Then map a drive using a script:

NET USE Z: /Delete
NET USE Z: \\servername\folder

Use this to connect.
0
 

Author Closing Comment

by:Alpha4043
Comment Utility
Perfect
0
 
LVL 90

Expert Comment

by:John Hurst
Comment Utility
@Alpha4043 - Thank you and I was happy to help.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Several part series to implement Internet Explorer 11 Enterprise Mode
Recently Microsoft released a brand new function called CONCAT. It's supposed to replace its predecessor CONCATENATE. But how does it work? And what's new? In this article, we take a closer look at all of this - we even included an exercise file for…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now