Re: Home network problem

Jeff,

In ZA go to Firewall (in the left column) then the Zones tab.

Is your NIC listed as being in the trusted zone? If not, click on
Internet and select Trusted. This lowers the blocking for anything from
the local net and unless some specific program is blocked should let the
other PCs see the Dell.

Next. How old is you ZA. Some of the (now very) older versions would get
quite goofy when its database started to get corrupted. You could do a
clean install (or update) to start over on the database. Or start in
safe mode and go to %windir%\Internet Logs and delete all the files.
When you restart normally it will recreate the files and start asking
again as each program tries to connect to the internet.

Roger

On 12/29/2005 9:28 AM, Jeff Crosby wrote:

>Since everyone is having a slow week <g> I need some ideas on a problem.
>
>At home I have Comcast broadband, Linksys BEFSX41, a Dell desktop (XP Pro),
>an AEC desktop (W2K), and a Thinkpad (W2K).  The Dell is where I have the
>printer installed and shared (supposedly).  All are totally current on
>Windows Update.  No domain, just a workgroup CROSBY.
>
>For some reason, I cannot access the Dell from either of the other PCs.
>Expanding My Network Places never shows it.  If I do a search for computers,
>I can _find_ the Dell, just can't _access_ anything.  Administrator has the
>same password on all 3 machines.  The Dell runs Zone Alarm (XP firewall is
>off) but it makes no difference if it is active or not.  From the Dell I can
>see and use shared directories on the other 2, just not vice versa.  I get
>"access denied".
>
>This has been going on for well over a year, maybe 2 years.  I have tried
>simple file sharing and not simple file sharing.  I have tried the
>troubleshooters.  I have asked tech savvy people I know.  I asked at the
>local PC store where my company buys stuff.  And at one time, it definitely
>worked.  Because it was sometimes months between trying to use the printer
>from one of the other PCs, I really have no clue what might have caused it
>to start failing.  Just one day it didn't work anymore.
>
>Any suggestions?
>
>Thanks.
>
>  
>