Conection problem

[cachulo]

Hi

I´ve a W3K R2 with terminal server enabled, configured, and until a few
days ago everything worked fine.
Problaby after a windowsupdate , the XP clients became unable to conect via
remote desktop to the server, in the XP clients i can ping, browse the
network, access de shared folders in the server, only remote conection isn´t
working.

I´ve tried everithing, no good, finally i decided to use our external ip,
and it worker fine.

The situation is this i can connect to the server with remote desktop if i
use my external ip ( internet ) even in the machines in the local area
network, but if instead i use de internal ip 192.168.16.2 i can´t connect.

All help would be aprecciated, thanks in advance

 

[Vera Noest [MVP]]

Re: Conection problem

What's the error message that you get?
Anything in the EventLog on the server?
What's the settings in rdp-tcp connection properties , under the
network tab?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Y2FjaHVsbw==?= <cachulo@discussions.microsoft.com> wrote
on 07 nov 2007 in microsoft.public.windows.terminal_services:

> Hi
>
> I´ve a W3K R2 with terminal server enabled, configured, and
> until a few days ago everything worked fine.
> Problaby after a windowsupdate , the XP clients became unable to
> conect via remote desktop to the server, in the XP clients i can
> ping, browse the network, access de shared folders in the
> server, only remote conection isn´t working.
>
> I´ve tried everithing, no good, finally i decided to use our
> external ip, and it worker fine.
>
> The situation is this i can connect to the server with remote
> desktop if i use my external ip ( internet ) even in the
> machines in the local area network, but if instead i use de
> internal ip 192.168.16.2 i can´t connect.
>
> All help would be aprecciated, thanks in advance

 

[cachulo]

Re: Conection problem

Hi

I get this message " Este computador não consegue estabelecer uma ligação" ,
in english something like this " This computer can´t estabilish a connection"

There is nothing in the event log
the setting in the RDP connections are TCP / Microsoft RDP 5.2

I think that is well configured because clients can connect to TS with the
external IP, the only problem i´m getting is when i put the internal ip of
the server or the name.

This was working for over 2 years, it sudnlly happened !!!

thanks in advance



"Vera Noest [MVP]" wrote:

> What's the error message that you get?
> Anything in the EventLog on the server?
> What's the settings in rdp-tcp connection properties , under the
> network tab?
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?Y2FjaHVsbw==?= <cachulo@discussions.microsoft.com> wrote
> on 07 nov 2007 in microsoft.public.windows.terminal_services:
>
> > Hi
> >
> > I´ve a W3K R2 with terminal server enabled, configured, and
> > until a few days ago everything worked fine.
> > Problaby after a windowsupdate , the XP clients became unable to
> > conect via remote desktop to the server, in the XP clients i can
> > ping, browse the network, access de shared folders in the
> > server, only remote conection isn´t working.
> >
> > I´ve tried everithing, no good, finally i decided to use our
> > external ip, and it worker fine.
> >
> > The situation is this i can connect to the server with remote
> > desktop if i use my external ip ( internet ) even in the
> > machines in the local area network, but if instead i use de
> > internal ip 192.168.16.2 i can´t connect.
> >
> > All help would be aprecciated, thanks in advance
>

 

[Vera Noest [MVP]]

Re: Conection problem

I meant: the settings in rdp-tcp connection - properties - network
adapter.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?Y2FjaHVsbw==?= <cachulo@discussions.microsoft.com> wrote
on 08 nov 2007:

> Hi
>
> I get this message " Este computador não consegue estabelecer
> uma ligação" , in english something like this " This computer
> can´t estabilish a connection"
>
> There is nothing in the event log
> the setting in the RDP connections are TCP / Microsoft RDP
> 5.2
>
> I think that is well configured because clients can connect to
> TS with the external IP, the only problem i´m getting is when i
> put the internal ip of the server or the name.
>
> This was working for over 2 years, it sudnlly happened !!!
>
> thanks in advance
>
>
>
> "Vera Noest [MVP]" wrote:
>
>> What's the error message that you get?
>> Anything in the EventLog on the server?
>> What's the settings in rdp-tcp connection properties , under
>> the network tab?
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?Y2FjaHVsbw==?= <cachulo@discussions.microsoft.com>
>> wrote on 07 nov 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Hi
>> >
>> > I´ve a W3K R2 with terminal server enabled, configured,
>> > and until a few days ago everything worked fine.
>> > Problaby after a windowsupdate , the XP clients became unable
>> > to conect via remote desktop to the server, in the XP clients
>> > i can ping, browse the network, access de shared folders in
>> > the server, only remote conection isn´t working.
>> >
>> > I´ve tried everithing, no good, finally i decided to use
>> > our external ip, and it worker fine.
>> >
>> > The situation is this i can connect to the server with remote
>> > desktop if i use my external ip ( internet ) even in the
>> > machines in the local area network, but if instead i use de
>> > internal ip 192.168.16.2 i can´t connect.
>> >
>> > All help would be aprecciated, thanks in advance