Okay. XP HE on both PCs. Host PC is FAT 32, client PC is NTFS. If I disable
ZA, everything works fine (file sharing & net), so I assume my network is
set up okay. When I enable ZA, I can't do anything from the client PC, so I
assume the problem lies with ZA.
I really appreciate your help Bob, thanks again!
Kim
trusted
anything
not
appreciate
friends,
I use ZAfree on one PC here, and it does not block F&P sharing on my LAN.
If you can get to the 'net from the client PC as well as from the host PC,
then your network is working OK. If that's true, then I assume your
complaint is that file sharing does not work; right? If so, then your
problem is with file access across your LAN. Are you using XP HE, or
XP PRO, or a mixture? NTFS or FAT32 or a mixture? If XP PRO, are you
using simple file sharing? Do you have the Guest account enabled on
both? Do you have a shared non-root folder, with a short simple folder
name a short simple share name on each PC? Can you map a network drive
to those shares in either direction?
1. Don't worry that the host PC uses FAT32 while the client PC uses
NTFS. That works fine.
2. Since you've deduced that ZA causes the problem, there are only a
couple of likely causes I can think of for the failure to share:
a. The other PC is not included in ZA's Trusted Zone - for simplicity,
set them all up to make 192.168.0.0-192.168.0.255 in the Trusted
Zone, since that covers both the ICS host and all possible ICS
client assignments. {You should normally see 192.168.0.1 for
the host and 192.168.0.2 for your only client.}
b. The client cannot get Domain Names translated because the IPA used
for DNS is outside of the 192.168.0.x range. Run CMD, then type
IPCONFIG/ALL in the CMD window; you'll see a few IPAs listed as
DNS Servers, so add each of them into ZA's Trusted Zone.
There are lebenty-leben other causes of sharing failures, but the two
above are the only ones that seem likely for your case.