Remote Desktop Broke, Cant Fix it

[copenhagen69]

Soooo, the only thing I know is that I switch from Charter to ATT and now my RDP wont work.

I have:
Updated my router with new IP for my server.
my updated RDP port is open
I have checked msconfig, everything is still the same
I have checked registry and my stuff is still there and correct
I have checked services.msc and all is good there
I have checked my firewall rules and all is good there

When I tried telnet I got the below ...

telnet: connect to address 192.168.0.150: Connection refused
telnet: Unable to connect to remote host
Drews-iMac:~ Drew$ telnet 192.168.0.150
Trying 192.168.0.150...
telnet: connect to address 192.168.0.150: Operation timed out
telnet: Unable to connect to remote host

The connection refused was when I had my FW off AV off and Torgaurd VPN off
Timed out was when I had all that on.

Literally the only thing that has changed was new internet service. Unless Msoft sent out a new update and that screwed something else up on it ... not sure.

thoughts on where else to look or what else could be the problem?

 

[stinger608]

What up bro?
Great to see ya posting man!!

What OS are you running on the system? 10 or are you still running 7?

 

[Kursah]

So looking at that IP address you're using RDP over LAN not WAN, so unless they replaced your router the external Internet connection shouldn't mean jack. You're also using IP address instead of hostname which takes DNS out of the equation as well.

Did you double check that you have the receiving workstation still set for all users or explicit users?

Are you able to RDP from another Windows PC? If not what error(s) do you receive?

When testing with telnet, you should be using telnet 192.168.0.150 3389 or other RDP specified port, as can be confirmed here. This also applies to Linux and MacOS terminals.

Port 3389 is reserved for RDP in Windows OSes by default, you mention an updated RDP port...have you checked whether the default port works still? If you did not explicitly block it in the firewall then it should still be open for use.

Hope that helps and am curious what this issue turns out to be!

 

[OneMoar]

you should not be using telnet period
my first guess is the isp supplied router either not having ports open or some odd ICMP/STP policy

 

[Solaris17]

They probably swapped your router. check the actual forward rules on that.

 

[eidairaman1]

So looking at that IP address you're using RDP over LAN not WAN, so unless they replaced your router the external Internet connection shouldn't mean jack. You're also using IP address instead of hostname which takes DNS out of the equation as well.

Did you double check that you have the receiving workstation still set for all users or explicit users?

Are you able to RDP from another Windows PC? If not what error(s) do you receive?

When testing with telnet, you should be using telnet 192.168.0.150 3389 or other RDP specified port, as can be confirmed here. This also applies to Linux and MacOS terminals.

Port 3389 is reserved for RDP in Windows OSes by default, you mention an updated RDP port...have you checked whether the default port works still? If you did not explicitly block it in the firewall then it should still be open for use.

Hope that helps and am curious what this issue turns out to be!

They probably swapped your router. check the actual forward rules on that.

As an Ex ATT premtech, I hated those cpes (gateways), either 2 wire, pace, motorolla/arris. Complete junk if you ask me.

The only good modem I had was a Netgear, they do have a vdsl model too, but if you have IP TV service you have to be an isp to buy a netgear gateway.

Course ATT went directtv now hive...

 

[copenhagen69]

What up bro?
Great to see ya posting man!!

What OS are you running on the system? 10 or are you still running 7?

hey Stinger!! Long time bud! Been crazy busy with work/life and 2 small kids haha

OS Win 7

So looking at that IP address you're using RDP over LAN not WAN, so unless they replaced your router the external Internet connection shouldn't mean jack. You're also using IP address instead of hostname which takes DNS out of the equation as well.

Did you double check that you have the receiving workstation still set for all users or explicit users?

Are you able to RDP from another Windows PC? If not what error(s) do you receive?

When testing with telnet, you should be using telnet 192.168.0.150 3389 or other RDP specified port, as can be confirmed here. This also applies to Linux and MacOS terminals.

Port 3389 is reserved for RDP in Windows OSes by default, you mention an updated RDP port...have you checked whether the default port works still? If you did not explicitly block it in the firewall then it should still be open for use.

Hope that helps and am curious what this issue turns out to be!

Well, right now I am trying to just see if I can connect to it using anything. Figured lan would be easier at the moment ... They tried to replace my router, but I turned off all their router features (I think) and now just use it for the modem side. I plugged my router back in and double checked the settings there and nothing had changed.

When I try telnet like you suggested I get:
Operation timed out
telnet: Unable to connect to remote host

which going off the site, means its blocked somewhere on my WAN setup ... default port and my new port both get same error message

you should not be using telnet period
my first guess is the isp supplied router either not having ports open or some odd ICMP/STP policy

whats wrong with telnet to check things?
Ya I am curious if there is more things I need to do on the supplied ATT Router/Modem to get it to stop blocking certain things. I will look more into that today.

They probably swapped your router. check the actual forward rules on that.

I switched it back, just not sure I turned everything off on the ATT or opened everything I should have ...

As an Ex ATT premtech, I hated those cpes (gateways), either 2 wire, pace, motorolla/arris. Complete junk if you ask me.

The only good modem I had was a Netgear, they do have a vdsl model too, but if you have IP TV service you have to be an isp to buy a netgear gateway.

Course ATT went directtv now hive...

yes, main reason I went back to my router

 

[newtekie1]

The first thing to do is get it working on the private network, you LAN. If it doesn't work there, then it definitely won't work from outside your network.

So use a second computer connected to the same network and try to remote into the computer you are trying to control using the LAN IP address. Once you have that working, move on to getting it working from the WAN.

 

[copenhagen69]

I have never had this much problem with DRP ever before .. not sure what is happening.

I will try the LAN connection first, if that fails then I am still blocking the RDP port somehow?

Googling this issue I saw that Chrome has an RDP type setup through the browser, does this work well?

 

[Ahhzz]

I have never had this much problem with DRP ever before .. not sure what is happening.

I will try the LAN connection first, if that fails then I am still blocking the RDP port somehow?

Googling this issue I saw that Chrome has an RDP type setup through the browser, does this work well?

It can, it requires you to login to your Google account from both locations.

I +1 the "Try from inside first". That will let you know if the issue is router, or PC. If router, that's a forwarding issue. If PC, well, that's a big can of "this, or this... or that... or even that!" Keep us updated.

Things to look at for interior problems. Verify in the system properties, in remote settings, that RDP is allowed, and from any connection.
I saw a smatter of "updated port". Did you change your default RDP port? That's located (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber). Make sure either it's set to 3389, or you're adding the port manually (192.168.0.150:3389).
I have had Norton crash to the point that one of the Email, Browsing, or RDP services gets blocked, without the others failing. Make sure it's all disabled, last resort (if you have the license), uninstall and reinstall your A/V.