Home All Groups Group Topic Archive Search About

Conflict: Network Name Resolving - XP Home vs XP Professional

Author
8 Sep 2006 6:00 AM
DRBlanchette
Hey to everyone,

I've got a large network of PCs that are grouped on subnets. If I'm
running a machine on XP Professional, then I can reference any shared
resource of computer with shared resources simply by invoking its
address: i.e. \\168.1.1.1

However, if the machine is XP home, I get a lovely error stating that
the path or resource is unavailable. Now, the pro machines can resolve
across subnets which is the upside. the home cant resolve anything; not
even machines on the same subnet.

what kind of functionality is missing in home such that it doesn't do
this? If I'm trying to recreate this functionality independent of xp
pro, what kind of materials should I be using as a reference?

Thanks in advance!
Derek

Author
8 Sep 2006 3:29 PM
Chuck
On 7 Sep 2006 23:00:55 -0700, DRBlanche***@gmail.com wrote:

Show quoteHide quote
>Hey to everyone,
>
>I've got a large network of PCs that are grouped on subnets. If I'm
>running a machine on XP Professional, then I can reference any shared
>resource of computer with shared resources simply by invoking its
>address: i.e. \\168.1.1.1
>
>However, if the machine is XP home, I get a lovely error stating that
>the path or resource is unavailable. Now, the pro machines can resolve
>across subnets which is the upside. the home cant resolve anything; not
>even machines on the same subnet.
>
>what kind of functionality is missing in home such that it doesn't do
>this? If I'm trying to recreate this functionality independent of xp
>pro, what kind of materials should I be using as a reference?
>
>Thanks in advance!
>Derek

Derek,

All things being equal, a computer running XP Home, and another running XP Pro,
should work fine with each other in Windows Networking.  There are differences
in diagnostic ability though.

One of the most common causes of this problem would be a misconfigured or
overlooked personal firewall, or other security component. There are several
other possibilities too, and any might be the cause of your problem. Read this
article with an open mind.
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

If no help from the above, look at the services running on each computer.  Run
CPSServ (download and install PSTools - free) on each computer.
<http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html>
http://nitecruzr.blogspot.com/2006/04/cpsserv-comprehensive-psservice-source.html

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My        email         is          AT         DOT
   actual       address    pchuck       mvps        org.