I meant to say it had nothing to do with the VPN setup, which was fine. (I was also having POP3 mail server problems, also caused by the same thing.)
Main Topics
Browse All TopicsRunning ISA 2004 with sp3 on server 2000, sp4.
VPN was working fine.
Suddenly, all outside clients get an "error 651...modem error" when trying to connect using the same connection string they were always using.
I tried disabling/enabling VPN in ISA2004 and rebooting, but that did nothing.
Any ideas would be GREATLY appreciated.
Thanks.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: gateguardPosted on 2008-10-31 at 10:49:47ID: 22852528
I found the problem. It actually had nothing to do with my POP3 server rule. A few days ago I set up a secure ftp server using a custom protocol and I misunderstood something I read about secure ftp wanting to have access to a large number of upper-range ports for random connections (or something like that) and I added a wide range of ports in my user-defined protocol. Much too wide a range. When I finally got around to doing a netstat -an and saw all the ports my machine was listening on, it clued me in to the problem.
So I deleted that rule, and that protocol and now everything is working.
I think the server was just bogged down with too much darn listening.