Windows 7 Networking Sucks!

[ericpeacock79]

HOLY COW!
That worked GREAT!
fixed a problem i've been trying to deal with for weeks!

Thanx!

*** 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.

 

[ericpeacock79]

...all my problems were caused by McAfee and McAfee alone. We had a perfectly working net work until my mom got a new laptop with McAfee preinstalled.

Agreed.

I think even Satan could learn a thing or two about dirty tricks from McAfee... :devil:

many years ago, i used to tell customers AOL was the worst thing to install in your computer.
but now, McAfee (and norton 360) have totally trumped AOL.

want a real headache of a computer to work on?
A Vista system with only 1GB of RAM, mcafee and AOL installed, with a dial-up connection.

 

[SouthSeaPirate]

I've worked with Windows networking since 1995 when I started as a Senior Support Engineer for Windows 95, Network Specialist. I've architected and worked with networks ranging from simple peer-to-peer systems to Enterprise domains. So I know Windows networking. Yes, it's true, Windows networking itself has not changed. But Microsoft has gone paranoid with security stuff that makes it suck.

For sharing and storing files, and running machine-to-machine backups, on my home network, it used to be simple. I would simply map a drive to the other machine's hidden Administrative Share (C$, D$, etc.), using the network machine's Administrator account, and everything just worked.

No more. I cannot connect to a Windows 7 machine's admin shares using the Admin account. Not with basic workgroup sharing. Not with the HomeGroup active. It just won't connect. It just asks for the password over and over and over and....

How can it be a security risk to connect to the Admin share using the Admin account?

I'm about to try the Security Policy settings suggested earlier in this thread. Just wanted to chime in with my complaint about Microsoft's making simple stuff hard with all their "Cover My A**" security crap.

Nailed it 100%

Like I said earlier, "Sacraficing productivity in the name of Security". How can one do this when it totally voids the ability to be productive...

When it is told by the appropriate account with appropriate permissions to do something, it should. That is Windows security, groups, accounts, permissions etc... All the failed 'security' in XP (and Vista) was exploits, not permission issues. So why the locked down OS M$?

Thank God our corporate IT hasnt made us upgrade to Win7 yet... But I think its coming...

 

[NNSVolunteer]

WORKAROUND SUCCESSFUL!!


*********************WORKAROUND!!

On win 7 machine I mapped the IP address plus folder to a drive letter e.g. \\192.168.1.10\c\mine and sure enough I was able to access that folder on the XP machine. Did the same for the XP machine mapped \\192.168.1.11\users\public and it also worked. Now for the printer, after trying various things I found that going to the Win 7 Devices & Printers>add network printer "Click on Printer Not Shown" in shared printer by name enter the ip address of your XP printserver. Mine is \\192.168.1.10\SamsungM and sure enough it connects and is printing. To further test, I did the same for the IP address of the XP machine that has the epson. It works tonight. CAUTION!! One thing working for me in this workaround is the ability of my router to reserve and IP address for a particular computer name & mac address.

The XP with the laser and the win 7 laptop are shut down each evening. Will only post again if it doesn't work tomorrow, or if win 7 suddenly works with the network in a NORMAL manner.

Win 7 auto update KB982110 & KB2272791 applied 8/24/2010--Now the IP mapping quit working. Guess Billy wanted to suck more of my time

 

[cluberti]

Why in the world are you installing LDR non-security updates? Those things have only been tested for the person or company they were written for - don't install anything like that unless you actually need the fixes they provide (and given one's an OLE update and one's a mobile device center update, I'm doubting you're doing it because both are broken at once!).

 

[NNSVolunteer]

Why in the world are you installing LDR non-security updates? Those things have only been tested for the person or company they were written for - don't install anything like that unless you actually need the fixes they provide (and given one's an OLE update and one's a mobile device center update, I'm doubting you're doing it because both are broken at once!).

Last night when I shut down this computer, these updates had already been automatically downloaded and they automatically applied as the computer shut down.

Should I not be trusting automatic updates?? Do I need to spend time researching whether or not a particular update applies to my machine??

 

[profdlp]

Can you System Restore back to before the updates? That might fix you right up.

 

[cluberti]

Last night when I shut down this computer, these updates had already been automatically downloaded and they automatically applied as the computer shut down.

Should I not be trusting automatic updates?? Do I need to spend time researching whether or not a particular update applies to my machine??

That's interesting - I just noticed my machines started seeing 982110 and 2272691 being offered........... so, now that gets interesting. One's an oleaut32 update, and one's an appcompat update, so I'm not sure how they would break networking..... but I guess anything's possible.

With that in mind, as standard troubleshooting, if you remove those two updates, does the problem go away?

 

[NNSVolunteer]

Can you System Restore back to before the updates? That might fix you right up.

A systems restore to 8/22/2010 again allows the workaround to function. However, how do I keep them from automatically downloading and installing again at shutdown?

 

[cluberti]

How about apply one (the app compat update) and reboot to see if it's broken again? It would be worth figuring out which one (if any) actually causes it, so we can troubleshoot the why.

 

[NNSVolunteer]

How about apply one (the app compat update) and reboot to see if it's broken again? It would be worth figuring out which one (if any) actually causes it, so we can troubleshoot the why.

To answer an earlier question. Its a Toshiba 17" Laptop with a Win7 32-bit OEM install.

I went to windows update and the updates had already been automaticaly downloaded and were waiting to be installed. I unchecked KB2272691 and proceded with the install of KB982110 which required a restart. After the restart, I could no longer access the network shares.

I noticed the Gold shield on the start button (from past experience that means when I shut down, it will automatically apply a pending update). I shut down and it applied the KB2272691 update.

How do I know which updates are LDR non-security updates? Looking at the update list there are a ton of updates that have been installed over the past year. Perhaps, it was a similar update shortly after 6/12/2010 that fritzed the normal networking -- that had worked for the previous six months. I'm really too busy to do a clean install, besides, not sure I can get the laptop out of my wifes hands long enough to complete one.

Thanks. Any help is appreciated.

P.S. Have never done a win7 clean install but have done over 50 winXP and/or XP Pro clean installs over the past couple years.

 

[profdlp]

Can you System Restore back to before the updates? That might fix you right up.

A systems restore to 8/22/2010 again allows the workaround to function. However, how do I keep them from automatically downloading and installing again at shutdown?

http://www.sevenforums.com/tutorials/24376-windows-update-hide-restore-hidden-updates.html

 

[cluberti]

I went to windows update and the updates had already been automaticaly downloaded and were waiting to be installed. I unchecked KB2272691 and proceded with the install of KB982110 which required a restart. After the restart, I could no longer access the network shares.

I'd uninstall 982110 from the control panel, reboot, and verify things work again. Then I'd add 2272691 to the system and test that (I'm guessing that will not cause a problem, as it should only be installing appcompat shims).

How do I know which updates are LDR non-security updates?

If you look at the update article, it usually tells you the files it's updating, and to the far right it will tell you if they're GDR or LDR/QFE. If you don't see any indication, you can assume it's LDR (these are actually GDR and LDR, so you're getting GDR unless you manually install the LDR bits, or previously had LDR bits). The articles also give you instruction on how to check your system for which type of files they are. For right now, though, let's ignore this point and do the other portion, test 2272691 on it's own with 982110 uninstalled and see if it still breaks after only 2272691 is installed.

 

[NNSVolunteer]

For right now, though, let's ignore this point and do the other portion, test 2272691 on it's own with 982110 uninstalled and see if it still breaks after only 2272691 is installed.[/QUOTE]

I did the "uninstall" of these updates. It needed a reboot. After rebooting, the IP workaround didn't work. So, did the restore to 8/22/2010, and after everthing had booted up, I changed windows updates to allow me to screen them before updating. And hid the 2 offending updates. There were actually 3 updates ready to attack. The other KB982670 was marked important. Based on it's description, it didn't look important to processes I use, so I hid it also.

The mapped folders to the XP machines, and the mapped IP to the printer attached to one of the XP's again works. I may get time later this evening to scamble things again to see if 2272691 screws things up on it's own.

 

[NNSVolunteer]

For right now, though, let's ignore this point and do the other portion, test 2272691 on it's own with 982110 uninstalled and see if it still breaks after only 2272691 is installed.

I created a "Current" restore point. Unhid and installed 2272691. Workaround works. Rebooted even though this install did not request it. Workaround still works. So, looks like 982110 is the one messing things up. KB976422 appeared -- allows larger than 32 GB SD drives -- don't need it, so hid it. Might be getting the hang of TAKING CONTROL of updates I think, I'll only install critical updates until the final Win7 SP1 becomes available. Then I'll install and hope it gets me back to "normal" networking like I had before 6/12/2010.

 

[profdlp]

...I think, I'll only install critical updates until the final Win7 SP1 becomes available...

That's the way I go. The others just add features or improvements which I may or may not want or need and often aren't worth the trouble.

 

[cluberti]

Amen - unless it's security critical, I think most of us would strongly suggest you look closely at what it changes to determine if you need it or not. If you don't think you need it, don't install it. It'll come with the next service pack anyway, and be much better tested by that point (hopefully, anyway).

 

[NNSVolunteer]

WORKAROUND SUCCESSFUL!!


*********************WORKAROUND!!

On win 7 machine I mapped the IP address plus folder to a drive letter e.g. \\192.168.1.10\c\mine and sure enough I was able to access that folder on the XP machine. Did the same for the XP machine mapped \\192.168.1.11\users\public and it also worked. Now for the printer, after trying various things I found that going to the Win 7 Devices & Printers>add network printer "Click on Printer Not Shown" in shared printer by name enter the ip address of your XP printserver. Mine is \\192.168.1.10\SamsungM and sure enough it connects and is printing. To further test, I did the same for the IP address of the XP machine that has the epson. It works tonight. CAUTION!! One thing working for me in this workaround is the ability of my router to reserve and IP address for a particular computer name & mac address.

The XP with the laser and the win 7 laptop are shut down each evening. Will only post again if it doesn't work tomorrow, or if win 7 suddenly works with the network in a NORMAL manner.

Win 7 auto update KB982110 & KB2272791 applied 8/24/2010--Now the IP mapping quit working. Guess Billy wanted to suck more of my time

About 3 weeks after posting, the workaround quit working so up until 2 weeks ago have been using a USB drive for networking with Win 7. 2 weeks ago did a complete wipe and retore with OEM restore DVD's. Win 7 has since been playing nicely on my predominently WinXP network. Who know's what went askew before and who knows how long it will work.

 

[Mil0s]

I tried this too but i still have the same problem.I connected windows 7 and xp much more easily then two PC's with windows 7.I turned off everything that could block the file sharing and i set up everything on my second computer same as my primary PC, and i stil got this when try to access You do not have permission to access \\User-pc\e Contact your administrator to request access

 

[kegobeer]

I tried this too but i still have the same problem.I connected windows 7 and xp much more easily then two PC's with windows 7.I turned off everything that could block the file sharing and i set up everything on my second computer same as my primary PC, and i stil got this when try to access You do not have permission to access \\User-pc\e Contact your administrator to request access

You are using a crossover cable. You have a different configuration and normal networking may not work for you. I posted a link to how to use a crossover cable in your original thread.