J
Johnson Fubar
I have searched the Micosoft Public Groups for the best and most
appropriate newsgroup to request some [probably technical] information.
It is my honor and privledge to be working with a Windows XP SP2 home
network: three Windows XP workstations accessing the internet via
ethernet to a router. SP2 all around with no apparent problems. Two of
the PC's are Windows XP Pro, and the other one is Windows XP Home.
The router is a Linksys flavor with all the most current firmware, and no
problems reported generally out there in the wild wild web. Access to
the web, and to IRC channels are fine, with appropriate communications
being forwarded to the appropriate workstation, etc. In other words, no
apparent problems with the router's functionality. Port forwarding for
each of the LAN units for Remote Desktop are set, as well.
All the PC's have unique "names" and they all successfully register as
the same workgroup "name."
One of the XP Pro PC's is actually a laptop, which is usually connected
via a wireless access point to the router - but can be connected via an
available hardwire - with the same behaviour indications, so that seems
not to be the source of the problem.
Checking to insure all firewall settings for each PC's LAN address are in
the "Trusted" permissions zone, and all Windows Firewall settings are
"Off" and all PC's have a designated "folder" for sharing, here's what
happens:
The XP Home unit accesses either and or both of the XP Pro units - and
transfers files to and from them just fine.
The XP Pro units access each other - but cannot access or see (either
automatically or after a search) the XP Home unit.
When trying to search, or map from an XP Pro unit to the XP Home unit,
the XP Pro units simply can't find the XP Home unit - However, when going
to the XP Home unit, it accesses the sucessive XP Pro units just fine.
I'm not sure if this could be a factor, because the path would always be
\\[unique name]\[folder] - but I have designated drives (partitions) for
shared access - the little icons and all like that. The way my machines
are configured are that Windows XP runs on C:\ ; D:\ is always for backup
images of C:\ , etc.; and E:\ is for storage, downloading and working
files, pending dispositions, etc., pretty fluid all around. Now, I have
always called the E:\ drive "Lower 40" mainly becuase it's typically 40
GB, and the nickname just stuck. I can't find any information which
would indicate any conflict with the drive's nickname - and additionally
it would seem that the problem would be all around if that were so;
rather than XP Pro's can access each other, but not XP Home, and XP Home
can access XP Pro's but won't allow access from XP Pro's.
I'm fried! <smoke coming from ears, keyboard, and telephone jacks>
Is there some service or setting in the Admin tools - or some procedure
to wipe out all settings and just go back to basics and set this thing up
from scratch appropriately without any conflicts?
appropriate newsgroup to request some [probably technical] information.
It is my honor and privledge to be working with a Windows XP SP2 home
network: three Windows XP workstations accessing the internet via
ethernet to a router. SP2 all around with no apparent problems. Two of
the PC's are Windows XP Pro, and the other one is Windows XP Home.
The router is a Linksys flavor with all the most current firmware, and no
problems reported generally out there in the wild wild web. Access to
the web, and to IRC channels are fine, with appropriate communications
being forwarded to the appropriate workstation, etc. In other words, no
apparent problems with the router's functionality. Port forwarding for
each of the LAN units for Remote Desktop are set, as well.
All the PC's have unique "names" and they all successfully register as
the same workgroup "name."
One of the XP Pro PC's is actually a laptop, which is usually connected
via a wireless access point to the router - but can be connected via an
available hardwire - with the same behaviour indications, so that seems
not to be the source of the problem.
Checking to insure all firewall settings for each PC's LAN address are in
the "Trusted" permissions zone, and all Windows Firewall settings are
"Off" and all PC's have a designated "folder" for sharing, here's what
happens:
The XP Home unit accesses either and or both of the XP Pro units - and
transfers files to and from them just fine.
The XP Pro units access each other - but cannot access or see (either
automatically or after a search) the XP Home unit.
When trying to search, or map from an XP Pro unit to the XP Home unit,
the XP Pro units simply can't find the XP Home unit - However, when going
to the XP Home unit, it accesses the sucessive XP Pro units just fine.
I'm not sure if this could be a factor, because the path would always be
\\[unique name]\[folder] - but I have designated drives (partitions) for
shared access - the little icons and all like that. The way my machines
are configured are that Windows XP runs on C:\ ; D:\ is always for backup
images of C:\ , etc.; and E:\ is for storage, downloading and working
files, pending dispositions, etc., pretty fluid all around. Now, I have
always called the E:\ drive "Lower 40" mainly becuase it's typically 40
GB, and the nickname just stuck. I can't find any information which
would indicate any conflict with the drive's nickname - and additionally
it would seem that the problem would be all around if that were so;
rather than XP Pro's can access each other, but not XP Home, and XP Home
can access XP Pro's but won't allow access from XP Pro's.
I'm fried! <smoke coming from ears, keyboard, and telephone jacks>
Is there some service or setting in the Admin tools - or some procedure
to wipe out all settings and just go back to basics and set this thing up
from scratch appropriately without any conflicts?