Re: SBS2003, Fully patched, and cannot RDP into machine
- From: Rosewood <Rosewood@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 2 Nov 2008 11:39:00 -0800
Thank you Susan. Your note about SP2 helped me in my searching. I found an
old post from Gary Wang and someone else who had this same issue back on
5/26/08.
He suggested reinstalling SP2. So I did just that and voila, all was good.
Thank you everyone for the help and suggestions here.
"Susan Bradley" wrote:
To set the record clear, 08-067 is not the trigger for the port issue..
The DNS patch way back in 08-037 is the trigger.
Are you trying this from several workstations?
If it's not listening, it's possible you lost this with sp2. I had an
issue where the TS driver got corrupted and I had to have support walk
me through manually reinstalling it.
3389 was not listening.
Rosewood wrote:
I think my reply was eaten :(
I set the exclusions and that didn't help. (Plus this started before
MS08-067, and those exclusions are UDP ports, not TCP)
Yes, the router is forwarded. If I forward it to a different machine, it
works fine. I can't connect either on the lan nor from the machine itself. If
I try to telnet to port 3389, there is no connection established. Nmap shows
the port as closed. Again, there is no firewall software. In fact, there is
no third party software on the machine other than the drivers.
I've gone through many, many reboots.
All services that are set to automatic are started. The terminal services
service is also started.
Remote Desktop is enabled and the RDP-Tcp shows up in the Terminal Services
configuration. I've even tried disabling it, rebooting, enabling it (trying
to connect, fail), rebooting (and then still no joy).
Bernie, I double checked the registry setting and it is still set to 3389. I
tried changing it to 3390 (no joy) and rebooting (no joy). I put it back at
3389 and even created a new host by copying the registry entry, changing the
name and setting this one to another random port. No joy. Again, nmap /
telnet shows the ports as closed.
Thank goodness for VNC so I at least have that for now, but I'd like to see
RDP going on this box once again.
The server is still running RDP 5.2 and neither a 5.2 client nor a 6.0
client can connect.
I've also set Terminal Services to only listen on the one NIC, no help there.
"Merv Porter [SBS-MVP]" wrote:
+ Could be one of the latest patches casuing issues if you didn't do the
port exclusions:
Microsoft Security Bulletin MS08-067 - Critical
http://msmvps.com/blogs/bradley/archive/2008/10/23/microsoft-security-bulletin-ms08-067-critical.aspx
+ In the router, you have port 3389 forwarded to the SBS NIC?
+ Is the SBS server handling DHCP for the network (SBS likes it better that
way)?
+ Have you rebooted the server a couple of times after hte upgrades?
+ Check your services and make sure they are all started.
+ Inthe server, right click on My Computer | Properties | Remote and insure
that the "Enable Remote Dektop on this computer" is checked.
--
Merv Porter [SBS-MVP]
============================
"Rosewood" <Rosewood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:87559CBD-30BB-43F0-8CE3-B56A50AE6397@xxxxxxxxxxxxxxxx
Thank you for the reply Merv.
The BPA comes back w/ no warnings.
Everything is up to date, including SBS2003 SP1.
Nmap shows the port as closed when scanning the localhost.
Could a service have been turned off or a registry setting changed in one
of
the patches that would keep it from running?
Agian, I don't see anything failing in event viewer either.
"Merv Porter [SBS-MVP]" wrote:
Install, update and run a scan with the SBS 2003 BPA:
Microsoft Windows Small Business Server 2003 Best Practices Analyzer
http://www.microsoft.com/downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en
When you upgraded the SBS server, did you install SBS 2003 SP1?
--
Merv Porter [SBS-MVP]
============================
"Rosewood" <Rosewood@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B42A27D6-0C5C-4893-B387-732BABF3E28F@xxxxxxxxxxxxxxxx
I took over yet another SBS2003 box last weekend. When I first started
working with it remotely, remote desktop worked fine.
The first thing I did was get the machine current with updates. It
looked
it
was still mostly SBS2003 RTM with just a few patches. No service packs.
Obviously this means I installed quite a few things all at once, so I'm
not
sure after which patch this started happening.
At some point I lost the ability to use RDP to connect to the server.
There
is no software firewall running on the machine itself. Even opening up
the
remote desktop program on the machine and trying to connect to itself
fails.
It is always the generic "This computer can't connect to the remote
computer. Try connecting again. If the problem continues, contact the
owner
of the remote computer or your network administrator."
Remote desktop is enabled. I tried disabling it, rebooting, and
re-enabling
it. Still no joy.
The RDP-Tcp connection is listed under Terminal Services Configuration.
Nothing in there looks like it would stop me from connecting.
Thank you
- References:
- SBS2003, Fully patched, and cannot RDP into machine
- From: Rosewood
- Re: SBS2003, Fully patched, and cannot RDP into machine
- From: Merv Porter [SBS-MVP]
- Re: SBS2003, Fully patched, and cannot RDP into machine
- From: Rosewood
- Re: SBS2003, Fully patched, and cannot RDP into machine
- From: Merv Porter [SBS-MVP]
- Re: SBS2003, Fully patched, and cannot RDP into machine
- From: Rosewood
- Re: SBS2003, Fully patched, and cannot RDP into machine
- From: Susan Bradley
- SBS2003, Fully patched, and cannot RDP into machine
- Prev by Date: Re: SBS2003, Fully patched, and cannot RDP into machine
- Next by Date: Re: Random client slow Internet browsing
- Previous by thread: Re: SBS2003, Fully patched, and cannot RDP into machine
- Next by thread: Re: SBS2003, Fully patched, and cannot RDP into machine
- Index(es):
Relevant Pages
|
