Erratic LAN problem with TPF

Nov 19, 2006 16 Replies

I use Tiny Personal Firewall 2.0.15A. It seems to be intermittently interferring with my LAN operation. Sometimes another LAN computer's drives are not accessable, but the LAN works ok the other direction. But if I turn the firewalls (all computers use TPF) off, then back on, access resumes normally. Can anyone who uses this firewall tell me how to set it not to do this? The IPs are in the trusted lists as they should be.



I've Googled but can't find any documentation or mentions of this problem.



Maybe a different firewwall?



TIA



Maybe no firewall or the Windows-Firewall at least.

Yours, VB.

Well, it should.

Most likely not, since even the developers obviously don't understand this piece of crap.

What problem? It is supposed to f*ck up your network connection.

What about a firewall in first place?

Maybe you want to post your problems here in detail.

Yours, VB.

Waht "permission errors" are you getting when you're doing what exactly?

Yours, VB.

Volker Birk wrote in news: snipped-for-privacy@news.uni-ulm.de:

I printed this out and will read it later.

I've never been able to get the LAN to work at all when the XP Home firewall is enabled. I keep getting permission errors.

Ken

Volker Birk wrote in news: snipped-for-privacy@news.uni-ulm.de:

What details should I add to my first message, besides OS is XP Home?

Ken

Volker Birk wrote in news: snipped-for-privacy@news.uni-ulm.de:

ulm.de:

"\\\\Kenneth\\c is not accessible. You might not have permission to use this resource. Contact the administrator of this service to find out if you access permissions.

The network path was not found."

Ken

[ permission errors with Windows-Firewall ]

Sounds like the Windows-Firewall was configured to block NetBIOS traffic. What exceptions had you made in the firewall config?

cu

59cobalt

Ansgar -59cobalt- Wiechers wrote in news: snipped-for-privacy@mid.individual.net:

Windows firewall in turned off. I will be switching to another firewall later this week, as soon as it arrives.

Ken

This does not sound like the Windows-Firewall. This must be something else.

If you're getting this on another computer, then maybe you mean that you cannot access network resources on the computer with the Windows-Firewall enabled. This is the reason, why one wants to have the Windows-Firewall: no network services. If you want to have an exception here, you may allow file service for your computer by configuring the Windows-Firewall.

If you have a setup with a local LAN, then it would be a very good idea to have a filtering NAT router at the gateway, though.

Yours, VB.

Volker Birk wrote in news: snipped-for-privacy@news.uni-ulm.de:

I know about XP firewall. Don't use it because I can't get the LAN to work. Discovered this years ago when I first set up the LAN.

I am currently using Tiny Personal Firewall 2.0.15A. I will be replacing this with a pre-Symantec Sygate Personal Firewall a friend is sending me on CD (9M is a big DL on a un-reliable dial-up connection). I hope that solves my problem. On the other hand, I've talked to people using my version of TPF, XP, and a LAN with no problems. So I have my fingers crossed.

Ken

Tiny has bad security design flaws - it installs a system service, which opens windows. So does Sygate. You better should use something from people, who have read and understood Microsoft's developer documentation.

Yours, VB.

We tested:

  • Kerio Personal Firewall 4.1.2 * Norman Personal Firewall 1.42 * Agnitum Outpost Firewall Pro 2.5 * Sygate Personal Firewall Pro 5.5 * Tiny Firewall 6.0 * Zone Labs ZoneAlarm Pro 5.5 * Symantec Norton Personal Firewall 2005

Unfortunately, it was no surprise, that all failed.

Yours, VB.

Volker Birk wrote in news: snipped-for-privacy@news.uni-ulm.de:

Whose firewall meets this criteria? I've heard bad things about Zone Alarm.

Ken

Windows Firewall, ISA Server 200x, Wipfw, InJoy Firewall, possibly the Cisco VPN Client stuff. There are some pseudo-legitimate alternative like Winsock Firewall, Jetico Personal Firewall and Comodo Firewall, but they're all full of this stupid trials of application control and some other nonsense.

Nah, this is all just a big misconception. It comes from people who actually believe that ZoneAlarm is supposed to provide security and not to f*ck up the system. They didn't understand the website and the documentation as the pure irony it obviously is.

ISA running on a non-dedicated Server is not certified as a Firewall Solution, even MS doesn't claim it to be a firewall on a non-dedicated server.

Windows XP Firewall - also open to any malware that wants to punch holes in it, as well as any legit app that wants to punch a hole in it.

Why would you fail to mention the above when you tell people that it's the only good solution?

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required