Re: Cannot Connect to TS in Admin mode on W2003
From: Michael Hubbard (mwhubbard_at_nospam.att.net)
Date: 02/03/04
- Next message: Tom Ausburne: "RE: Win XP PRO licens --> TS-CAL"
- Previous message: Vera Noest [MVP]: "Re: Because of a protocol error"
- In reply to: Huei Wang [MSFT]: "Re: Cannot Connect to TS in Admin mode on W2003"
- Next in thread: Huei Wang [MSFT]: "Re: Cannot Connect to TS in Admin mode on W2003"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Feb 2004 15:08:54 -0800
Yes, that was the first place I checked. Originally I had the administrator
in the "Permitted to remote connect" properties. This is a standalone
server in a workgroup and I renamed the administrator account. RDP still
worked fine but when I checked the remote properties today there was no user
in the permissions. I added the renamed admin account and figured that
would fix it. No such luck!
Michael Hubbard
"Huei Wang [MSFT]" <hueiwang@online.microsoft.com> wrote in message
news:%23Myldhq6DHA.2712@tk2msftngp13.phx.gbl...
> Can you check if remote desktop is enabled on this box, My Computer ->
> Properties -> Remote
>
> --
>
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
>
> "Michael Hubbard" <mwhubbard@nospam.att.net> wrote in message
> news:%23m0iIVq6DHA.1596@TK2MSFTNGP10.phx.gbl...
> > Dear Reader;
> > I read the MS TS FAQ at
> >
>
http://www.microsoft.com/windowsserver2003/community/centers/terminal/terminal_faq.mspx#XSLTfaqSection122123121120120
> > but didn't see anything relevant. When this first started I went to
> connect
> > and received an error saying all connections were in use. After that I
> > can't connect. I get the same message as when trying to connect to a
> > computer without Remote Desktop installed.
> >
> > I have TS installed in admin mode on w2003 web edition server. The TS
> > service is running, RPC service is running. Telephony, Remote access
> > connection manager and remote access auto connection manager are
disabled.
> > For several weeks I was able to connect from my XP box using the remote
> > desktop client. A netstat -a -n -o shows no service listening on 3389.
> I
> > rebooted the server, no effect. I opened network neighborhood, entire
> > network, Terminal Servers from the server and no TS boxes were found. I
> > have looked through the system and application log and don't see
anything
> > related to TS except messages about the spooler service being disabled
> (web
> > edition default).
> >
> > I don't think this is a network issue as I can still FTP, HTTP and Ping
> the
> > device and I can't connect even if I run the client on the server. I
> > expected to get the message that you can't connect to yourself. I'm not
> > getting the "Black Screen" issue but I did a successful ping -l 1470
> > 172.16.4.10 just in case. Automatic updates are disabled and I haven't
> > applied any patches recently. I did the IE patch today but TS was
already
> > broken. IIS with FTP, HTTP and SMTP are running on this box but they
have
> > been running since day one.
> >
> > This is the second server that this has occurred on. Any suggestions
> > appreciated!
> >
> > Michael Hubbard
> >
> > Output from netstat -a -n -o
> >
> > Active Connections
> >
> > Proto Local Address Foreign Address State
PID
> > TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
> 1880
> > TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
688
> > TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
> 1248
> > TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
> > TCP 0.0.0.0:1025 0.0.0.0:0 LISTENING
> 1036
> > TCP 0.0.0.0:1026 0.0.0.0:0 LISTENING
> 1484
> > TCP 0.0.0.0:1027 0.0.0.0:0 LISTENING
> 1880
> > TCP 0.0.0.0:1034 0.0.0.0:0 LISTENING
> 1732
> > TCP 0.0.0.0:2301 0.0.0.0:0 LISTENING
> 1804
> > TCP 0.0.0.0:2381 0.0.0.0:0 LISTENING
> 1804
> > TCP 0.0.0.0:2522 0.0.0.0:0 LISTENING
> 1732
> > TCP 0.0.0.0:2901 0.0.0.0:0 LISTENING
> 1732
> > TCP 0.0.0.0:8098 0.0.0.0:0 LISTENING
688
> > TCP 0.0.0.0:8099 0.0.0.0:0 LISTENING
688
> > TCP 0.0.0.0:8103 0.0.0.0:0 LISTENING
> 1732
> > TCP 0.0.0.0:19997 0.0.0.0:0 LISTENING
> 1740
> > TCP 0.0.0.0:19998 0.0.0.0:0 LISTENING
> 1760
> > TCP 0.0.0.0:49400 0.0.0.0:0 LISTENING
292
> > TCP 0.0.0.0:49401 0.0.0.0:0 LISTENING
> 1836
> > TCP 0.0.0.0:51010 0.0.0.0:0 LISTENING
> 1732
> > TCP 127.0.0.1:1787 127.0.0.1:51010 CLOSE_WAIT
> 3412
> > TCP 172.16.4.13:21 66.243.105.131:53944 ESTABLISHED
> 1880
> > TCP 172.16.4.13:2046 66.243.105.131:54012 ESTABLISHED
> 1880
> > UDP 0.0.0.0:161 *:*
232
> > UDP 0.0.0.0:445 *:* 4
> > UDP 0.0.0.0:500 *:*
> 1036
> > UDP 0.0.0.0:1028 *:*
232
> > UDP 0.0.0.0:1053 *:*
> 1404
> > UDP 0.0.0.0:3456 *:*
> 1880
> > UDP 0.0.0.0:4500 *:*
> 1036
> > UDP 127.0.0.1:123 *:*
> 1484
> > UDP 127.0.0.1:3456 *:*
> 1880
> > UDP 172.16.4.2:123 *:*
> 1484
> > UDP 172.16.4.4:123 *:*
> 1484
> > UDP 172.16.4.5:123 *:*
> 1484
> > UDP 172.16.4.8:123 *:*
> 1484
> > UDP 172.16.4.9:123 *:*
> 1484
> > UDP 172.16.4.10:123 *:*
> 1484
> > UDP 172.16.4.11:123 *:*
> 1484
> > UDP 172.16.4.12:123 *:*
> 1484
> > UDP 172.16.4.13:123 *:*
> 1484
> > UDP 172.16.4.14:123 *:*
> 1484
> >
> >
>
>
- Next message: Tom Ausburne: "RE: Win XP PRO licens --> TS-CAL"
- Previous message: Vera Noest [MVP]: "Re: Because of a protocol error"
- In reply to: Huei Wang [MSFT]: "Re: Cannot Connect to TS in Admin mode on W2003"
- Next in thread: Huei Wang [MSFT]: "Re: Cannot Connect to TS in Admin mode on W2003"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
