Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Windows 8.1 not connecting to a Windows 7 server

Posted on 2014-04-03
12
Medium Priority
?
280 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 99

Accepted Solution

by:
John Hurst earned 1600 total points
ID: 39975509
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
ID: 39975528
The Windows 8.1 is NOT Pro.
0
 
LVL 99

Expert Comment

by:John Hurst
ID: 39975566
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
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
LVL 99

Expert Comment

by:John Hurst
ID: 39975692
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
ID: 39975735
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 99

Expert Comment

by:John Hurst
ID: 39976280
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
 

Author Comment

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

Expert Comment

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

Author Comment

by:Alpha4043
ID: 39978906
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 99

Expert Comment

by:John Hurst
ID: 39978916
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
ID: 39979120
Perfect
0
 
LVL 99

Expert Comment

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

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
The article covers five tools all IT professionals should know about, as they up productivity by a great deal!
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

963 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