Windows 7 Networking Sucks!

[hacku]

There are 2 PC's in my house (soon to be 3), and they are running Windows 7 RC. I have a couple of drives that are dedicated to media (TV shows & Movies). When we both had XP Pro installed, all I had to do was right-click on the drive, go to Properties, Sharing and share the ENTIRE drive and it worked with no problems.

Now the problem I'm having is that when I try to share my media drive, I go through the same steps. The other Windows 7 computer can see the drive, he can go into it and see the folders inside that drive, but cannot access the other folders.

I also tried sharing the individual folders that are in the drive with the Homegroup and the same thing happens. He can see the folders just fine, but when he tries to view the contents of the folders it doesn't let him. Keeps telling him he doesn't have permission.

Here I thought Windows 7 improved their home networking, but it's really just became a big pain in the ass.

Can someone help? I just want to be able to share the entire contents of the drive with the other computer.

Thanks

*** UPDATE WITH FIX ***

I figured out what the issue was and it all had to deal with Windows Security. For anyone else that is interested in this fix, here is what I did.

Start>Control Panel>Administrative Tools>Local Security Policy

Then:

Local Policies>Security Options>Network Security: LAN Manager authentication level
Set it to Send LM & NTLM - use NTLMv2 session security if negotiated

I went back to share the entire drive this time with no problems, and was able to map the network drives on the other computer.

 

[djmorgan]

Try it with your AV program off, if you use Homegroup and have done the password try the built in troubleshooter.
Ensure that you have set your sharing criteria correct for both computers ie. discovery and password requirements.

David

 

[aem]

The other Windows 7 computer can see the drive, he can go into it and see the folders inside that drive, but cannot access the other folders.

Thanks

What "other folders", and where is it exactly?

 

[hacku]

The other Windows 7 computer can see the drive, he can go into it and see the folders inside that drive, but cannot access the other folders.

Thanks

What "other folders", and where is it exactly?

The Media drive has 2 folders inside of it

1. TV Shows
2. Movies

Inside each of these folders are other folders containing individual media. I just want to be able to grand FULL access to the drive without having to set folder specific permissions.

Is that so much to ask for? When I went into Computer Management>Shared Folders>Shares you can setup a New Share. From there I chose the Media drive, which it even warned me telling me that it's not safe to share an entire drive and asked if I was sure. I clicked yes and it setup the share. But once again the other computer can see the drive, I can go into it and see the TV Shows and Movies folders, but when I try to access those folders it tells me that the computer doesn't have permission.

 

[aem]

When you share that folder using the sharing wizard (which u did), did u choose "Customize permissions" where u click on the Custom button, give the Everyone group Full control, and in the Security tab, the account that is listed (you can add which ever account you want to use as credentials) make sure you are accessing your share with one of those account.

 

[torrentg]

Good advice AEM. +1

What has to be realized here is that - Windows 7 networking is exactly the same as its predecessors! Nothing different at all. Precisely the same.

Only difference is the addition of Homegroup but we can effectively forget about that since you aren't trying to use it. So in reality in this situation, nothing different at all.

 

[INH]

Why not use a homegroup, since you don't have other OSs to worry about?

 

[hacku]

I added the folders to the homegroup to share as well, and got the same error message.

In XP, you could just right-click the drive, click share and anyone on your network would access it. Why can't it be that easy anymore?

 

[hacku]

I figured out what the issue was and it all had to deal with Windows Security. For anyone else that is interested in this fix, here is what I did.

Start>Control Panel>Administrative Tools>Local Security Policy

Then:

Local Policies>Security Options>Network Security: LAN Manager authentication level
Set it to Send LM & NTLM - use NTLMv2 session security if negotiated

I went back to share the entire drive this time with no problems, and was able to map the network drives on the other computer.

 

[blade1269]

Hey,

Thanks for that tip good to know.

 

[JimDodds]

So.... just wanted to interject here. I was having the problem where Win7 can access XP, but XP can't access Win7. As soon as I took my Win7 computer out of the HOMEGROUP -- NO PROBLEM! Everything connects in both directions. Seems like the number 1 thing to check, hmmm?

 

[TaraSWinTeam]

Hello Jim,

To network computers running different versions of Windows you will need to set up a workgroup: Networking home computers running different versions of Windows.

Cheers,
Tara
Windows Outreach Team

 

[JimDodds]

Workgroup

Tara,
Thanks for your comment, but I already had a workgroup set up, AND Homegroups. My problem was my XP computer could see Win7 but not access it. As soon as I left the Homegroup everything became completely accessible in both directions. Is that the way it's supposed to work? I still can't connect across the network to the printers attached to Win7.

 

[DocBrown]

@ JimDodds,

Homegroup only works between other computers running win7. If you have a mixture of win7, Vista, XP, etc. you need to use standard business type workgroup as your network setup. Check out our tutorials here at SevenForums for networking.

 

[maxzebra]

This last note about setting security policy is the difference between a happy life and disaster! I have a Linux based server (e-smith) and Win 2K and XP all logged on OK. With 25 years of business history, that is critical!!!! But my new Win7 machine simply would not log on to it! Now - it's fine!!! Thanks heaps.

Best wishes,
Max Williams

 

[marknhl]

trying to make windows 7 and windows xp talk. it USED to work. NOW it doesn't. sooooooooo frustrating. win 7 and win 7 can share files but not win 7 and xp. tried the fix to no avail

 

[SouthSeaPirate]

Nice thread revival. Well its up now so Ill add my 2 cents...

I must agree that win7 networking completely sucks. Lets hinder productivity in the name of security that doesnt work...

My mapped drives work then dont work and then work again... Today I added a new external drive, had to add everyone group with full control and guess what... I still dont have ****ing permission!

Yesterday it kept asking for a password on a drive that Ive had working for 2 months. Funny, its set to not require passwords! So I had to create another account (again) and give it a password. Then it stops working entirely about 2 hours later... wtf? I wonder when Ill get to use it again.

 

[acurasd]

I think that Windows Seven Networking works perfectly fine.

You have to understand how a computer and software works. They are a set of instructions that are only changed by the USER.

So, if you had the networking working at one point. You either updated, changed, modified or anything dealing with networking then maybe something is going to happen. Maybe something not to your liking...

You know TIT for TAT. Not everything in Windows is going to work perfectly. Microsoft only gives enough code to some software companies just to get their product to work on windows. Therefore, comes the bugs that they have to work out.

I have been working with Windows Networking since 1995 since Windows 95. Never touched Networking. I started to work with it on Windows 98se. Now I am work with Windows Seven and its networking functions. I have never had a problem unless I create it.

For example, people thought Windows Vista as an operating system sucked! But when you have a computer is running the bare min specs for Vista of course its going to be lagging and of course the people are going to complain.

Real computer gurus know that you have to keep up with the specs as the software comes out for it to run proficient.

The same goes with networking. As the OS upgrades, our knowledge has too as well. What is exactly a computer to most of us? Test and Error until one day it works like we want and we gain the knowledge to fix it if it goes down again by (or) there is a system wide change by microsoft as we download hotfixes and kernal updates.

You have no idea how many times I had to test and error my network but I finally got it working and now I can narrow down any kinds of problems that it has becuase I know it very well.

You can't get fustrated with computers. That is why I am so interested in them becuase one day they will do soemthing and another day it can be something else and its a challange.

I have:
1. Cable Modem (Internet WAN)
2. Vonage Adapter (Open DMZ to Router)
3. Linksys Wireless N (Contains Static IP from Vonage)
4. Going to two different (Gigabyte switches)
5. The switches are sending it to 6 different rooms in the house
6. I have 1 Server, 2 Workstations, 2 Laptops Wireless, 1 PS3, 2 Blueray (using netflix), 2 networked printers -- then of course my ipod and anything else small and wireless

The only thing that keeps this setup simple is that it is not on a domain controller *lol*
but everything works fine and never had a problem with it.

Like everything else said... networks can be affected by sleep, hybernation, windows update downloads (on its own), power savers, system wide changes by users.

 

[SouthSeaPirate]

I think that Windows Seven Networking works perfectly fine.

You have to understand how a computer and software works. They are a set of instructions that are only changed by the USER.

So, if you had the networking working at one point. You either updated, changed, modified or anything dealing with networking then maybe something is going to happen. Maybe something not to your liking...

Didn't change not one single thing...

You know TIT for TAT. Not everything in Windows is going to work perfectly. Microsoft only gives enough code to some software companies just to get their product to work on windows. Therefore, comes the bugs that they have to work out.

Im not talking about and has nothing to do with third party. Im talking about basic network sharing...

I have been working with Windows Networking since 1995 since Windows 95. Never touched Networking. I started to work with it on Windows 98se. Now I am work with Windows Seven and its networking functions. I have never had a problem unless I create it.

I've been working on networks for many years as well. And I've never had a problem till now.

For example, people thought Windows Vista as an operating system sucked! But when you have a computer is running the bare min specs for Vista of course its going to be lagging and of course the people are going to complain.

Vista (& 7) doesnt suck because of lag. It sucks because of issues all usually caused by what they call Security Features. I shouldn't have to enable the administrator account, then log on locally, to delete a folder in Program Files, just so I can reinstall Adobe.

Real computer gurus know that you have to keep up with the specs as the software comes out for it to run proficient.

So your saying the only reason OSes have bug/issues is because of my lack of knowledge?

Seriously though... Of course I know I have to learn the new stuff. Otherwise I don't think I'd be in IT. Why do you think I still run Win7...

The same goes with networking. As the OS upgrades, our knowledge has too as well. What is exactly a computer to most of us? Test and Error until one day it works like we want and we gain the knowledge to fix it if it goes down again by (or) there is a system wide change by microsoft as we download hotfixes and kernal updates.

Right. It is my job to fix, but when your doing everything correctly and it still doesnt work. Then that is not my fault!

You have no idea how many times I had to test and error my network but I finally got it working and now I can narrow down any kinds of problems that it has becuase I know it very well.

Had no issues till win7

You can't get fustrated with computers. That is why I am so interested in them becuase one day they will do soemthing and another day it can be something else and its a challange.

I have:
1. Cable Modem (Internet WAN)
2. Vonage Adapter (Open DMZ to Router)
3. Linksys Wireless N (Contains Static IP from Vonage)
4. Going to two different (Gigabyte switches)
5. The switches are sending it to 6 different rooms in the house
6. I have 1 Server, 2 Workstations, 2 Laptops Wireless, 1 PS3, 2 Blueray (using netflix), 2 networked printers -- then of course my ipod and anything else small and wireless

The only thing that keeps this setup simple is that it is not on a domain controller *lol*
but everything works fine and never had a problem with it.

Im typing this while on a massive domain and Win7. With about 3,000 workstations, 100+ POS, countless servers of NT 2000 and 2003. Layer 3 Cisco core switches and routers (for wan to lan) and 2960's for LAN. I know this about my home network, but I still have to say it was pure hell getting it to take to the Domain... Hows that for comparison?

Like everything else said... networks can be affected by sleep OFF, hybernation OFF, windows update downloads (on its own) OFF, power savers OFF, system wide changes by users NONE.

I changed absolutely nothing. When I get home I bet my map will work (this happens all the time). I know what Im doing, I know how to build networks that most ppl have only seen in pictures, I only change things when it suddenly fails. Windows 7 Networking Sucks! PERIOD.

Today I added a new external drive, had to add everyone group with full control and guess what... I still dont have ****ing permission!

Hmmm I say everyone with FC and I dont have permission. Nope deff my fault here... :sarc:


Thanks for the input anyway. You just cant assume that just because its working for you doesn't mean the user having issues is at fault...

LMFAO!

 

[acurasd]

What I am saying is... It is windows... It is faulty. Windows has been out since early 90's and we know this by now.

It is always being upgraded and hotfixed at least 3 times a week and all those fixes moves or changes something inside windows.

I am not saying that your not "knowledgeable" I am just saying that It is hard to stay on top of things when things are constantly changing.

I am not wrong. Windows and every other software are just sets of instructions waiting for users to input but then again there are so many things to input now and days and changings; it is hard to keep track.

You are right. I have done many things as well to fix network problems and it all comes down to the ISP but of course to too proud with their chest sticking out to admit the fault.
===================================

So what I am saying is especially now that we figured out that you have a big *** server with domain is to narrow down the problem. Take that one computer your having issues with. Put it next to the server side by side and start working on permissions/security.

I am just saying whoever wrote "Windows 7 Networking Sucks!" is wrong. Of course the smaller the network the easier it is and in your case you are going to have a few more problems to work out since you are running. on a massive domain and Windows 7. With about 3,000 workstations, 100+ POS, countless servers of NT 2000 and 2003. Layer 3 Cisco core switches and routers (for wan to lan) and 2960's for LAN

Like I claimed in my last post.. .what makes it simple is that I am not on a domain becuase I know how "difficult" that can get with security/permissions and 2. I don't have massive computers like a company, mines is just simple home networking with a few perks.