Win 7 Cannot Access XP PC

I have a network (LAN) of several machines at home. The other day I
tried to access OLDPC with XP from my DENPC with Win7. I got an access
error for //OLDPC from . Both are on MILKWAY group. I somehow managed to
fix matters from the XP machine, so that I could access it from Win7. A
few days later I was getting the access error from Win7. Whatever I did
on the XP machine doesn't work any longer. The ethernet cables seem
properly connected (visually)

I am not really able to verify the groupname on the Win7 PC. Under the
Control Panel Network Sharing Icon it shows HomeGroup: Joined. Joined
opened shows four choices. None show me the group name. One is Leave the
Homegroup, but the choices do not seem to give any insight into what the
Homegroup name is. The WinPC does not show it sharing with anyone else
on the LAN, which is OK by me.

I've found Win7 in this respect on other features. That is, to find
something to display, one often has to dig into choices that eventually
reveal what you are looking for, rather than making it real obvious.

Comments?

On 7/17/2011 1:17 PM, W. eWatson wrote:
I have a network (LAN) of several machines at home. The other day I tried to access OLDPC with XP from my DENPC with Win7. I got an
access error for //OLDPC from . Both are on MILKWAY group. I somehow managed to fix matters from the XP machine, so that I could
access it from Win7. A few days later I was getting the access error from Win7. Whatever I did on the XP machine doesn't work any
longer. The ethernet cables seem properly connected (visually)

I am not really able to verify the groupname on the Win7 PC. Under the Control Panel Network Sharing Icon it shows HomeGroup: Joined.
Joined opened shows four choices. None show me the group name. One is Leave the Homegroup, but the choices do not seem to give any
insight into what the Homegroup name is. The WinPC does not show it sharing with anyone else on the LAN, which is OK by me.

I've found Win7 in this respect on other features. That is, to find something to display, one often has to dig into choices that
eventually reveal what you are looking for, rather than making it real obvious.

Comments?

Reboot everything in sight. Ethernet connections tend to
degrade over time in Windows.

Lynn

On Tue, 19 Jul 2011 14:18:16 -0500, Lynn McGuire wrote:

Reboot everything in sight. Ethernet connections tend to
degrade over time in Windows.

??? Never heard of that one. I've had on computer running 24/7 without a
reboot in weeks, and no trouble with the LAN.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

On 7/19/2011 5:51 PM, N. Miller wrote:
On Tue, 19 Jul 2011 14:18:16 -0500, Lynn McGuire wrote:

Reboot everything in sight. Ethernet connections tend to
degrade over time in Windows.

??? Never heard of that one. I've had on computer running 24/7 without a
reboot in weeks, and no trouble with the LAN.

I took this question ...xp.general. Too little action here. It looks
like a week between posts on a topic. That is, the post rate is about
one topic a week. Maybe 3 days instead of a week. Not very active.

On 7/19/2011 7:51 PM, N. Miller wrote:
On Tue, 19 Jul 2011 14:18:16 -0500, Lynn McGuire wrote:

Reboot everything in sight. Ethernet connections tend to
degrade over time in Windows.

??? Never heard of that one. I've had on computer running 24/7 without a
reboot in weeks, and no trouble with the LAN.

I have to reboot my file servers here in the office regularly.
Sometimes once a week and sometimes once a month. Usually MS
updates do it for me though. One is a Windows 2003 Server and
the other is Windows XP Pro box.

Lynn

On Wed, 20 Jul 2011 11:54:18 -0500, Lynn McGuire wrote:

On 7/19/2011 7:51 PM, N. Miller wrote:

On Tue, 19 Jul 2011 14:18:16 -0500, Lynn McGuire wrote:

Reboot everything in sight. Ethernet connections tend to
degrade over time in Windows.

??? Never heard of that one. I've had on computer running 24/7 without a
reboot in weeks, and no trouble with the LAN.

I have to reboot my file servers here in the office regularly.
Sometimes once a week and sometimes once a month. Usually MS
updates do it for me though. One is a Windows 2003 Server and
the other is Windows XP Pro box.

I have one old HP Pavilion 6745C running MS Windows XP Home Edition, 24/7
and acting as a mail server. Never had problems accessing it, except when
the power supply died. Can't reboot from that until you replace the power
supply!

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

On Sun, 17 Jul 2011 11:17:25 -0700, W. eWatson wrote:

I have a network (LAN) of several machines at home. The other day I
tried to access OLDPC with XP from my DENPC with Win7. I got an access
error for //OLDPC from . Both are on MILKWAY group. I somehow managed to
fix matters from the XP machine, so that I could access it from Win7. A
few days later I was getting the access error from Win7. Whatever I did
on the XP machine doesn't work any longer. The ethernet cables seem
properly connected (visually)

I am not really able to verify the groupname on the Win7 PC. Under the
Control Panel Network Sharing Icon it shows HomeGroup: Joined. Joined
opened shows four choices. None show me the group name. One is Leave the
Homegroup, but the choices do not seem to give any insight into what the
Homegroup name is. The WinPC does not show it sharing with anyone else
on the LAN, which is OK by me.
[...]

http://winhlp.com/node/179

Hans-Georg