Windows NT Vista and 2003 server

  • Thread starter Thread starter chas
  • Start date Start date
C

chas

I'm trying to connect to a windows 2003 sever which is on the local
network, via Vista's remote desktop.

I get the error message:- "The client could not connect. You are already
connected to the console of this computer. A new console session cannot
be established."

I have no idea what this message means or how to fix it. A terminal
session worked fine from XP before I upgraded to vista. A friend of mine
with a very similar set-up, has exactly the same error when he tries to
connect to his server also.

Can any tell what I'm doing wrong?

Chas
 
Perhaps a bit more detailed information might help.

For example:
which version of 2003 Server (e.g. Standard, Enterprise, SP1, R2, SP2)
is the Terminal Server role installed on the 2003 server (not required, but
changes the picture a bit)
which edition of Vista
are either or both the Vista and 2003 in a domain
are you attempting to logon using the 2003 server's local Administrator user
account, another local account or a domain user account

I routinely use RDC from Vista to logon to 2003 servers (mostly those with
Terminals Services installed) without difficulty.

I tried several scenarios in my test environment to try and reproduce your
situation, but was unsuccssful - RDC from Vista to 2003 server worked
correctly in every scenario.

So, there must be something particular to your situation, thus more details
might help.

--
Bruce Sanderson MVP Printing
http://members.shaw.ca/bsanders

It is perfectly useless to know the right answer to the wrong question.



"chas" <chas756@aintispannnn.yahoo.co.uk> wrote in message
news:u3uFaytxHHA.4592@TK2MSFTNGP05.phx.gbl...
> I'm trying to connect to a windows 2003 sever which is on the local
> network, via Vista's remote desktop.
>
> I get the error message:- "The client could not connect. You are already
> connected to the console of this computer. A new console session cannot be
> established."
>
> I have no idea what this message means or how to fix it. A terminal
> session worked fine from XP before I upgraded to vista. A friend of mine
> with a very similar set-up, has exactly the same error when he tries to
> connect to his server also.
>
> Can any tell what I'm doing wrong?
>
> Chas
 
Hello Chas,

Maybe this helps you:
http://www.accendo.co.uk/blog/

Best regards

Myweb
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

> I'm trying to connect to a windows 2003 sever which is on the local
> network, via Vista's remote desktop.
>
> I get the error message:- "The client could not connect. You are
> already connected to the console of this computer. A new console
> session cannot be established."
>
> I have no idea what this message means or how to fix it. A terminal
> session worked fine from XP before I upgraded to vista. A friend of
> mine with a very similar set-up, has exactly the same error when he
> tries to connect to his server also.
>
> Can any tell what I'm doing wrong?
>
> Chas
>
 
Bruce Sanderson wrote:
> Perhaps a bit more detailed information might help.
>
> For example:
> which version of 2003 Server (e.g. Standard, Enterprise, SP1, R2, SP2)
> is the Terminal Server role installed on the 2003 server (not required,
> but changes the picture a bit)
> which edition of Vista
> are either or both the Vista and 2003 in a domain
> are you attempting to logon using the 2003 server's local Administrator
> user account, another local account or a domain user account
>
> I routinely use RDC from Vista to logon to 2003 servers (mostly those
> with Terminals Services installed) without difficulty.
>
> I tried several scenarios in my test environment to try and reproduce
> your situation, but was unsuccssful - RDC from Vista to 2003 server
> worked correctly in every scenario.
>
> So, there must be something particular to your situation, thus more
> details might help.
>

Ok Bruce thanks for the reply.

The 2003 server is the standard version with sp2 and fully updated from
windows update. I use Exchange and ISA 2000 and the terminal server
services are installed on the server. The vista PC is a domain member
with the 2003 server as the PDC.

I can connect to the server with remote desktop using XP without any
problems at all. Therefore, IMHO its not the server that has the issue.

I get the same error if I try from 32bit Vista Business edition and from
Vista Ultimate 64bit edition. The vista firewall is set to allow remote
desktop.

If I browse using remote desktop, it sees the server. I get the same
error no matter what account I try to use, even with a non-existent
username.

"The client could not connect. You are already connected to the console
of this computer. A new console session cannot be established."

Chas
 
chas wrote:

> I'm trying to connect to a windows 2003 sever which is on the local
> network, via Vista's remote desktop.
>
> I get the error message:- "The client could not connect. You are
> already connected to the console of this computer. A new console
> session cannot be established."
>
> I have no idea what this message means or how to fix it. A terminal
> session worked fine from XP before I upgraded to vista. A friend of
> mine with a very similar set-up, has exactly the same error when he
> tries to connect to his server also.
>
> Can any tell what I'm doing wrong?
>
> Chas

It took some time but I finally managed to fix this problem. It seems
that Vista uses the default TS port for something else.

My fix was to change the port number in the registry

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp]PortNumber.

I set mine to 3388 and everything is working now and I can connect to
my server again.

--
 
Did you change the port on the W2k3 TS or on the Vista client?

I am quite confused since both options do not explain why it is
working now.

a) Changed port on the server

The TS client software on the Vista machine does expect the TS to
listen on port 3389. So this cannot have worked.

b) Changed port on the client

The RDC software (TS client) does not (or at least should not) open a
server port, and by no means 3389, for outgoing connections.

Does anyone have an explanation for this?

Helge

On 24 Aug., 22:07, "Chas" <chas...@aintispannnn.yahoo.co.uk> wrote:
> chas wrote:
> > I'm trying to connect to a windows 2003 sever which is on the local
> > network, via Vista's remote desktop.
>
> > I get the error message:- "The client could not connect. You are
> > already connected to the console of this computer. A new console
> > session cannot be established."
>
> > I have no idea what this message means or how to fix it. A terminal
> > session worked fine from XP before I upgraded to vista. A friend of
> > mine with a very similar set-up, has exactly the same error when he
> > tries to connect to his server also.
>
> > Can any tell what I'm doing wrong?
>
> > Chas
>
> It took some time but I finally managed to fix this problem. It seems
> that Vista uses the default TS port for something else.
>
> My fix was to change the port number in the registry
>
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
> Server\WinStations\RDP-Tcp]PortNumber.
>
> I set mine to 3388 and every is working now and I can connect to my
> server again.
>
> --
 
No. I agree with you that there seems to be something weird going on.
Changing the listening port on the client should have no impact
whatsoever. The only thing which could help is changing the listening
port on the server AND connecting to <servername>:3388 from the Vista
client.
But already the first error message is puzzeling, since AFAIK you get
this error message only if you connect to the localhost (i.e. the
Vista client).
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Helge Klein <Helge.Klein@googlemail.com> wrote on 24 aug 2007 in
microsoft.public.windows.terminal_services:

> Did you change the port on the W2k3 TS or on the Vista client?
>
> I am quite confused since both options do not explain why it is
> working now.
>
> a) Changed port on the server
>
> The TS client software on the Vista machine does expect the TS
> to listen on port 3389. So this cannot have worked.
>
> b) Changed port on the client
>
> The RDC software (TS client) does not (or at least should not)
> open a server port, and by no means 3389, for outgoing
> connections.
>
> Does anyone have an explanation for this?
>
> Helge
>
> On 24 Aug., 22:07, "Chas" <chas...@aintispannnn.yahoo.co.uk>
> wrote:
>> chas wrote:
>> > I'm trying to connect to a windows 2003 sever which is on the
>> > local network, via Vista's remote desktop.
>>
>> > I get the error message:- "The client could not connect. You
>> > are already connected to the console of this computer. A new
>> > console session cannot be established."
>>
>> > I have no idea what this message means or how to fix it. A
>> > terminal session worked fine from XP before I upgraded to
>> > vista. A friend of mine with a very similar set-up, has
>> > exactly the same error when he tries to connect to his server
>> > also.
>>
>> > Can any tell what I'm doing wrong?
>>
>> > Chas
>>
>> It took some time but I finally managed to fix this problem. It
>> seems that Vista uses the default TS port for something else.
>>
>> My fix was to change the port number in the registry
>>
>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>> Server\WinStations\RDP-Tcp]PortNumber.
>>
>> I set mine to 3388 and every is working now and I can connect
>> to my server again.
 
I changed the port on my local Vista PC (the client) and didn't touch
the server. What ever it did I can connect via remote desktop now.

Chas


Helge Klein wrote:
> Did you change the port on the W2k3 TS or on the Vista client?
>
> I am quite confused since both options do not explain why it is
> working now.
>
> a) Changed port on the server
>
> The TS client software on the Vista machine does expect the TS to
> listen on port 3389. So this cannot have worked.
>
> b) Changed port on the client
>
> The RDC software (TS client) does not (or at least should not) open a
> server port, and by no means 3389, for outgoing connections.
>
> Does anyone have an explanation for this?
>
> Helge
>
> On 24 Aug., 22:07, "Chas" <chas...@aintispannnn.yahoo.co.uk> wrote:
>> chas wrote:
>>> I'm trying to connect to a windows 2003 sever which is on the local
>>> network, via Vista's remote desktop.
>>> I get the error message:- "The client could not connect. You are
>>> already connected to the console of this computer. A new console
>>> session cannot be established."
>>> I have no idea what this message means or how to fix it. A terminal
>>> session worked fine from XP before I upgraded to vista. A friend of
>>> mine with a very similar set-up, has exactly the same error when he
>>> tries to connect to his server also.
>>> Can any tell what I'm doing wrong?
>>> Chas
>> It took some time but I finally managed to fix this problem. It seems
>> that Vista uses the default TS port for something else.
>>
>> My fix was to change the port number in the registry
>>
>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>> Server\WinStations\RDP-Tcp]PortNumber.
>>
>> I set mine to 3388 and every is working now and I can connect to my
>> server again.
>>
>> --
>
>
 
Strange as it may be changing the the default port allowed me to connect
to my server again.

Its a long story. A friend has an almost identical setup up to me. We
both upgraded our PC's to Vista. His server is a SBS2003 server (Not
R2), while mine is a Standard 2003 server.

Both Vista PC's gave the same error ie "The client could not connect.
You are already connected to the console of this computer. A new console
session cannot be established." when trying to connect to our servers
via Remote desktop. My friend had more of and issue than I did, as
remote desktop was his only method of logging onto his server (no screen
or keyboard). It was working fine with XP before the upgrade to Vista
but not afterwards.

I asked the question before in this newsgroup but everyone said there
should not be an issue with vista, but as both of us had identical
errors clearly there is an issue.

Changing [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp]PortNumber fixed the problem on both vista
PC's. No changes where made to either server.

Chas


Vera Noest [MVP] wrote:
> No. I agree with you that there seems to be something weird going on.
> Changing the listening port on the client should have no impact
> whatsoever. The only thing which could help is changing the listening
> port on the server AND connecting to <servername>:3388 from the Vista
> client.
> But already the first error message is puzzeling, since AFAIK you get
> this error message only if you connect to the localhost (i.e. the
> Vista client).
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> Helge Klein <Helge.Klein@googlemail.com> wrote on 24 aug 2007 in
> microsoft.public.windows.terminal_services:
>
>> Did you change the port on the W2k3 TS or on the Vista client?
>>
>> I am quite confused since both options do not explain why it is
>> working now.
>>
>> a) Changed port on the server
>>
>> The TS client software on the Vista machine does expect the TS
>> to listen on port 3389. So this cannot have worked.
>>
>> b) Changed port on the client
>>
>> The RDC software (TS client) does not (or at least should not)
>> open a server port, and by no means 3389, for outgoing
>> connections.
>>
>> Does anyone have an explanation for this?
>>
>> Helge
>>
>> On 24 Aug., 22:07, "Chas" <chas...@aintispannnn.yahoo.co.uk>
>> wrote:
>>> chas wrote:
>>>> I'm trying to connect to a windows 2003 sever which is on the
>>>> local network, via Vista's remote desktop.
>>>> I get the error message:- "The client could not connect. You
>>>> are already connected to the console of this computer. A new
>>>> console session cannot be established."
>>>> I have no idea what this message means or how to fix it. A
>>>> terminal session worked fine from XP before I upgraded to
>>>> vista. A friend of mine with a very similar set-up, has
>>>> exactly the same error when he tries to connect to his server
>>>> also.
>>>> Can any tell what I'm doing wrong?
>>>> Chas
>>> It took some time but I finally managed to fix this problem. It
>>> seems that Vista uses the default TS port for something else.
>>>
>>> My fix was to change the port number in the registry
>>>
>>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>>> Server\WinStations\RDP-Tcp]PortNumber.
>>>
>>> I set mine to 3388 and every is working now and I can connect
>>> to my server again.
 
Weird!
There are known problems with Vista clients in an SBS2003 domain, I
don't know the details, but the sbs newsgroup has numerous posts
about it.
But I've never seen a report like yours with Vista and Windows
Server 2003, and I don't understand what's going on.
Could you post the output of a "netstat -an" command, to check what
is listening on port 3389?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

chas <chas756@aintispannnn.yahoo.co.uk> wrote on 27 aug 2007 in
microsoft.public.windows.terminal_services:

> Strange as it may be changing the the default port allowed me to
> connect to my server again.
>
> Its a long story. A friend has an almost identical setup up to
> me. We both upgraded our PC's to Vista. His server is a SBS2003
> server (Not R2), while mine is a Standard 2003 server.
>
> Both Vista PC's gave the same error ie "The client could not
> connect. You are already connected to the console of this
> computer. A new console session cannot be established." when
> trying to connect to our servers via Remote desktop. My friend
> had more of and issue than I did, as remote desktop was his only
> method of logging onto his server (no screen or keyboard). It
> was working fine with XP before the upgrade to Vista but not
> afterwards.
>
> I asked the question before in this newsgroup but everyone said
> there should not be an issue with vista, but as both of us had
> identical errors clearly there is an issue.
>
> Changing
> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
> Server\WinStations\RDP-Tcp]PortNumber fixed the problem on both
> vista PC's. No changes where made to either server.
>
> Chas
>
>
> Vera Noest [MVP] wrote:
>> No. I agree with you that there seems to be something weird
>> going on. Changing the listening port on the client should have
>> no impact whatsoever. The only thing which could help is
>> changing the listening port on the server AND connecting to
>> <servername>:3388 from the Vista client.
>> But already the first error message is puzzeling, since AFAIK
>> you get this error message only if you connect to the localhost
>> (i.e. the Vista client).
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> Helge Klein <Helge.Klein@googlemail.com> wrote on 24 aug 2007
>> in microsoft.public.windows.terminal_services:
>>
>>> Did you change the port on the W2k3 TS or on the Vista client?
>>>
>>> I am quite confused since both options do not explain why it
>>> is working now.
>>>
>>> a) Changed port on the server
>>>
>>> The TS client software on the Vista machine does expect the TS
>>> to listen on port 3389. So this cannot have worked.
>>>
>>> b) Changed port on the client
>>>
>>> The RDC software (TS client) does not (or at least should not)
>>> open a server port, and by no means 3389, for outgoing
>>> connections.
>>>
>>> Does anyone have an explanation for this?
>>>
>>> Helge
>>>
>>> On 24 Aug., 22:07, "Chas" <chas...@aintispannnn.yahoo.co.uk>
>>> wrote:
>>>> chas wrote:
>>>>> I'm trying to connect to a windows 2003 sever which is on
>>>>> the local network, via Vista's remote desktop.
>>>>> I get the error message:- "The client could not connect. You
>>>>> are already connected to the console of this computer. A new
>>>>> console session cannot be established."
>>>>> I have no idea what this message means or how to fix it. A
>>>>> terminal session worked fine from XP before I upgraded to
>>>>> vista. A friend of mine with a very similar set-up, has
>>>>> exactly the same error when he tries to connect to his
>>>>> server also.
>>>>> Can any tell what I'm doing wrong?
>>>>> Chas
>>>> It took some time but I finally managed to fix this problem.
>>>> It seems that Vista uses the default TS port for something
>>>> else.
>>>>
>>>> My fix was to change the port number in the registry
>>>>
>>>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
>>>> Server\WinStations\RDP-Tcp]PortNumber.
>>>>
>>>> I set mine to 3388 and every is working now and I can connect
>>>> to my server again.
 
While connected via RD.

Z:\>netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2804 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3388 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49162 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49187 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49199 0.0.0.0:0 LISTENING
TCP 127.0.0.1:25 0.0.0.0:0 LISTENING
TCP 127.0.0.1:110 0.0.0.0:0 LISTENING
TCP 127.0.0.1:143 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2804 127.0.0.1:49233 ESTABLISHED
TCP 127.0.0.1:49233 127.0.0.1:2804 ESTABLISHED
TCP 127.0.0.1:49515 127.0.0.1:49516 ESTABLISHED
TCP 127.0.0.1:49516 127.0.0.1:49515 ESTABLISHED
TCP 127.0.0.1:49517 127.0.0.1:49518 ESTABLISHED
TCP 127.0.0.1:49518 127.0.0.1:49517 ESTABLISHED
TCP 192.168.10.10:139 0.0.0.0:0 LISTENING
TCP 192.168.10.10:49231 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49506 192.168.10.1:445 ESTABLISHED
TCP 192.168.10.10:49519 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49527 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49528 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49587 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49591 192.168.10.1:3389 ESTABLISHED
TCP 192.168.10.10:49597 192.168.10.1:139 TIME_WAIT
TCP 192.168.10.10:49598 192.168.10.1:16725 ESTABLISHED
TCP 192.168.10.10:49599 192.168.10.1:16727 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:3388 [::]:0 LISTENING
TCP [::]:3389 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49158 [::]:0 LISTENING
TCP [::]:49162 [::]:0 LISTENING
TCP [::]:49187 [::]:0 LISTENING
TCP [::]:49199 [::]:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49152 *:*
UDP 127.0.0.1:49155 *:*
UDP 127.0.0.1:49157 *:*
UDP 127.0.0.1:49159 *:*
UDP 127.0.0.1:49161 *:*
UDP 127.0.0.1:49163 *:*
UDP 127.0.0.1:49166 *:*
UDP 127.0.0.1:49167 *:*
UDP 127.0.0.1:49172 *:*
UDP 127.0.0.1:49179 *:*
UDP 127.0.0.1:49181 *:*
UDP 127.0.0.1:49183 *:*
UDP 127.0.0.1:49195 *:*
UDP 127.0.0.1:49196 *:*
UDP 127.0.0.1:49210 *:*
UDP 127.0.0.1:49213 *:*
UDP 127.0.0.1:49214 *:*
UDP 127.0.0.1:49217 *:*
UDP 127.0.0.1:49344 *:*
UDP 127.0.0.1:49369 *:*
UDP 192.168.10.10:137 *:*
UDP 192.168.10.10:138 *:*
UDP 192.168.10.10:1900 *:*
UDP 192.168.10.10:49178 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::1]:1900 *:*
UDP [::1]:49176 *:*
UDP [fe80::100:7f:fffe%8]:1900 *:*
UDP [fe80::100:7f:fffe%8]:49177 *:*

Z:\>

When not connected
Z:\>netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2804 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3388 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49162 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49187 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49199 0.0.0.0:0 LISTENING
TCP 127.0.0.1:25 0.0.0.0:0 LISTENING
TCP 127.0.0.1:110 0.0.0.0:0 LISTENING
TCP 127.0.0.1:143 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2804 127.0.0.1:49233 ESTABLISHED
TCP 127.0.0.1:49233 127.0.0.1:2804 ESTABLISHED
TCP 127.0.0.1:49515 127.0.0.1:49516 ESTABLISHED
TCP 127.0.0.1:49516 127.0.0.1:49515 ESTABLISHED
TCP 127.0.0.1:49517 127.0.0.1:49518 ESTABLISHED
TCP 127.0.0.1:49518 127.0.0.1:49517 ESTABLISHED
TCP 192.168.10.10:139 0.0.0.0:0 LISTENING
TCP 192.168.10.10:49231 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49506 192.168.10.1:445 ESTABLISHED
TCP 192.168.10.10:49519 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49527 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49528 192.168.10.1:1745 ESTABLISHED
TCP 192.168.10.10:49598 192.168.10.1:16725 TIME_WAIT
TCP 192.168.10.10:49599 192.168.10.1:16727 ESTABLISHED
TCP 192.168.10.10:49602 192.168.10.1:16726 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:3388 [::]:0 LISTENING
TCP [::]:3389 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49158 [::]:0 LISTENING
TCP [::]:49162 [::]:0 LISTENING
TCP [::]:49187 [::]:0 LISTENING
TCP [::]:49199 [::]:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49152 *:*
UDP 127.0.0.1:49155 *:*
UDP 127.0.0.1:49157 *:*
UDP 127.0.0.1:49159 *:*
UDP 127.0.0.1:49161 *:*
UDP 127.0.0.1:49163 *:*
UDP 127.0.0.1:49166 *:*
UDP 127.0.0.1:49167 *:*
UDP 127.0.0.1:49172 *:*
UDP 127.0.0.1:49179 *:*
UDP 127.0.0.1:49181 *:*
UDP 127.0.0.1:49183 *:*
UDP 127.0.0.1:49195 *:*
UDP 127.0.0.1:49196 *:*
UDP 127.0.0.1:49210 *:*
UDP 127.0.0.1:49213 *:*
UDP 127.0.0.1:49214 *:*
UDP 127.0.0.1:49217 *:*
UDP 127.0.0.1:49344 *:*
UDP 192.168.10.10:137 *:*
UDP 192.168.10.10:138 *:*
UDP 192.168.10.10:1900 *:*
UDP 192.168.10.10:49178 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::1]:1900 *:*
UDP [::1]:49176 *:*
UDP [fe80::100:7f:fffe%8]:1900 *:*
UDP [fe80::100:7f:fffe%8]:49177 *:*

Hope this helps

Vera Noest [MVP] wrote:
> Weird!
> There are known problems with Vista clients in an SBS2003 domain, I
> don't know the details, but the sbs newsgroup has numerous posts
> about it.
> But I've never seen a report like yours with Vista and Windows
> Server 2003, and I don't understand what's going on.
> Could you post the output of a "netstat -an" command, to check what
> is listening on port 3389?
 
Thought i had better post my friends results too: We changed his port
to 3391

Netstat when not connected

Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2804 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3391 0.0.0.0:0 LISTENING
TCP 0.0.0.0:10541 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49161 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49184 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2804 127.0.0.1:49182 ESTABLISHED
TCP 127.0.0.1:49182 127.0.0.1:2804 ESTABLISHED
TCP 192.168.16.16:139 0.0.0.0:0 LISTENING
TCP 192.168.16.16:49164 192.168.16.2:1745 ESTABLISHED
TCP 192.168.16.16:49180 192.168.16.2:1745 ESTABLISHED
TCP 192.168.16.16:49720 192.168.16.2:8080 CLOSE_WAIT
TCP 192.168.16.16:49724 192.168.16.2:1745 ESTABLISHED
TCP 192.168.16.16:49725 192.168.16.2:53030 ESTABLISHED
TCP 192.168.16.16:49740 192.168.16.2:53100 ESTABLISHED
TCP 192.168.16.16:49763 192.168.16.2:445 ESTABLISHED
TCP 192.168.16.16:49795 192.168.16.2:8080 TIME_WAIT
TCP 192.168.16.16:49798 192.168.16.2:8080 TIME_WAIT
TCP 192.168.16.16:49800 192.168.16.2:8080 TIME_WAIT
TCP 192.168.16.16:49801 192.168.16.2:8080 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:3391 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49158 [::]:0 LISTENING
TCP [::]:49161 [::]:0 LISTENING
TCP [::]:49184 [::]:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:10541 *:*
UDP 0.0.0.0:49184 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49152 *:*
UDP 127.0.0.1:49155 *:*
UDP 127.0.0.1:49159 *:*
UDP 127.0.0.1:49165 *:*
UDP 127.0.0.1:49166 *:*
UDP 127.0.0.1:49170 *:*
UDP 127.0.0.1:49176 *:*
UDP 127.0.0.1:49177 *:*
UDP 127.0.0.1:49180 *:*
UDP 127.0.0.1:49186 *:*
UDP 127.0.0.1:49187 *:*
UDP 127.0.0.1:49188 *:*
UDP 127.0.0.1:49196 *:*
UDP 127.0.0.1:49197 *:*
UDP 127.0.0.1:49199 *:*
UDP 127.0.0.1:49200 *:*
UDP 127.0.0.1:49216 *:*
UDP 127.0.0.1:49232 *:*
UDP 127.0.0.1:49277 *:*
UDP 192.168.16.16:137 *:*
UDP 192.168.16.16:138 *:*
UDP 192.168.16.16:1900 *:*
UDP 192.168.16.16:49175 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:5355 *:*
UDP [::]:49185 *:*
UDP [::1]:1900 *:*
UDP [::1]:49173 *:*
UDP [fe80::100:7f:fffe%10]:1900 *:*
UDP [fe80::100:7f:fffe%10]:49174 *:*
UDP [fe80::6cd3:4366:b5c8:a591%8]:1900 *:*
UDP [fe80::6cd3:4366:b5c8:a591%8]:49172 *:*

When conected to SBS2003 via Remote desktop

z:\netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2804 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3391 0.0.0.0:0 LISTENING
TCP 0.0.0.0:10541 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49158 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49161 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49184 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2804 127.0.0.1:49182 ESTABLISHED
TCP 127.0.0.1:49182 127.0.0.1:2804 ESTABLISHED
TCP 192.168.16.16:139 0.0.0.0:0 LISTENING
TCP 192.168.16.16:49164 192.168.16.2:1745 ESTABLISHED
TCP 192.168.16.16:49180 192.168.16.2:1745 ESTABLISHED
TCP 192.168.16.16:49720 192.168.16.2:8080 CLOSE_WAIT
TCP 192.168.16.16:49724 192.168.16.2:1745 ESTABLISHED
TCP 192.168.16.16:49725 192.168.16.2:53030 ESTABLISHED
TCP 192.168.16.16:49740 192.168.16.2:53100 ESTABLISHED
TCP 192.168.16.16:49763 192.168.16.2:445 ESTABLISHED
TCP 192.168.16.16:49802 192.168.16.2:1745 ESTABLISHED
TCP 192.168.16.16:49804 192.168.16.2:3389 ESTABLISHED
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:3391 [::]:0 LISTENING
TCP [::]:5357 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:49158 [::]:0 LISTENING
TCP [::]:49161 [::]:0 LISTENING
TCP [::]:49184 [::]:0 LISTENING
UDP 0.0.0.0:123 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:3702 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:10541 *:*
UDP 0.0.0.0:49184 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:49152 *:*
UDP 127.0.0.1:49155 *:*
UDP 127.0.0.1:49159 *:*
UDP 127.0.0.1:49165 *:*
UDP 127.0.0.1:49166 *:*
UDP 127.0.0.1:49170 *:*
UDP 127.0.0.1:49176 *:*
UDP 127.0.0.1:49177 *:*
UDP 127.0.0.1:49180 *:*
UDP 127.0.0.1:49186 *:*
UDP 127.0.0.1:49187 *:*
UDP 127.0.0.1:49188 *:*
UDP 127.0.0.1:49196 *:*
UDP 127.0.0.1:49197 *:*
UDP 127.0.0.1:49199 *:*
UDP 127.0.0.1:49200 *:*
UDP 127.0.0.1:49216 *:*
UDP 127.0.0.1:49232 *:*
UDP 127.0.0.1:49277 *:*
UDP 127.0.0.1:49501 *:*
UDP 192.168.16.16:137 *:*
UDP 192.168.16.16:138 *:*
UDP 192.168.16.16:1900 *:*
UDP 192.168.16.16:49175 *:*
UDP [::]:123 *:*
UDP [::]:500 *:*
UDP [::]:3702 *:*
UDP [::]:3702 *:*
UDP [::]:5355 *:*
UDP [::]:49185 *:*
UDP [::1]:1900 *:*
UDP [::1]:49173 *:*
UDP [fe80::100:7f:fffe%10]:1900 *:*
UDP [fe80::100:7f:fffe%10]:49174 *:*
UDP [fe80::6cd3:4366:b5c8:a591%8]:1900 *:*
UDP [fe80::6cd3:4366:b5c8:a591%8]:49172 *:*


Vera Noest [MVP] wrote:
> Weird!
> There are known problems with Vista clients in an SBS2003 domain, I
> don't know the details, but the sbs newsgroup has numerous posts
> about it.
> But I've never seen a report like yours with Vista and Windows
> Server 2003, and I don't understand what's going on.
> Could you post the output of a "netstat -an" command, to check what
> is listening on port 3389?
 
Back
Top