I'm having problems on a XP home peer to peer network sharing files & folders
from a host computer to a client laptop computer. I can make it work but not
consistanly.

Background:
1 host computer, 1 Desktop client and 1 laptop client. All the computers
were recently upgraded to SP2. The host computer seems to be the problem. All
computers have no vireses,3rd party firewall or adaware and the windows
firewall is turned off. On the host computer after the SP2 upgrade the
firewall fearture was turned on and greyed out so I couln't change it. I
found out that the Windows Firewall services were turned off. I set them to
Auto and started them. I was now able to turn off the firewall and the
desktop client was now able to connect to the shared host computer files.
However when I connect the laptop to the network I can not connect or ping
the host computer. Pinging the other client is not a problem and pinging the
host to the laptop is not a problem.

Here is what worked when I was last at my client business.

When I would ping from the laptop to the host I would get no reply however
pinging the laptop from the host did return a replay. After the host was
able to ping the laptop, the laptop was now able to ping the host and get a
reply. If I reboot the host I will have to ping the laptop from the host
again in order to allow the laptop to ping the host. After making this
connection I could sometimes share host files with the laptop and sometimes
not. What I did the last time to make sharing work was I enabled the
firewall feature on the host and used the exclusion area to exlude firewall
to the local area network.

If I reboot the host I will still have to ping the laptop before I can use
one of the host mapped drives on the laptop.

Is there something in the registry that needs tweaking, added or removed?

Tbrox

--
Tbrox

On Thu, 24 Mar 2005 08:21:04 -0800, "tbrox" <(E-Mail Removed)>
wrote:

>I'm having problems on a XP home peer to peer network sharing files & folders
>from a host computer to a client laptop computer. I can make it work but not
>consistanly.
>
>Background:
>1 host computer, 1 Desktop client and 1 laptop client. All the computers
>were recently upgraded to SP2. The host computer seems to be the problem. All
>computers have no vireses,3rd party firewall or adaware and the windows
>firewall is turned off. On the host computer after the SP2 upgrade the
>firewall fearture was turned on and greyed out so I couln't change it. I
>found out that the Windows Firewall services were turned off. I set them to
>Auto and started them. I was now able to turn off the firewall and the
>desktop client was now able to connect to the shared host computer files.
>However when I connect the laptop to the network I can not connect or ping
>the host computer. Pinging the other client is not a problem and pinging the
>host to the laptop is not a problem.
>
>Here is what worked when I was last at my client business.
>
>When I would ping from the laptop to the host I would get no reply however
>pinging the laptop from the host did return a replay. After the host was
>able to ping the laptop, the laptop was now able to ping the host and get a
>reply. If I reboot the host I will have to ping the laptop from the host
>again in order to allow the laptop to ping the host. After making this
>connection I could sometimes share host files with the laptop and sometimes
>not. What I did the last time to make sharing work was I enabled the
>firewall feature on the host and used the exclusion area to exlude firewall
>to the local area network.
>
>If I reboot the host I will still have to ping the laptop before I can use
>one of the host mapped drives on the laptop.
>
>Is there something in the registry that needs tweaking, added or removed?
>
>Tbrox

Please provide ipconfig information for each computer, and we'll go from there.
Start - Run - "cmd" - Type "ipconfig /all >c:\ipconfig.txt" into the command
window. Open Notepad, make sure that Format - Word Wrap is NOT checked!, open
file c:\ipconfig.txt, copy and paste entire contents into your next post.

--
Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
My email is AT DOT
actual address pchuck sonic net.

This is very similar to the issue I posted about yesterday and to which I am
still waiting for a reply!

Other cases are turning up, most notably an entire branch office that is
unable to use their shared printers!

Help please!

Dave

Dave Dahle wrote:
> This is very similar to the issue I posted about yesterday and to which I am
> still waiting for a reply!
>
> Other cases are turning up, most notably an entire branch office that is
> unable to use their shared printers!
>
> Help please!
>
> Dave
>

I have had similar situations and had to power reset the Router/Switch.
How are these devices connected?

--
Danny Kile
Please reply to the Newsgroup ONLY

"Dogs come when they're called, CATS take a message and get back to
you." Mary Bly