SBS RWW Server Desktop connection has stopped working

After the ADSL router for this client died and was replaced this problem began.

I remotely support a client who runs a single SBS 2003 server SP2
This server runs Exchange 2003 and Sharepoint 2.0
ISA Server 2004 SP3 is installed.
Server has a single NIC.
Until 2 months ago I could connect to the Server Desktop from my home. I'd login to RWW and then use the Server Desktop link from there. Now it doesn't work.
I get the message "The client coul;d not connect to the remote computer" "Remote connections might not be enabled ... etc"
I can monitor the connection attempt on the SBS box using ISA Server Monitoring.
It lists Initiated Connection and then Closed Connection a short while later. The extra information with the latter has an error FWX_E_ABORTIVE_SHUTDOWN 0x80074e21.
I've looked this up on, but the article there only suggests that the listener is not running. The listener is running becuase if I try this conmnection from a client on the same LAN as the server it works fine.
Who is Participating?
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.

James MontgomeryCommented:
Chances are port 4125 have not been setup to forward following the replacement of the router.

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
ComputerFundiAuthor Commented:
Thanks. Don't know why I didn't double-check the settings before.
I had setup a service called RWW for UDP port 4125 and placed it in the forwarding table (on this router setting up a service and then adding to the forward ports table are two separate steps). I had also setup service RWW1 for TCP 4125, but had omitted to place that service in the forwarding table. Now it's in the forwarding table and I can get at my server desktop again.

Glad it was a simple solution, wish I'd asked earlier!
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
Microsoft Forefront ISA Server

From novice to tech pro — start learning today.