Windows 8.1 not connecting to a Windows 7 server

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.
Alpha4043Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Alpha4043Author Commented:
The Windows 8.1 is NOT Pro.
0
JohnBusiness Consultant (Owner)Commented:
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
Exploring ASP.NET Core: Fundamentals

Learn to build web apps and services, IoT apps, and mobile backends by covering the fundamentals of ASP.NET Core and  exploring the core foundations for app libraries.

JohnBusiness Consultant (Owner)Commented:
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
Alpha4043Author Commented:
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
JohnBusiness Consultant (Owner)Commented:
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
Alpha4043Author Commented:
I should have clarified the Windows 7 is Pro.  We are upgrading to 8.1 Pro now. Waiting for it to finish.
0
JohnBusiness Consultant (Owner)Commented:
Thanks. I assumed the Windows 7 machine was Pro as it was being used for connections.
0
Alpha4043Author Commented:
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
JohnBusiness Consultant (Owner)Commented:
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
Alpha4043Author Commented:
Perfect
0
JohnBusiness Consultant (Owner)Commented:
@Alpha4043 - Thank you and I was happy to help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.