changed ISP now remote desktop won't work 1

[TheCandyman]

(Running 2003 small business server)

I changed our ISP company, hence new static IP addresses. But i can't get the remote desktop to work now. It worked fine before so i know nothing has change, except the new IP address for the machine.

I changed the IP and subnet on the outside network card and things worked great. What else do i need to change to get this working again?

 

[alliknowisnetworking]

Please let us know a little more. What sort of errors are you getting, etc,etc.

"Never assume users know what there talking about. Act as if all users are the dumbest form of earth scum there is"
-Myself
A+,Network+,MCP+2000

 

[mrdenny]

I'm assuming that your are trying to connect from outside.

From a command prompt type telnet {ip address} 3389. This will attempt to connect to the remote desktop service. If you get a blank window with a flashing cursor it connected, if you get an error message back, it did not.

It it doesn't connect it could be one of a few problems.
When you changed the static ip in your router the port mapping got wiped out and needs to be re-setup.
Your new ISP could be blocking port 3389 (the remote desktop port). (They should be able to tell you this over the phone or on thier web site).

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[TheCandyman]

Thanks for the tips,
1- My port 3389 is open, i did a few different port scans to verify.
2- If i connect locally to my server using remote desktop it works fine.

When i try remotely (public IP) i get this error:
The page cannot be displayed
There is a problem with the page you are trying to reach and it c

Friendly errors are off, and that's all it displays which is weird is cuts off in the middle of a sentence. So i am assuming i need to change the IP address somewhere, just can't find it.

 

[JimWells]

CandyMan,

Are you using the web-frontend for Remote Desktop? Do you know what IIS server is handling that for you? Might be that the IIS server is in a DMZ or not getting its port 80 requests forwarded through a firewall. If that's the case, then you'd have to make sure that the website running your RDP-frontend is LISTENING on the correct IP addresses....

 

[dkediger]

Yes - We need to know if this is the Remote Web Workplace ( the web frontend that JimWells mentioned) or straight RDP.

RWW utilizes SSL certificates. Depending on how the cert was issued, you might need to reissue it. This can be done in CIECW (Conect to Internat and Emial Connection Wizard.)

Also, it is common to access RWW using a hostname:

https://remote.domain.com/Remote.

You'll need to make sure your new ISP has that DNS hostname (remote.domain.com) - or whatever hostname you choose - mapped to your router's public IP.

 

[TheCandyman]

I have been trying the web front. I had been using a Cert in the past, so you think i should remake that?

I do have ports 8 & 25 open for emailing and 3389 for this remote access. I did a scan at

http://scan.sygatetech.com/quickscan.html

and it says my port 80 is:
"CLOSED, This port has responded to our probes. This means that you are not running any application on this port, but it is still possible for someone to crash your computer through known TCP/IP stack vulnerabilities."
Should i have this open?

 

[TheCandyman]

I remade the Cert, it did change the error i get. Now it shows this through the web interface:

10061 - Connection refused
Internet Security and Acceleration Server

I just want to thank you guys for the help, i'm at the end of my rope on this thing.

 

[dkediger]

Yes, for RWW, port 80 needs to be open, as well as the usual SSL port, 443. Since you're getting the ISA error, that means the request is at least getting through to your SBS server, but not getting processed from there.

I don't think that changing ISPs should have affected ISA, but I'll dig up my SBS/ISA/RWW config to see what's there.

Do you have a "public" website hosted on the SBS/ISA server?

Give me about an hour...

 

[TheCandyman]

Not public if you mean that i am actually hosting a website. I do have IIS running with the following folders 'Application Pools', 'Web Sites', and 'Web Service Entensions'

Inside the Web Sites folder is my companyweb (internal SBS website), SharePoint Central Administration, Microsoft SharePoint Administration, and Default Web Site. Inside the Default Web Site are the pages that users can connect to to see remote desktop login or remote Exchange(Outlook) emailing. And that website has the Local IP of my server. And the local IP never changed, only the public IP (i have two NICs one for the LAN, and the other for WAN IPs)

 

[dkediger]

That's your standard config then, which is good.

 

[dkediger]

What I would recommend, since it sounds like you're running an "out of the box" basic install with no customized web settings, is to re-run the CEICW (Configure Email and Internet Connections Wizard). This is the item under the Server Managament app/Internet and Email/Connect to the Internet.

Choose to specificly identify each option, rather than clicking through the "Keep Current Settings" for each page. On the Firewall page, choose to Enable. You'll get a notice about ISA and resetting back to default items. This should be OK if your running a plain vanilla setup. Even so, it should still keep any custom protocols you've enabled - but be safe and note these in the ISA manager. Select all the services you need on the firewall page.

On the Web Certificate page, choose to issue a new cert. For some reason, RWW/SBS seems to work better with the cert issued under the Public IP of the server, rather than the server's name or domain. Select the standard SSL port of 443.

Complete the Wizard and let it do its thing. After its done, I'd check the Exchange server's Default SMTP Connector Relay restrictions as I've seen the CEICW sometimes add the localhost address (127.0.0.1) to the "Only the List Below" setting. This list should be blank, unless you have very specific reasons, as it enables relaying.

On your firewall, make sure ports 80, 443, and I've got 4125 listed as RWW are open and forwarded to your server's ISA WAN address.

 

[TheCandyman]

dkediger,

your awesome! That fixed everything. I bet it was the old cert, just had to follow your advice and reconnect everthing again. Guess it makes more changes then i can get to manually.

THANKS TO ALL

 

[dkediger]

Glad it worked out...ISA/RWW/OWA can be a ticklish combination.