Why is networking two computers so flakey in XP?

[Todd33]

I once again setup a workgroup with two whole computers in XP. I shared some folders on both machines. One computer can see the computer and the shared folders fine. The second can hardly ever see the other and when it does and you try to open a shared folder you get some permission error.

I've had similar problems since Windows 95, why does MS make such a simple thing so hard?

 

[Genx87]

Are you trying to browse the network neighborhood?

I would just map to the machine directly \\machinename

 

[Thor86]

If you had problems sharing with Win95, than what makes you think you know how to setup sharing with WinXP? Maybe you should do some research and learn how to do things properly before blaming MS on how hard it is to setup?

Just my 2cents.

 

[sswingle]

Ive never had a problem with sharing with any windows version...

 

[JackMDS]

Originally posted by: Todd33why does MS make such a simple thing so hard?

Actually you stated the problem.

Because of the attempt to make it easy, it is troublesome. I.e. Wizard auto setting CDs etc.

If you fresh install Windows and manually configure the network, it works like a charm.:thumbsup:

However, in order to configure Manually you have (OMG) to spend an hour or two learning the basics of Network.:shocked:

Hmm... Learning? Nope! Not me give me "Speed" I do not want to learn.:thumbsdown:

In addition network setting interact with other components that are not necessarily part of the core OS.

Prevalent example, a lot of systems come with a trial of Norton or other Firewalls. Well it is free so people try it. However, reading the manual? NAH (give me Speed) so the trusted Zone is not set. No trusted Zone, No Network Sharing. No Network Sharing hmm it is probably Windows fault.

The above is just an Example, there are many more...:brokenheart:

:sun:

 

[spidey07]

because it just is. the entire browsing mechanism is flawed at its core and the possiblity of having a configuration error is very high as there a bunch of things that need to be done just right.

if you follow Jack's ezlan.net links it will help a lot.

if you can reference other computers with \\computername then you just about have it and just need to let things settle down. better yet, as others have said just reference other computers as \\<ip address>

 

[Throwmeabone]

I have the exact same problem.

 

[nweaver]

network browsers are craptastic at best. networky neigborhood exists as a shortcut to "local are connections"

 

[Smilin]

The browser in XP is considered legacy by MS btw.

 

[Nothinman]

I've had similar problems since Windows 95, why does MS make such a simple thing so hard?

Because it's not a simple problem to solve.

The browser in XP is considered legacy by MS btw.

Then what replaces it?

 

[skyking]

Originally posted by: Nothinman

I've had similar problems since Windows 95, why does MS make such a simple thing so hard?

Because it's not a simple problem to solve.

The browser in XP is considered legacy by MS btw.

Then what replaces it?

Some high-dollar home server "solution" from MS. Details to come.

 

[ktwebb]

Curiously there are some of us who can setup a windows network, whatever flavor, and have it run smoothly and without many issues over and over and over. Rarely, if ever, have problems getting to remote resources. <shrugs>

 

[JackMDS]

Originally posted by: ktwebb
Curiously there are some of us who can setup a windows network, whatever flavor, and have it run smoothly and without many issues over and over and over. Rarely, if ever, have problems getting to remote resources. <shrugs>

Might be that you know how to read.

 

[ktwebb]

I think I can safely say I have never read so much as an article or narrative on how to setup a windows network. I'm sure I've been shown stuff. Been so long it's hard to remember the details of the skill set learning but reading was never part of the equation. It just isn't that hard once you understand the fundamentals and pitfalls. Pitfalls that really are few and far between. Especially on XP. XP is about as reliable as windows networking gets without a DNS or WINS server local for name resolution. At least with Pro. My experience with home is pretty light.