FTP access issues after renewing 3rd party certificate on SBS 2003 server with ISA 2004.

We recently renewed a 3rd party SSL certificate on a customers SBS 2003 server running ISA 2004 SP3.  Ever since we renewed the certificate the customer cannot connect to FTP sites through their ISA server.  The certificate is working fine and shows as the current certificate when using OWA or RWW.  If I set the servers Internet Explorer to use the proxy server, I cannot access any FTP sites, if I go in and remove the settings for the proxy server I can access FTP sites with no issues.  None of their workstations can access any FTP sites.  When I try to connect to an FTP site through the ISA server IE almost immediately goes to its default search page (Bing in this case).  When I try to connect to a FTP site using the proxy settings, I get the following entry while monitoring the servers IP in ISA:

Destination IP: XXX.XXX.XXX.XXX,  Destination Port: 21,  Protocol: ftp,  Action: Failed Connection Attempt,  Rule: SBS FTP Outbound Access Rule,  Source Network: Local Host,  Destination Network: External.

I have re-run the "Connect to the Internet" wizard and verified all the Access Rules are correct.  I have verified that the FTP Access Filter is also "Enabled" in the ISA configuration for Add-ins.

Anybody seen anything like this before or have any suggestions ??

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cris HannaSr IT Support EngineerCommented:
Sounds like FTP got set back to Read Only
optionpcAuthor Commented:
It was not the FTP read only settings...I had rechecked these numerous times. I reran the Connect to the Internet wizard about three more times and the issue was resolved. I have seen the wizard resolve problems in the past and assume that there was some corruption that was remedied during this process.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.