IT BS thread

Well I have confirmed that its not the router, but the windows 7 box itself that isn't accepting the connections. I can connect to 9 out of 10 PC's in my house using RDP. Of course my main box doesn't work. Swapped routers out with my old WRT-54G, works fine on all PC's but that one Windows 7 box.

I haven't re-formatted this machine in about 2 years anyways so I think its just quicker to do that then try and hunt down this daemon anymore.

 

have you used telnet to see if the port is open on the machine? you can also run a netstat -a to see if it is listening on port 3389

 

I suggested nmap, he didn't seem interested in checking that for some reason. netstat would be a real good one to check on the local machine as well...

 

What OS are you using to initiate the RDP connection? On the Win 7 box, right click Computer > properties > remote settings (on the left side). The second section, remote desktop, has three options. Is the middle or bottom checked? if the bottom, try the middle (less secure) and see if it works.

 

I wasn't not interested running Nmap, I use it all the time at work and at home. But I was at work at the time and I don't like running port sniffing tools in my office unless it is work related. Infosec freaks out over shit like that.

I ran Nmap, and my ports for RDP are open. Also all the custom ports I use are working as well.

Any PC/Mac/Phone isn't working RDP for my to my Windows 7 64bit box internally or externally. Again, this was working about 1-2 months ago as I use RDP almost daily.

I've tired all the secure and unsecured ways of getting at it. Still no go. Nmap shows the ports open and I can confirm on every other machine in my house that RDP is passing through the router. I'm remoted into my wife's PC (also windows 7 64bit) right now as I type. When I try mine - fail. The router logs show that data is passing through port 3389 when I check my syslog server. (all my customer RDP ports are working as well)

I ran into this with XP years ago and fixed it in the reg keys somehow, I just can't remember what I did.

 

Strange, I don't think I've ever had an issue when 3389 was actually listening. I've had issues before where RDP should've been running - but it wasn't, and as such 3389 wasn't listening on that IP.

I assume all the latest Windoze patches are installed? There was some Win2k8 patch that hit recently that fixed a bug similar to this. Not sure if it applies to 7 or not tho...

 

The issue i've seen is one that was described a few posts above. The wrong option was checked in the RDP settings allowing only secure connections. If you tried to connect with an rdp client that doesn't support the secure connection, then it wouldn't connect, just as if the port wasn't listening. I've also seen software installs/patches change this setting.

 

Ah, makes sense. Never ran into this one myself, but I don't do much desktop support...

 

Same issue with 2008 R2

 

I'm giving this universal print deal a try... How do I know which driver to add for the x86 printers?

 

Yeah I am fully patched/updated. I have a feeling that one of the patches didn't apply right.

I've ran into the security feature before when the company I worked for changed all the PC's to vista (Dear god that sucked).. Couldn't remote in since my main box was XP, already got bit in the ass for that one.

It's very odd, the services are running and the ports are open, the box just isn't accepting the connections. I created a new admin user, tried that login, same effect.

I know it doesn't matter but just food for thought. If I use RDP on this box that doesn't accept incoming connections, it works fine if I connect to any other PC (XP/Vista/7)..

When I get home I'm going to replace all the reg keys for terminal services and see what happens.. If I hose the OS, meh, re-installing 7 is fast.

I appreciate all the help!

 

What's the error you get when trying to connect?

 

is it a windows x64 print server?

 

If u can't connect using RDP, check for any open sessions on the machine you're trying to connect to.

Kill the disconnected ones or be sure there are enough available for you to connect.

 

Just the typical couldn't connect error. "Remote desktop can't connect to the remote computer for one of these reasons: yadda yadda

 

If you go back to computer properties and click remote settings, click on select users at the bottom. are there any users in the list? If not, try adding the everyone group and see if it makes a difference.

 

There is the admin account I created on the list and that's it. And of course my default account has access. I'm remoted into it now using slashtop. Working fine, RDP still a no go.

Edit: added everyone, still no change.. Rebooted it and waiting for it to come back up to test again.

 

IT guy having a slow work day.

I just read all 39 pages of this thread.

***

This is one of the nice days of being salaried

 

F salary. I'm tired of working 70 hr weeks for the same damned paycheck as if I was working 40 hr weeks...

I know that's why they put me on salary, but it still stinks

 

I haven't punched a clock in...

...

...

11 years. Wow.

I don't mind salary work, provided there are stipulations made up front by both worker and employer. But, my last two bosses were my best friend and a very good friend, so its a lot easier.

Yea, there's times that salary sucks. But really, I manage my risks to minimize the need for those times. Sure, I still get the occasional all-weekend datacenter move type things, or the overnight emergency...those come with the territory.

Damn, I'm getting old.