Hi Allie, ACM> When I had the problem, a restart of TB! would *always* result in a ACM> successful mailcheck. When it stopped checking for mail, it would ACM> stop and never successfully check again until I restarted TB!.
The same thing happened to me - every time I started TB! (with ZA running) I would get about 5 minutes worth of successful checks. Quit and restart TB and I'd get another 5 minutes. When you start a program ZA keeps a table of where the program is accessing. When you quit, that table is removed. Therefore a quit + restart would clear that table. ACM> My connection problems were later not confined to TB! but my ACM> internet connection in general. I'd be connected to my ISP but ACM> nothing would be happening. Only an OS reboot would fix this, ... ACM> all the time. That's probably a different and bigger issue. :-) ACM> When I installed uninstalled ZA and installed TPF, I created 2 rules ACM> for TB!. One to allow connections to the remote machine's port 25 ACM> and another for remote port 110, with both connecting at a single IP ACM> (not a hostname who's IP may vary). I never had problems again. Unfortunately with ZA you can't create specific rules like that - you can only say the remote server(s) IP address is good. But my first suggestion/solution that I gave is effectively the same as what you did with TPF. ACM> The changing IP may be one factor but I doubt that it's the only ACM> one. True. I don't have a full Windows debugger available on my email box to be able to track down what's going on in the background otherwise. I'm more of a unix guy (actually a networking guy) than a windows expert. :-) ACM> Be that as it may, I don't think ZA is to blame for the frequently ACM> reported problems with auto-mail checking. In my case it was - I could reproduce the problem and create the test environment so I found out what it was. There may be (and most likely are) other problems/bugs/issues that look and act in similar ways. ACM> Especially since a clean install of TB! fixes the problem. This ACM> seems to point to a TB! problem. Hate to say it, but it's probably is a windows problem actually. They (MS) have an absolutely horrid TCP/IP implementation in the OS, so I wouldn't be surprised to find it does things in weird and unexpected ways... Cheers, Ross. -- Ross West mailto:[EMAIL PROTECTED] ________________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
