Network fails in one direction

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The network involved is a Workgroup consisting onf 3 PC's, 1 laptop and 1 Mac
.. The network worked totally up to expectations when the OS config was 3PC's
on Win2kPro, the Laptop on XP Pro and the Mac on OS 10.7

The change came when 2 of the PC's were upgraded to XP Media Center 2005.
The IDs of the PC's are not important. But the name of one of them is
material to the problem. We'll call it ABLE.
ABLE can see and access all of the other members of the workgroup
ABLE does NOT appear in the Workgroup listing on any of the PC's
ABLE DOES appear and is accessible on the Mac
All of the other members of the Workgroup are visible and accessible
at
ABLE

When I do tracert from ABLE these are the results that I get
All stations except ABLE = <1 ms 192.168.2.73 - the 73 varies with @
station.
Tracert for ABLE = <1 ms ABLE [::1]

One further bit of info. The upgrading of the 2 PC's to XP was not done at
the same time. When only one was on XP, the functioning of the workgroup was
normal. The anomay occured after installing XP on ABLE
 
Chartsmalm said:
The network involved is a Workgroup consisting onf 3 PC's, 1 laptop and 1
Mac . The network worked totally up to expectations when the OS config was
3PC's on Win2kPro, the Laptop on XP Pro and the Mac on OS 10.7

The change came when 2 of the PC's were upgraded to XP Media Center 2005.
The IDs of the PC's are not important. But the name of one of them is
material to the problem. We'll call it ABLE.
ABLE can see and access all of the other members of the workgroup
ABLE does NOT appear in the Workgroup listing on any of the PC's
ABLE DOES appear and is accessible on the Mac
All of the other members of the Workgroup are visible and
accessible
at
ABLE

When I do tracert from ABLE these are the results that I get
All stations except ABLE = <1 ms 192.168.2.73 - the 73 varies with
@
station.
Tracert for ABLE = <1 ms ABLE [::1]

One further bit of info. The upgrading of the 2 PC's to XP was not done
at
the same time. When only one was on XP, the functioning of the workgroup
was
normal. The anomay occured after installing XP on ABLE
Click to expand...

This is most commonly caused by a misconfigured firewall. Run the Network
Setup Wizard, making sure to enable File & Printer Sharing, and reboot. The
only "gotcha" is that this will turn on the XPSP2 Windows Firewall. If you
aren't running a third-party firewall or have an antivirus with "Internet
Worm Protection" (like Norton 2005/06) which acts as a firewall, then
you're fine. If you have third-party firewall software, configure it to
allow the Local Area Network traffic as trusted. I usually do this with my
firewalls with an IP range. Ex. would be 192.168.1.0-192.168.1.254.
Obviously you would substitute your correct subnet.

If one or more of the computers is XP Pro - and this is applicable to you
since Media Center Edition is a superset of XP Pro:

a. If you need Pro's ability to set fine-grained permissions, turn off
Simple File Sharing (Folder Options>View tab) and create identical user
accounts/passwords on all computers.

b. If you don't care about using Pro's advanced features, leave the Simple
File Sharing enabled.

Simple File Sharing means that Guest (network) is enabled. This means that
anyone without a user account on the target system can use its resources.
This is a security hole but only you can decide if it matters in your
situation.

Then create shares as desired. XP Home does not permit sharing of users'
home directories (My Documents) or Program Files, but you can share folders
inside those directories. A better choice is to simply use the Shared
Documents folder.

If that doesn't work for you, here is an excellent network troubleshooter by
MVP Hans-Georg Michna. Take the time to go through it and it will usually
pinpoint the problem area(s) - http://winhlp.com/wxnet.htm

Malke
 
Malke said:
Chartsmalm said:
The network involved is a Workgroup consisting onf 3 PC's, 1 laptop and 1
Mac . The network worked totally up to expectations when the OS config was
3PC's on Win2kPro, the Laptop on XP Pro and the Mac on OS 10.7

The change came when 2 of the PC's were upgraded to XP Media Center 2005.
The IDs of the PC's are not important. But the name of one of them is
material to the problem. We'll call it ABLE.
ABLE can see and access all of the other members of the workgroup
ABLE does NOT appear in the Workgroup listing on any of the PC's
ABLE DOES appear and is accessible on the Mac
All of the other members of the Workgroup are visible and
accessible
at
ABLE

When I do tracert from ABLE these are the results that I get
All stations except ABLE = <1 ms 192.168.2.73 - the 73 varies with
@
station.
Tracert for ABLE = <1 ms ABLE [::1]

One further bit of info. The upgrading of the 2 PC's to XP was not done
at
the same time. When only one was on XP, the functioning of the workgroup
was
normal. The anomay occured after installing XP on ABLE
Click to expand...

This is most commonly caused by a misconfigured firewall. Run the Network
Setup Wizard, making sure to enable File & Printer Sharing, and reboot. The
only "gotcha" is that this will turn on the XPSP2 Windows Firewall. If you
aren't running a third-party firewall or have an antivirus with "Internet
Worm Protection" (like Norton 2005/06) which acts as a firewall, then
you're fine. If you have third-party firewall software, configure it to
allow the Local Area Network traffic as trusted. I usually do this with my
firewalls with an IP range. Ex. would be 192.168.1.0-192.168.1.254.
Obviously you would substitute your correct subnet.

If one or more of the computers is XP Pro - and this is applicable to you
since Media Center Edition is a superset of XP Pro:

a. If you need Pro's ability to set fine-grained permissions, turn off
Simple File Sharing (Folder Options>View tab) and create identical user
accounts/passwords on all computers.

b. If you don't care about using Pro's advanced features, leave the Simple
File Sharing enabled.

Simple File Sharing means that Guest (network) is enabled. This means that
anyone without a user account on the target system can use its resources.
This is a security hole but only you can decide if it matters in your
situation.

Then create shares as desired. XP Home does not permit sharing of users'
home directories (My Documents) or Program Files, but you can share folders
inside those directories. A better choice is to simply use the Shared
Documents folder.

If that doesn't work for you, here is an excellent network troubleshooter by
MVP Hans-Georg Michna. Take the time to go through it and it will usually
pinpoint the problem area(s) - http://winhlp.com/wxnet.htm

Malke
--
MS-MVP Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic"
Click to expand...

My installation ox XP has the Guest account diabled under Simple File
Sharing. I have XP firewall off and am using Trend-Micro 2006 Security
firewall THere is no option to put in "trusted" IP's. However, I don't think
that is the source of the problem, in that both XP's are set up exactly the
same in that regard (firewall). Yet, the network traffic is ok in one
direction and not in the other.

When nothing chaged from going thru the items mentioned, I went to the
suggested wxnet.htm. Nothing there seemed to fit what is happening to me.

I did pick up a little more info about my by doing 'ping ABLE' The address
back was:
::1: That is a little different than what I got from tracert
ABLE but essentailly the same.

So, at this point I sit with an unresolved issue. The only way an ABLE file
can be addressed by the other PC is for ABLE to send the file to NOTABLE.
Then NOTABLE does whatever and files it back in the shared folder. Then ABLE
takes it back. Awkward - but it works in dire necessity situations
 
Chartsmalm said:
My installation ox XP has the Guest account diabled under Simple File
Sharing. I have XP firewall off and am using Trend-Micro 2006 Security
firewall THere is no option to put in "trusted" IP's. However, I don't
think that is the source of the problem, in that both XP's are set up
exactly the
same in that regard (firewall). Yet, the network traffic is ok in one
direction and not in the other.

When nothing chaged from going thru the items mentioned, I went to the
suggested wxnet.htm. Nothing there seemed to fit what is happening to me.

I did pick up a little more info about my by doing 'ping ABLE' The
address back was:
::1: That is a little different than what I got from
::tracert
ABLE but essentailly the same.

So, at this point I sit with an unresolved issue. The only way an ABLE
file can be addressed by the other PC is for ABLE to send the file to
NOTABLE.
Then NOTABLE does whatever and files it back in the shared folder. Then
ABLE
takes it back. Awkward - but it works in dire necessity situations
Click to expand...

Sorry, but it does sound like you've got a firewall setting wrong. I'm quite
sure there is a place in Trend Micro's program to configure the lan
settings. I don't have that program so I can't look for you. Did you create
identical usernames/passwords on both machines?

Maybe someone else will have some more ideas for you. I'm sorry I was unable
to help you.

Malke
 
Back
Top