Windows 7 Networking Sucks!

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?

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

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.

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

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

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.

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.