RDP stopped working

[Jonathan]

I don't know if anyone can shed any light on this. RDP stopped working
on our 2003 Server. The machine is actually running SBS 2003 with sp2 (I
am posting here since RDP is a more general Windows app). RDP was
working on this server and then between one use and then next, several
months ago it just stopped.

Details:

-Any client attempting to connect gets: "The client could not connect to
remote computer." (Including localhost)
-Remote Desktop is turned on in the Remote tab of System Properties.
-Terminal Services is in Administration mode.
-HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP\PortNumber
is set to 3389, but
-"netstat -a" does not show port 3389 (although it does show others).
-ISA is not installed and windows firewall is off.
-As far as I am able to tell, windows thinks that Remote Desktop is
ready to go but the port is not open.

Any ideas?

[Lanwench [MVP - Exchange]]

Jonathan <cantbuzz@noemail.noemail> wrote:
> I don't know if anyone can shed any light on this. RDP stopped working
> on our 2003 Server. The machine is actually running SBS 2003 with sp2
> (I am posting here since RDP is a more general Windows app).

But SBS does so many things its own way, you should always post in the
microsoft.public.windows.server.sbs group, even if you crosspost elsewhere.
I'm setting up my reply to crosspost there for the purposes of this thread.

> RDP was
> working on this server and then between one use and then next, several
> months ago it just stopped.

What happened right before then? When did you install W2003 SP2?

>
> Details:
>
> -Any client attempting to connect gets: "The client could not connect
> to remote computer." (Including localhost)
> -Remote Desktop is turned on in the Remote tab of System Properties.
> -Terminal Services is in Administration mode.

Where are you seeing that? There's no such thing as "...in administration
mode" in W2003 - that's just called Remote Desktop.And in SBS, you can't
install Terminal Services.


> -HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP\PortNumber
> is set to 3389, but
> -"netstat -a" does not show port 3389 (although it does show others).

Can you telnet?

telnet localhost 3389

?

> -ISA is not installed and windows firewall is off.

What antivirus?

> -As far as I am able to tell, windows thinks that Remote Desktop is
> ready to go but the port is not open.
>
> Any ideas?

[Jonathan]

Lanwench [MVP - Exchange] wrote:
> Jonathan <cantbuzz@noemail.noemail> wrote:
>> I don't know if anyone can shed any light on this. RDP stopped working
>> on our 2003 Server. The machine is actually running SBS 2003 with sp2
>> (I am posting here since RDP is a more general Windows app).
>
> But SBS does so many things its own way, you should always post in the
> microsoft.public.windows.server.sbs group, even if you crosspost elsewhere.
> I'm setting up my reply to crosspost there for the purposes of this thread.

Thanks!

>> RDP was
>> working on this server and then between one use and then next, several
>> months ago it just stopped.
>
> What happened right before then? When did you install W2003 SP2?

The sp2 log file is dated 6/14/07 so it is clear when we installed that,
but the rest is a bit obscure. We first noticed the problem back in
August but we weren't using rdp very often on that machine so it is hard
to be certain exactly when it started. (Since originally trying to find
a solution we've been using VNC as a work-around. But we're getting a
bit tired of VNC, so we are making another push to solve the original
problem)

>> Details:
>>
>> -Any client attempting to connect gets: "The client could not connect
>> to remote computer." (Including localhost)
>> -Remote Desktop is turned on in the Remote tab of System Properties.
>> -Terminal Services is in Administration mode.
>
> Where are you seeing that? There's no such thing as "...in administration
> mode" in W2003 - that's just called Remote Desktop.And in SBS, you can't
> install Terminal Services.

I was looking at Licensing, under Server Settings in Terminal Services
Configuration utility. As a point of interest, Terminal Services Manager
shows "RDP (listener)" listed under servername with a State of "Listen."

>> -HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP\PortNumber
>> is set to 3389, but
>> -"netstat -a" does not show port 3389 (although it does show others).
>
> Can you telnet?
>
> telnet localhost 3389

No. I get "Could not open connection to the host, on port 3389: Connect
failed"

>> -ISA is not installed and windows firewall is off.
>
> What antivirus?

Symantec Antivirus Corporate Ed. v.10.1.5. This is an upgrade since the
problem began. During the upgrade we had to uninstall the old version of
SAV...and we tried rdp in the interim (even though we were sure it
wasn't SAV) and there was no difference.

>> -As far as I am able to tell, windows thinks that Remote Desktop is
>> ready to go but the port is not open.
>>
>> Any ideas?
>
>
>
>

[George Yin]

Hello,

Thank you for your post and as well as to Lanwench for the inputting.

We have an article giving some detailed steps to troubleshoot some RDP
connection problems. So, please read the following article in detail and
see if it can help.

Troubleshooting RDP Client Connection Problems:
http://support.microsoft.com/kb/186645

As this issue relates to Windows SBS, and some configurations are not the
same. I would like to suggest that you post this issue to our SBS newsgroup
as Lanwench mentioned.

http://www.microsoft.com/technet/com...r/en-us/defaul
t.mspx?dg=microsoft.public.windows.server.sbs

We recommend posting for the appropriate product in order to get the most
qualified pool of support deliver team members, and other partners who read
the newsgroups regularly can either share their knowledge or learn from
your interaction with us.

Here are two tests just for your reference (on Windows SBS, these tests may
be different).
=================================

1. Create a new connection in the Terminal Services Configuration console,
then see if it works.

Open the Terminal Services Configuration console, right click the
"Connections" in the left pane, then click "Create New Connection" and
follow the wizard. If you have only one network adapter, you may need to
disable the existing connection first.

2. Disable all the non-Microsoft startup applications on the Startup tab
and all the non-Microsoft services on the Services tab of System
Configuration Utility, then reboot your server and see how it goes. You can
do this by entering msconfig in the Run dialog box.

Thank you for understanding.

Sincerely,
George Yin
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[George Yin]

Hello,

I am just writing to see how everything is going. If you have any updates
or need any further assistance on this issue, please feel free to let me
know. I am glad to be of assistance.

Sincerely,
George Yin
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Jonathan]

George,

I read through the kb article you listed but the problem does not appear
to be a tcp/ip issue since all of the other network related services on
the server seem to be working fine, port 3389 just seems to be
unavailable (see my 3/21 post for more details).

I have also tried stopping all non-microsoft services (except those that
are necessary for mail delivery - spam filter, etc) and this had no effect.

I was unable to create a new TS connection without removing the existing
connection (even after disabling it) and I am reluctant to remove the
existing connection in case I would be making the situation worse.

I have again crossposted this to microsoft.public.windows.server.sbs in
case someone there can help.

Thanks for the help!

George Yin(MSFT) wrote:
> Hello,
>
> Thank you for your post and as well as to Lanwench for the inputting.
>
> We have an article giving some detailed steps to troubleshoot some RDP
> connection problems. So, please read the following article in detail and
> see if it can help.
>
> Troubleshooting RDP Client Connection Problems:
> http://support.microsoft.com/kb/186645
>
> As this issue relates to Windows SBS, and some configurations are not the
> same. I would like to suggest that you post this issue to our SBS newsgroup
> as Lanwench mentioned.
>
> http://www.microsoft.com/technet/com...r/en-us/defaul
> t.mspx?dg=microsoft.public.windows.server.sbs
>
> We recommend posting for the appropriate product in order to get the most
> qualified pool of support deliver team members, and other partners who read
> the newsgroups regularly can either share their knowledge or learn from
> your interaction with us.
>
> Here are two tests just for your reference (on Windows SBS, these tests may
> be different).
> =================================
>
> 1. Create a new connection in the Terminal Services Configuration console,
> then see if it works.
>
> Open the Terminal Services Configuration console, right click the
> "Connections" in the left pane, then click "Create New Connection" and
> follow the wizard. If you have only one network adapter, you may need to
> disable the existing connection first.
>
> 2. Disable all the non-Microsoft startup applications on the Startup tab
> and all the non-Microsoft services on the Services tab of System
> Configuration Utility, then reboot your server and see how it goes. You can
> do this by entering msconfig in the Run dialog box.
>
> Thank you for understanding.
>
> Sincerely,
> George Yin
> Microsoft Online Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>

[Henrik \(Hear\)]

Jonathan / George

Check If the service, Network Location Awareness (NLA), is running, if not,
set It to automatic and reboot the server. Without It It will not get GPs as
it should and there fore runns Its own settings In its own Windows Firewall
wich Is by default to not allow RDP connections.

--
Henrik Arenblad, MCP SBS,


"Jonathan" <cantbuzz@noemail.noemail> wrote in message
news:O5Qvg%23$kIHA.2304@TK2MSFTNGP05.phx.gbl...
> George,
>
> I read through the kb article you listed but the problem does not appear
> to be a tcp/ip issue since all of the other network related services on
> the server seem to be working fine, port 3389 just seems to be unavailable
> (see my 3/21 post for more details).
>
> I have also tried stopping all non-microsoft services (except those that
> are necessary for mail delivery - spam filter, etc) and this had no
> effect.
>
> I was unable to create a new TS connection without removing the existing
> connection (even after disabling it) and I am reluctant to remove the
> existing connection in case I would be making the situation worse.
>
> I have again crossposted this to microsoft.public.windows.server.sbs in
> case someone there can help.
>
> Thanks for the help!
>
> George Yin(MSFT) wrote:
>> Hello,
>>
>> Thank you for your post and as well as to Lanwench for the inputting.
>>
>> We have an article giving some detailed steps to troubleshoot some RDP
>> connection problems. So, please read the following article in detail and
>> see if it can help.
>>
>> Troubleshooting RDP Client Connection Problems:
>> http://support.microsoft.com/kb/186645
>>
>> As this issue relates to Windows SBS, and some configurations are not the
>> same. I would like to suggest that you post this issue to our SBS
>> newsgroup as Lanwench mentioned.
>>
>> http://www.microsoft.com/technet/com...r/en-us/defaul
>> t.mspx?dg=microsoft.public.windows.server.sbs
>>
>> We recommend posting for the appropriate product in order to get the most
>> qualified pool of support deliver team members, and other partners who
>> read the newsgroups regularly can either share their knowledge or learn
>> from your interaction with us.
>>
>> Here are two tests just for your reference (on Windows SBS, these tests
>> may be different).
>> =================================
>>
>> 1. Create a new connection in the Terminal Services Configuration
>> console, then see if it works.
>>
>> Open the Terminal Services Configuration console, right click the
>> "Connections" in the left pane, then click "Create New Connection" and
>> follow the wizard. If you have only one network adapter, you may need to
>> disable the existing connection first.
>>
>> 2. Disable all the non-Microsoft startup applications on the Startup tab
>> and all the non-Microsoft services on the Services tab of System
>> Configuration Utility, then reboot your server and see how it goes. You
>> can do this by entering msconfig in the Run dialog box.
>>
>> Thank you for understanding.
>>
>> Sincerely,
>> George Yin
>> Microsoft Online Support
>> Microsoft Global Technical Support Center
>>
>> Get Secure! - www.microsoft.com/security
>> =====================================================
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> =====================================================
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>

[Jonathan]

Henrik and Terence,

Thank you both for the suggestions!

Henrik, I checked and Network Location Awareness was already started.

Terence, when I typed "removing the existing connection" in my previous
post I was referring to when I opened Terminal Services Configuration
console, right clicked "Connections" in the left pane, then clicked
"Create New Connection" and followed the wizard to create a new
connection. But since I have a single nic I got the message: "The new
connection must have a unique connection type, transport type or network
adaptor." I also received this message after I right-clicked the
original connection and selected "all tasks" and "disable."

I tried stopping the Windows Firewall/Internet Connection Sharing
service but it had no effect. (There is no 3rd party firewall installed)

I checked the registry key you mentioned and what I found was actually
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStatio
ns\RDP, rather than RDP-Tcp (I'm not sure if that is significant). But
PortNumber was set to port 3389.

I reran CEICW as you suggested. The only difference was that since the
server has a single nic I received a pop up saying that the wizard could
not configure the firewall. Rerunning CEICW did not solve the problem
and since I was uncomfortable leaving all web services exposed I reran
it (again) to disable everything but OWA. I did this after testing RWW -
although since I ran the test connecting to locahost (which is how I
have been testing all along) I don't think it would have mattered.

Here is the additional information you requested:

1. The error I get is "the client cannot connect to the remote computer."

2. The contents of netstat.txt are attached (see below).

3. I am able to log into RWW but when I try to connect to the server in
question ("connect to server desktops") I get the message: "Connectivity
to the remote computer could not be established."

4. ISA server is not installed.

5. The contents of ipconfig_sbs.txt is:

Windows IP Configuration

Host Name . . . . . . . . . . . . : servidor
Primary Dns Suffix . . . . . . . : latino.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : latino.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-15-C5-F7-16-6A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.2
Primary WINS Server . . . . . . . : 192.168.1.2


netstat.txt:


Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING 1508
TCP 0.0.0.0:42 0.0.0.0:0 LISTENING 3112
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:125 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 732
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:464 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:593 0.0.0.0:0 LISTENING 732
TCP 0.0.0.0:636 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:691 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:1075 0.0.0.0:0 LISTENING 1656
TCP 0.0.0.0:1096 0.0.0.0:0 LISTENING 1572
TCP 0.0.0.0:1101 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1102 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1103 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1104 0.0.0.0:0 LISTENING 2472
TCP 0.0.0.0:1105 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1112 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1141 0.0.0.0:0 LISTENING 3112
TCP 0.0.0.0:1146 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:1157 0.0.0.0:0 LISTENING 3304
TCP 0.0.0.0:1189 0.0.0.0:0 LISTENING 4008
TCP 0.0.0.0:2562 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:2967 0.0.0.0:0 LISTENING 2784
TCP 0.0.0.0:3268 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:3269 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:5800 0.0.0.0:0 LISTENING 3212
TCP 0.0.0.0:5900 0.0.0.0:0 LISTENING 3212
TCP 0.0.0.0:6001 0.0.0.0:0 LISTENING 4008
TCP 0.0.0.0:6002 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:6004 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:7588 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:55555 0.0.0.0:0 LISTENING 1508
TCP 127.0.0.1:53 0.0.0.0:0 LISTENING 1656
TCP 127.0.0.1:389 127.0.0.1:1074 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1094 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1121 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1151 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1184 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1192 ESTABLISHED 400
TCP 127.0.0.1:445 127.0.0.1:1234 ESTABLISHED 4
TCP 127.0.0.1:1074 127.0.0.1:389 ESTABLISHED 1656
TCP 127.0.0.1:1094 127.0.0.1:389 ESTABLISHED 1572
TCP 127.0.0.1:1121 127.0.0.1:389 ESTABLISHED 1812
TCP 127.0.0.1:1151 127.0.0.1:389 ESTABLISHED 3524
TCP 127.0.0.1:1184 127.0.0.1:389 ESTABLISHED 4008
TCP 127.0.0.1:1192 127.0.0.1:389 ESTABLISHED 1036
TCP 127.0.0.1:1234 127.0.0.1:445 ESTABLISHED 4
TCP 192.168.1.2:53 0.0.0.0:0 LISTENING 1656
TCP 192.168.1.2:135 192.168.1.159:1557 ESTABLISHED 732
TCP 192.168.1.2:135 192.168.1.181:1456 ESTABLISHED 732
TCP 192.168.1.2:139 0.0.0.0:0 LISTENING 4
TCP 192.168.1.2:139 192.168.1.22:3782 ESTABLISHED 4
TCP 192.168.1.2:389 192.168.1.2:1109 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1127 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1130 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1152 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1156 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1158 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1159 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1162 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1163 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1166 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1167 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1168 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1169 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1171 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1186 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1187 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1194 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1196 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1247 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1248 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1255 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1256 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:2003 ESTABLISHED 400
TCP 192.168.1.2:445 192.168.1.101:2679 ESTABLISHED 4
TCP 192.168.1.2:445 192.168.1.159:1417 ESTABLISHED 4
TCP 192.168.1.2:445 192.168.1.181:1352 ESTABLISHED 4
TCP 192.168.1.2:691 192.168.1.2:1128 ESTABLISHED 1812
TCP 192.168.1.2:691 192.168.1.2:1188 ESTABLISHED 1812
TCP 192.168.1.2:691 192.168.1.2:1195 ESTABLISHED 1812
TCP 192.168.1.2:1026 192.168.1.2:1111 ESTABLISHED 400
TCP 192.168.1.2:1026 192.168.1.2:1164 ESTABLISHED 400
TCP 192.168.1.2:1026 192.168.1.2:1262 ESTABLISHED 400
TCP 192.168.1.2:1026 192.168.1.2:1560 ESTABLISHED 400
TCP 192.168.1.2:1026 192.168.1.13:1447 ESTABLISHED 400
TCP 192.168.1.2:1109 192.168.1.2:389 ESTABLISHED 2472
TCP 192.168.1.2:1111 192.168.1.2:1026 ESTABLISHED 2472
TCP 192.168.1.2:1126 192.168.1.2:3268 ESTABLISHED 1812
TCP 192.168.1.2:1127 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1128 192.168.1.2:691 ESTABLISHED 1812
TCP 192.168.1.2:1130 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1136 192.168.1.2:389 CLOSE_WAIT 3304
TCP 192.168.1.2:1152 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1153 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1156 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1158 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1159 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1162 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1163 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1164 192.168.1.2:1026 ESTABLISHED 3524
TCP 192.168.1.2:1166 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1167 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1168 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1169 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1171 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1172 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1173 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1174 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1175 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1176 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1177 192.168.1.2:3268 CLOSE_WAIT 3524
TCP 192.168.1.2:1178 192.168.1.2:3268 CLOSE_WAIT 3524
TCP 192.168.1.2:1183 192.168.1.2:3268 ESTABLISHED 4008
TCP 192.168.1.2:1185 192.168.1.2:389 CLOSE_WAIT 4008
TCP 192.168.1.2:1186 192.168.1.2:389 ESTABLISHED 4008
TCP 192.168.1.2:1187 192.168.1.2:389 ESTABLISHED 4008
TCP 192.168.1.2:1188 192.168.1.2:691 ESTABLISHED 4008
TCP 192.168.1.2:1189 192.168.1.13:1427 ESTABLISHED 4008
TCP 192.168.1.2:1189 192.168.1.101:2663 ESTABLISHED 4008
TCP 192.168.1.2:1189 192.168.1.181:1350 ESTABLISHED 4008
TCP 192.168.1.2:1193 192.168.1.2:3268 ESTABLISHED 1036
TCP 192.168.1.2:1194 192.168.1.2:389 ESTABLISHED 1036
TCP 192.168.1.2:1195 192.168.1.2:691 ESTABLISHED 1036
TCP 192.168.1.2:1196 192.168.1.2:389 ESTABLISHED 4008
TCP 192.168.1.2:1247 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1248 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1255 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1256 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1257 192.168.1.2:3268 ESTABLISHED 1812
TCP 192.168.1.2:1262 192.168.1.2:1026 ESTABLISHED 3524
TCP 192.168.1.2:1560 192.168.1.2:1026 ESTABLISHED 400
TCP 192.168.1.2:2003 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:2022 192.168.1.2:1026 TIME_WAIT 0
TCP 192.168.1.2:2034 192.168.1.2:135 TIME_WAIT 0
TCP 192.168.1.2:2035 192.168.1.2:135 TIME_WAIT 0
TCP 192.168.1.2:2036 192.168.1.2:135 TIME_WAIT 0
TCP 192.168.1.2:2037 192.168.1.2:1026 TIME_WAIT 0
TCP 192.168.1.2:3268 192.168.1.2:1126 ESTABLISHED 400
TCP 192.168.1.2:3268 192.168.1.2:1183 ESTABLISHED 400
TCP 192.168.1.2:3268 192.168.1.2:1193 ESTABLISHED 400
TCP 192.168.1.2:3268 192.168.1.2:1257 ESTABLISHED 400
TCP 192.168.1.2:5900 71.150.251.97:49302 ESTABLISHED 3212
TCP 192.168.1.3:25 0.0.0.0:0 LISTENING 1508
TCP 192.168.1.3:125 0.0.0.0:0 LISTENING 1912
UDP 0.0.0.0:42 *:* 3112
UDP 0.0.0.0:135 *:* 732
UDP 0.0.0.0:161 *:* 2564
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 400
UDP 0.0.0.0:1035 *:* 792
UDP 0.0.0.0:1071 *:* 1656
UDP 0.0.0.0:1100 *:* 2216
UDP 0.0.0.0:1113 *:* 1812
UDP 0.0.0.0:1147 *:* 3524
UDP 0.0.0.0:1190 *:* 4008
UDP 0.0.0.0:1263 *:* 3524
UDP 0.0.0.0:1264 *:* 3524
UDP 0.0.0.0:1460 *:* 792
UDP 0.0.0.0:3456 *:* 1812
UDP 0.0.0.0:3457 *:* 1812
UDP 0.0.0.0:4500 *:* 400
UDP 127.0.0.1:53 *:* 1656
UDP 127.0.0.1:1068 *:* 1572
UDP 127.0.0.1:1070 *:* 1656
UDP 127.0.0.1:1073 *:* 1656
UDP 127.0.0.1:1108 *:* 2472
UDP 127.0.0.1:1114 *:* 1812
UDP 127.0.0.1:1133 *:* 1372
UDP 127.0.0.1:1135 *:* 3304
UDP 127.0.0.1:1140 *:* 3112
UDP 127.0.0.1:1148 *:* 3524
UDP 127.0.0.1:1182 *:* 4008
UDP 127.0.0.1:1191 *:* 1036
UDP 127.0.0.1:1197 *:* 340
UDP 127.0.0.1:1203 *:* 804
UDP 127.0.0.1:1235 *:* 1636
UDP 127.0.0.1:1242 *:* 2784
UDP 127.0.0.1:1657 *:* 1840
UDP 127.0.0.1:3456 *:* 1812
UDP 127.0.0.1:3457 *:* 1812
UDP 192.168.1.2:53 *:* 1656
UDP 192.168.1.2:67 *:* 3304
UDP 192.168.1.2:68 *:* 3304
UDP 192.168.1.2:88 *:* 400
UDP 192.168.1.2:137 *:* 4
UDP 192.168.1.2:138 *:* 4
UDP 192.168.1.2:389 *:* 400
UDP 192.168.1.2:464 *:* 400
UDP 192.168.1.2:2535 *:* 3304
UDP 192.168.1.3:88 *:* 400
UDP 192.168.1.3:389 *:* 400
UDP 192.168.1.3:464 *:* 400

[Jonathan]

Henrik and Terence,

Thank you both for the suggestions!

Henrik, I checked and Network Location Awareness was already started.

Terence, when I typed "removing the existing connection" in my previous
post I was referring to when I opened Terminal Services Configuration
console, right clicked "Connections" in the left pane, then clicked
"Create New Connection" and followed the wizard to create a new
connection. But since I have a single nic I got the message: "The new
connection must have a unique connection type, transport type or network
adaptor." I also received this message after I right-clicked the
original connection and selected "all tasks" and "disable."

I tried stopping the Windows Firewall/Internet Connection Sharing
service but it had no effect. (There is no 3rd party firewall installed)

I checked the registry key you mentioned and what I found was actually
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStatio
ns\RDP, rather than RDP-Tcp (I'm not sure if that is significant). But
PortNumber was set to port 3389.

I reran CEICW as you suggested. The only difference was that since the
server has a single nic I received a pop up saying that the wizard could
not configure the firewall. Rerunning CEICW did not solve the problem
and since I was uncomfortable leaving all web services exposed I reran
it (again) to disable everything but OWA. I did this after testing RWW -
although since I ran the test connecting to locahost (which is how I
have been testing all along) I don't think it would have mattered.

Here is the additional information you requested:

1. The error I get is "the client cannot connect to the remote computer."

2. The contents of netstat.txt are attached (see below).

3. I am able to log into RWW but when I try to connect to the server in
question ("connect to server desktops") I get the message: "Connectivity
to the remote computer could not be established."

4. ISA server is not installed.

5. The contents of ipconfig_sbs.txt is:

Windows IP Configuration

Host Name . . . . . . . . . . . . : servidor
Primary Dns Suffix . . . . . . . : latino.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : latino.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-15-C5-F7-16-6A
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.2
Primary WINS Server . . . . . . . : 192.168.1.2


netstat.txt:


Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:25 0.0.0.0:0 LISTENING 1508
TCP 0.0.0.0:42 0.0.0.0:0 LISTENING 3112
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:125 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 732
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:464 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:593 0.0.0.0:0 LISTENING 732
TCP 0.0.0.0:636 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:691 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:1075 0.0.0.0:0 LISTENING 1656
TCP 0.0.0.0:1096 0.0.0.0:0 LISTENING 1572
TCP 0.0.0.0:1101 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1102 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1103 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1104 0.0.0.0:0 LISTENING 2472
TCP 0.0.0.0:1105 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1112 0.0.0.0:0 LISTENING 1812
TCP 0.0.0.0:1141 0.0.0.0:0 LISTENING 3112
TCP 0.0.0.0:1146 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:1157 0.0.0.0:0 LISTENING 3304
TCP 0.0.0.0:1189 0.0.0.0:0 LISTENING 4008
TCP 0.0.0.0:2562 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:2967 0.0.0.0:0 LISTENING 2784
TCP 0.0.0.0:3268 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:3269 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:5800 0.0.0.0:0 LISTENING 3212
TCP 0.0.0.0:5900 0.0.0.0:0 LISTENING 3212
TCP 0.0.0.0:6001 0.0.0.0:0 LISTENING 4008
TCP 0.0.0.0:6002 0.0.0.0:0 LISTENING 3524
TCP 0.0.0.0:6004 0.0.0.0:0 LISTENING 400
TCP 0.0.0.0:7588 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:55555 0.0.0.0:0 LISTENING 1508
TCP 127.0.0.1:53 0.0.0.0:0 LISTENING 1656
TCP 127.0.0.1:389 127.0.0.1:1074 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1094 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1121 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1151 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1184 ESTABLISHED 400
TCP 127.0.0.1:389 127.0.0.1:1192 ESTABLISHED 400
TCP 127.0.0.1:445 127.0.0.1:1234 ESTABLISHED 4
TCP 127.0.0.1:1074 127.0.0.1:389 ESTABLISHED 1656
TCP 127.0.0.1:1094 127.0.0.1:389 ESTABLISHED 1572
TCP 127.0.0.1:1121 127.0.0.1:389 ESTABLISHED 1812
TCP 127.0.0.1:1151 127.0.0.1:389 ESTABLISHED 3524
TCP 127.0.0.1:1184 127.0.0.1:389 ESTABLISHED 4008
TCP 127.0.0.1:1192 127.0.0.1:389 ESTABLISHED 1036
TCP 127.0.0.1:1234 127.0.0.1:445 ESTABLISHED 4
TCP 192.168.1.2:53 0.0.0.0:0 LISTENING 1656
TCP 192.168.1.2:135 192.168.1.159:1557 ESTABLISHED 732
TCP 192.168.1.2:135 192.168.1.181:1456 ESTABLISHED 732
TCP 192.168.1.2:139 0.0.0.0:0 LISTENING 4
TCP 192.168.1.2:139 192.168.1.22:3782 ESTABLISHED 4
TCP 192.168.1.2:389 192.168.1.2:1109 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1127 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1130 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1152 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1156 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1158 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1159 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1162 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1163 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1166 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1167 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1168 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1169 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1171 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1186 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1187 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1194 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1196 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1247 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1248 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1255 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:1256 ESTABLISHED 400
TCP 192.168.1.2:389 192.168.1.2:2003 ESTABLISHED 400
TCP 192.168.1.2:445 192.168.1.101:2679 ESTABLISHED 4
TCP 192.168.1.2:445 192.168.1.159:1417 ESTABLISHED 4
TCP 192.168.1.2:445 192.168.1.181:1352 ESTABLISHED 4
TCP 192.168.1.2:691 192.168.1.2:1128 ESTABLISHED 1812
TCP 192.168.1.2:691 192.168.1.2:1188 ESTABLISHED 1812
TCP 192.168.1.2:691 192.168.1.2:1195 ESTABLISHED 1812
TCP 192.168.1.2:1026 192.168.1.2:1111 ESTABLISHED 400
TCP 192.168.1.2:1026 192.168.1.2:1164 ESTABLISHED 400
TCP 192.168.1.2:1026 192.168.1.2:1262 ESTABLISHED 400
TCP 192.168.1.2:1026 192.168.1.2:1560 ESTABLISHED 400
TCP 192.168.1.2:1026 192.168.1.13:1447 ESTABLISHED 400
TCP 192.168.1.2:1109 192.168.1.2:389 ESTABLISHED 2472
TCP 192.168.1.2:1111 192.168.1.2:1026 ESTABLISHED 2472
TCP 192.168.1.2:1126 192.168.1.2:3268 ESTABLISHED 1812
TCP 192.168.1.2:1127 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1128 192.168.1.2:691 ESTABLISHED 1812
TCP 192.168.1.2:1130 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1136 192.168.1.2:389 CLOSE_WAIT 3304
TCP 192.168.1.2:1152 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1153 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1156 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1158 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1159 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1162 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1163 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1164 192.168.1.2:1026 ESTABLISHED 3524
TCP 192.168.1.2:1166 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1167 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1168 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1169 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1171 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:1172 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1173 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1174 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1175 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1176 192.168.1.2:389 CLOSE_WAIT 3524
TCP 192.168.1.2:1177 192.168.1.2:3268 CLOSE_WAIT 3524
TCP 192.168.1.2:1178 192.168.1.2:3268 CLOSE_WAIT 3524
TCP 192.168.1.2:1183 192.168.1.2:3268 ESTABLISHED 4008
TCP 192.168.1.2:1185 192.168.1.2:389 CLOSE_WAIT 4008
TCP 192.168.1.2:1186 192.168.1.2:389 ESTABLISHED 4008
TCP 192.168.1.2:1187 192.168.1.2:389 ESTABLISHED 4008
TCP 192.168.1.2:1188 192.168.1.2:691 ESTABLISHED 4008
TCP 192.168.1.2:1189 192.168.1.13:1427 ESTABLISHED 4008
TCP 192.168.1.2:1189 192.168.1.101:2663 ESTABLISHED 4008
TCP 192.168.1.2:1189 192.168.1.181:1350 ESTABLISHED 4008
TCP 192.168.1.2:1193 192.168.1.2:3268 ESTABLISHED 1036
TCP 192.168.1.2:1194 192.168.1.2:389 ESTABLISHED 1036
TCP 192.168.1.2:1195 192.168.1.2:691 ESTABLISHED 1036
TCP 192.168.1.2:1196 192.168.1.2:389 ESTABLISHED 4008
TCP 192.168.1.2:1247 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1248 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1255 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1256 192.168.1.2:389 ESTABLISHED 1812
TCP 192.168.1.2:1257 192.168.1.2:3268 ESTABLISHED 1812
TCP 192.168.1.2:1262 192.168.1.2:1026 ESTABLISHED 3524
TCP 192.168.1.2:1560 192.168.1.2:1026 ESTABLISHED 400
TCP 192.168.1.2:2003 192.168.1.2:389 ESTABLISHED 3524
TCP 192.168.1.2:2022 192.168.1.2:1026 TIME_WAIT 0
TCP 192.168.1.2:2034 192.168.1.2:135 TIME_WAIT 0
TCP 192.168.1.2:2035 192.168.1.2:135 TIME_WAIT 0
TCP 192.168.1.2:2036 192.168.1.2:135 TIME_WAIT 0
TCP 192.168.1.2:2037 192.168.1.2:1026 TIME_WAIT 0
TCP 192.168.1.2:3268 192.168.1.2:1126 ESTABLISHED 400
TCP 192.168.1.2:3268 192.168.1.2:1183 ESTABLISHED 400
TCP 192.168.1.2:3268 192.168.1.2:1193 ESTABLISHED 400
TCP 192.168.1.2:3268 192.168.1.2:1257 ESTABLISHED 400
TCP 192.168.1.2:5900 71.150.251.97:49302 ESTABLISHED 3212
TCP 192.168.1.3:25 0.0.0.0:0 LISTENING 1508
TCP 192.168.1.3:125 0.0.0.0:0 LISTENING 1912
UDP 0.0.0.0:42 *:* 3112
UDP 0.0.0.0:135 *:* 732
UDP 0.0.0.0:161 *:* 2564
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 400
UDP 0.0.0.0:1035 *:* 792
UDP 0.0.0.0:1071 *:* 1656
UDP 0.0.0.0:1100 *:* 2216
UDP 0.0.0.0:1113 *:* 1812
UDP 0.0.0.0:1147 *:* 3524
UDP 0.0.0.0:1190 *:* 4008
UDP 0.0.0.0:1263 *:* 3524
UDP 0.0.0.0:1264 *:* 3524
UDP 0.0.0.0:1460 *:* 792
UDP 0.0.0.0:3456 *:* 1812
UDP 0.0.0.0:3457 *:* 1812
UDP 0.0.0.0:4500 *:* 400
UDP 127.0.0.1:53 *:* 1656
UDP 127.0.0.1:1068 *:* 1572
UDP 127.0.0.1:1070 *:* 1656
UDP 127.0.0.1:1073 *:* 1656
UDP 127.0.0.1:1108 *:* 2472
UDP 127.0.0.1:1114 *:* 1812
UDP 127.0.0.1:1133 *:* 1372
UDP 127.0.0.1:1135 *:* 3304
UDP 127.0.0.1:1140 *:* 3112
UDP 127.0.0.1:1148 *:* 3524
UDP 127.0.0.1:1182 *:* 4008
UDP 127.0.0.1:1191 *:* 1036
UDP 127.0.0.1:1197 *:* 340
UDP 127.0.0.1:1203 *:* 804
UDP 127.0.0.1:1235 *:* 1636
UDP 127.0.0.1:1242 *:* 2784
UDP 127.0.0.1:1657 *:* 1840
UDP 127.0.0.1:3456 *:* 1812
UDP 127.0.0.1:3457 *:* 1812
UDP 192.168.1.2:53 *:* 1656
UDP 192.168.1.2:67 *:* 3304
UDP 192.168.1.2:68 *:* 3304
UDP 192.168.1.2:88 *:* 400
UDP 192.168.1.2:137 *:* 4
UDP 192.168.1.2:138 *:* 4
UDP 192.168.1.2:389 *:* 400
UDP 192.168.1.2:464 *:* 400
UDP 192.168.1.2:2535 *:* 3304
UDP 192.168.1.3:88 *:* 400
UDP 192.168.1.3:389 *:* 400
UDP 192.168.1.3:464 *:* 400

[George Yin]

Hello,

Thank you for the updating.

Well, then I think maybe you should wait to see if anyone in the SBS
newsgroup has any information on this, because some settings may be not the
same as on Windows Server 2003. And if you get any resolution, please also
keep us informed.

Meanwhile, Please check the "Device\Video0" registry key. This problem may
occur when the Device\Video0 registry key is missing. If this registry
value is corrupt, the RDP-Tcp will be displayed as "Down" state.

Remote Desktop Protocol Clients Cannot Connect to Terminal Services Server
http://support.microsoft.com/?id=270588

In addition, it is reported that MySQL can influence the operation of
terminal services. If you have this service enabled, please temporarily
disable MySQL to test this problem again.

Thank you again for understanding.

Sincerely,
George Yin
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Jonathan]

George,

Thank you for the suggestions. The "Device\Video0" seems to be set up
correctly and mysql is not running on the server. I will certainly pass
along a resolution if I can achieve one.

Thanks again

Jonathan

George Yin(MSFT) wrote:
> Hello,
>
> Thank you for the updating.
>
> Well, then I think maybe you should wait to see if anyone in the SBS
> newsgroup has any information on this, because some settings may be not the
> same as on Windows Server 2003. And if you get any resolution, please also
> keep us informed.
>
> Meanwhile, Please check the "Device\Video0" registry key. This problem may
> occur when the Device\Video0 registry key is missing. If this registry
> value is corrupt, the RDP-Tcp will be displayed as "Down" state.
>
> Remote Desktop Protocol Clients Cannot Connect to Terminal Services Server
> http://support.microsoft.com/?id=270588
>
> In addition, it is reported that MySQL can influence the operation of
> terminal services. If you have this service enabled, please temporarily
> disable MySQL to test this problem again.
>
> Thank you again for understanding.
>
> Sincerely,
> George Yin
> Microsoft Online Support
> Microsoft Global Technical Support Center
>
> Get Secure! - www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>

[Jonathan]

Replacing termdd.sys did the trick! Thanks for the help.

Terence Liu [MSFT] wrote:
> Hello Jonathan,
>
> Thank you for your update.
>
> This is really a strange issue.
>
> Do you install the windows server 2003 sp2 on your SBS? If yes, please
> perform the following steps:
>
> a. Copy the "termdd.sys" file from the Service Pack 2 cab folder located in
> "%WINDOWS%\Driver Cache\i386" to the "%windows%\system32\drivers".
>
> b. Please ensure Terminal Services on SBS is started. If it stop, please
> start it manually.
>
> c. Restart SBS and test this issue.
>

[Jonathan]

Replacing termdd.sys did the trick! Thanks for the help.

Terence Liu [MSFT] wrote:
> Hello Jonathan,
>
> Thank you for your update.
>
> This is really a strange issue.
>
> Do you install the windows server 2003 sp2 on your SBS? If yes, please
> perform the following steps:
>
> a. Copy the "termdd.sys" file from the Service Pack 2 cab folder located in
> "%WINDOWS%\Driver Cache\i386" to the "%windows%\system32\drivers".
>
> b. Please ensure Terminal Services on SBS is started. If it stop, please
> start it manually.
>
> c. Restart SBS and test this issue.
>

[Jonathan]

Replacing termdd.sys did the trick! Thanks for the help.

Terence Liu [MSFT] wrote:
> Hello Jonathan,
>
> Thank you for your update.
>
> This is really a strange issue.
>
> Do you install the windows server 2003 sp2 on your SBS? If yes, please
> perform the following steps:
>
> a. Copy the "termdd.sys" file from the Service Pack 2 cab folder located in
> "%WINDOWS%\Driver Cache\i386" to the "%windows%\system32\drivers".
>
> b. Please ensure Terminal Services on SBS is started. If it stop, please
> start it manually.
>
> c. Restart SBS and test this issue.
>

[Jonathan]

Replacing termdd.sys did the trick! Thanks for the help.

Terence Liu [MSFT] wrote:
> Hello Jonathan,
>
> Thank you for your update.
>
> This is really a strange issue.
>
> Do you install the windows server 2003 sp2 on your SBS? If yes, please
> perform the following steps:
>
> a. Copy the "termdd.sys" file from the Service Pack 2 cab folder located in
> "%WINDOWS%\Driver Cache\i386" to the "%windows%\system32\drivers".
>
> b. Please ensure Terminal Services on SBS is started. If it stop, please
> start it manually.
>
> c. Restart SBS and test this issue.
>