Tiny Firewall all ****ed up now...

Well, I decided to download the 2.0.14 version (or something like that) of the Tiny Personal Firewall, and it seemed to work for a while...

But then I couldn't connect to the 'net with my DSL connection. (didn't try normal dialup) And my proxy software for the home network would NOT recognize my network adapter, and finally, running winipcfg.exe or ipconfig.exe would return an error dialog box saying that my TCP/IP configuration information was corrupted! I didn't find any options or help about this problem with the firewall, and I don't have the installer for the old version!

I might just have to go <bleh-from-what-I-remember> ZA or a reeeally-old version of Conseal I have here somewhere... Or sygate, who knows....

Anyone ever have a similar problem? Uninstalling the firewall software FINALLY made it go away.

I had the same problem with my home network but winipcfg still worked, if you have some money you cuold get winroute, it's about the same firewall but with some proxy stuff also for dsl connections (i don't have such connection one so i'm not sure):)

ok my english is ****ed up so send me as many replyz as you can about my grammar and stuff so i can learn (at school we don't learn this kind off words, only some stupid about asking were the postoffice is and so on)

I had a problem connecting to the net........using Tiny and a Netgear 311 with a dsl connection. (It worked for a week)
I was able to connect after I unplugged the Netgear and reinstalled Winpoet.
Maybe Tiny doesn't play well with certain software or hardware.

:cool:

i have problem too with tiny i instal it and all that reboot machine and start it then when i try to turn on firewall i just keep on geting some errors i dont know why but heheh its dumb for sure
so al stick to ZA

gratez all



______ ______ ______


I Am D3stR0y3r


______ ______ ______

Tiny Firewall has some big problems. Suposedly they are trying to fix them for the next release, but some of the less blatent bugs have been around for a while...

Check out this thread about TPF 2.0.15 final

http://www.antionline.com/showthread...hreadid=119211

My preliminary opinions in finding a new firewall:

Zone Alarm:
Same as it was before, exactly the kind of lack of in-depth control that I dislike, but still okay for the less-knowledgable (or more hurried) user.

Agnitum Outpost
Confusing layout and interface. I'm just not comfortable with it, because I am never sure where to find the settings I want.

Sygate 4.2
Didn't work with my internet-connection-sharing proxy either, apparently. More like TPF than some of the others in terms of customizability, but I didn't spend much time with it after I learned that it didn't play well with my network setup.

Well, to update on this...

Checking out Agnitum Outpost, and then ZA, wasn't too complex...

But problems started when I tried to use Sygate. Now, I didn't want to jump to conclusions, I thought my ISP was at fault... because I couldn't ping or get any access through my DSL connection, even after trying nearly every reconfiguration in the book. But after quite a bit of looking, I've fixed it by moving the culprit... which seems to have been files left behind by ZoneAlarm!

To be fair, I didn't do the scheduled restart that they always recommend after uninstalling, so that could be part of it. Anyway, some files with VS*.vxd and VS*.dll were in my c:\windows\ and c:\windows\system\ directory, and the file properties showed that they were ZA files, so I moved them out, and now it seems to work...

I had thought that it was Sygate messing things up. I might go back and try Sygate again, now, seeing that the problems might have been due to the ZA leftovers. At any rate, I just wanted to get this info out in case anyone else seemed to have similar problems.

Quote:

---

Anyway, some files with VS*.vxd and VS*.dll were in my c:\windows\ and c:\windows\system\ directory, and the file properties showed that they were ZA files, so I moved them out, and now it seems to work...

---

Those files must have been loaded from somewhere, so removing them problably caused a conflict, not a big deal, but if you want your system to start a second or two faster, id suggest searching the registry for the files you deleted.

The installer might have removed the registry entrys after the re-start. I just assume that you tried re-starting your system to get it to work again.

-8trak

Well, I think the chain of usage was from system.ini, rather than the registry. I think that ZA just somehow didn't remove them quite right in that instance. (These were VXDs and DLLs)

Has anybody on here used Norton's Firewall?

I've managed to 'obtain' a copy of the 2002 version and I would appreciate any input from someone who has used it, before I install it.
I've currently got TPF installed, but I'm having a couple of proplems with it on my Windows XP Pro install, so I'm currently looking for alternatives.

Cheers. :thumbsup:

I have tried a number of firewalls and quite like Tiny, I have it running on NT4 and it runs great, I have not experienced an problems with it, but I was using the latest version of zone alarm and had a lot of problems with that but it is a good firewall.

Quote:

---

Originally posted by Terr
Well, I think the chain of usage was from system.ini, rather than the registry. I think that ZA just somehow didn't remove them quite right in that instance. (These were VXDs and DLLs)

---

Edit: I was wrong. Registry. Bleh. Icky registry.

REAL Edit:
DOH! I meant to EDIT that last post for the sake of posterity, not to QUOTE it... Sorry, didn't mean to push this thing back up to the surface! Down boy, down!

I am using Tiny now and i didn't have any problems but who knows they might come up later. But while we on this subject i was just wondering having a tiny firewall does it open any high ports on a box. My box is now listening to a port 44334 udp and tcp so i was just curios. I added rules to block any traffic from and two this port. This only appeard after installing Tiny?!?

Quote:

---

Originally posted by Terr
Well, I decided to download the 2.0.14 version (or something like that) of the Tiny Personal Firewall, and it seemed to work for a while...

---

I had a similair problem last week..
A local company was totally exposed to the Internet and needed a solution fast..

Meanwhile waiting for the hardware router, decided I to do a quick and dirty solution (read Tiny)..

I installed Tiny and a lots of services stopped to work and when uninstalling the program Tiny also uninstalled some files needed for Win terminalservices or maybe Tiny replaced them during installation, I'm not sure yet..

You can guess that I was happy and had a big shiny face almost divided in half due to the big grin..

5 min work ended up in 8 hours of phonecalls with consults and reinstalling the "nice" computer..

The internet connection did work all the time though :-).

--
//Learn from the wise and do a RTFM before do quick and dirty solutions !!

I have been tinkering with TPF 2.0.15 for a little while now, and I have had nothing but problems. I would get it loaded and enstate filter rules and so on and all was fine...until I closed my internet connection and dialed in once again. Once connected to my ISP, I couldn't resolve any web pages at all. I mean nothing. I also have ZonaAlarm 2.6 and that has worked great since I downloaded it over a year ago (although it wasn't 2.6 back then). Once I disabled TPF, and re-enabled ZA all was well. I am quite baffled by now. I am running XP Home edition in case anyone was curious. If there is anybody out there with similar problems with a similar system let me know.

I'm using ZoneAlarm for my home PC (Win98.2ndEd) and I discovered some of the same things you guys have said - I found that if I uninstalled ZoneAlarm completely, then tried to go online, I couldn't resolve any pages. I would connect to my ISP, but I couldn't bring any pages up - reinstalled ZoneAlarm, everything worked fine. I figured that the uninstaller didn't quite get all the files removed and there was some sort of discrepancy but I haven't had the chance to dig deep into Windows to find those files. So thanks Terr, for telling me where they are at - saves me a little time. And eeshman, was this the first time that you disabled ZoneAlarm? You may have had similar problems to mine.

Maverick811 - This was the first time that I disabled ZA. What I did was just started my computer and then closed out ZA completely and started Tiny Firewall. I couldn't resolve web pages, however I was connected to my ISP. At first I thought I had entered the filter rules incorrectly into the TPF administrator console, but I had it running fine the first time I put them in so it very well could be a problem with ZA. I am going to try to completely uninstall ZA and then run Tiny and we'll see what happens.

:hello:
ZA and BlackIce work very well together so why not try them together?:killcompu

Eeshman, that sounds like a good idea - I would use Zone Alarms' uninstaller then reboot. Then, I would go into your \windows\system and \windows directories and be sure to move all of the files that are part of Zone Alarm - Terr says that they all are vs*.vxd or vs*.dll files - you can double check by clicking the properties and seeing if they are registered to Zone Alarm. Then, just for testing, with no firewall running, connect to your ISP and verify that you can resolve web pages. Then install TPF and you can work with it - you just have to be sure to completely get rid of Zone Alarm before you can continue.

Quote:

---

Originally posted by bAgZ
I am using Tiny now and i didn't have any problems but who knows they might come up later. But while we on this subject i was just wondering having a tiny firewall does it open any high ports on a box. My box is now listening to a port 44334 udp and tcp so i was just curios. I added rules to block any traffic from and two this port. This only appeard after installing Tiny?!?

---

I believe those are remote administration ports for tiny. For reasons unknown to me, it actually opens connections when you open the administration locally.

I finally removed ZA from my PC. I did the easy way...Add/Remove Programs utility. When I did that, I was asked if I wanted to remove some files that were shared, but will be of no use once ZA is removed and I opted to leave them there until I could find out exactly what they did and what program they were registered to. So far, so good. Tiny is performing like a champ and I can connect to my ISP and resolve web pages. All my rules are in place and all ports previously found open (used SuperScan) that were unneeded are now closed off to the rest of the world. Live and learn I guess. Hope this helps anyone.

The Eeshman

Quote:

---

Originally posted by Terr
To be fair, I didn't do the scheduled restart that they always recommend after uninstalling, so that could be part of it. Anyway, some files with VS*.vxd and VS*.dll were in my c:\windows\ and c:\windows\system\ directory, and the file properties showed that they were ZA files, so I moved them out, and now it seems to work...

---

The 'VS' files that you are referring to are indeed left by ZoneAlarm...they are parts of the 'VectorSafe' portion of ZoneAlarm. What they do, I'm not sure, but they remain after uninstall, as do your ZoneAlarm settings...I uninstalled ZA after becoming frustrated with it, and reinstalled it (to see if that would make a difference), and it remembered my settings (tied to the Registry), and recognized the old (there was an update of ZA between these times) VectorSafe files, and asked to replace them. All this after multiple shutdown restarts in the time between uninstall and 'fresh' install. It hasn't been a problem since, so I'll stick with it for now.

Hope this helps shed some light...

Ouroboros

its gota be the software for sure, i have it on my dialup connection and i get init errors when windoze starts but then i just run it again after it crashes (illegal op error) and then its fine