Windows NT Cannot connect to Windows XP Client remote desktop

  • Thread starter Thread starter Marcus
  • Start date Start date
M

Marcus

Dear Newsgroup

I cannot establish a remote desktop connection on my Windows XP Pro base
unit (10.0.1.241) from my Windows XP laptop (10.0.1.242). Connection is an
internal one only on 10.0.1.x subnet via router.

Windows Firewall has been switched off, checked that port 3389 is listening
with netstat -a, RD is swithced on, check that relevant services are
running, even moved the RDP port from 3389 to 4489.

Ran wireshark to monitor network activity and have noticed lots of TCP
checksum error, first 4 packets are good, then errors as below

Source Destination Proto Info
10.0.1.242 10.0.1.241 TCP warmspotMgmt > 4489 [SYN] Seq=0
Win=16384 Len=0 MSS=1460
10.0.1.241 10.0.1.242 TCP 4489 > warmspotMgmt [SYN, ACK[
Seq=0 Ack=1 Win=65535 Len = 0 MSS=1460
10.0.1.242 10.0.1.241 TCP warmspotMgmt > 4489 [ACK] Seq=1
Ack=1 Win=17520 Len =0
10.0.1.242 10.0.1.241 TCP warmspotMgmt > 4489 [PSH, ACK]
Seq=1 Ack=1 Win=17520, Len = 19
10.0.1.241 10.0.1.242 TCP 4489 > warmspotMgmt [PSH, ACK]
Seq=1 Ack=20, Win=65516 [TCP CHECKSUM INCORRECT]
10.0.1.242 10.0.1.241 TCP warmsportMgmt > 4489 [PSH,ACK]
Seq=20 Ack=12 Win=17509 Len=428
10.0.1.241 10.0.1.242 TCP 4489 > warmsportMgmt [PSH, ACK]
Seq=12 Ack=448 Win=65088 [TCP CHECKSUM INCORRECT]

Funny thing when a remove XP SP3 RD worked, but other problems occured which
did not relate to RD. So I reinstalled SP3 and once again cannot establish
connection.


Would be truely grateful from help, lost on this one myself.

Many thanks in advance!
 
Have you tried disabling, hit apply/ok, then reenabling remote desktop? Can
you telnet to 3389?

Jeff Pitsch
Microsoft MVP - Terminal Services


"Marcus" <marcusuk@ntlworld.com> wrote in message
news:FEHlk.118089$Lc6.8276@newsfe18.ams2...
> Dear Newsgroup
>
> I cannot establish a remote desktop connection on my Windows XP Pro base
> unit (10.0.1.241) from my Windows XP laptop (10.0.1.242). Connection is an
> internal one only on 10.0.1.x subnet via router.
>
> Windows Firewall has been switched off, checked that port 3389 is
> listening with netstat -a, RD is swithced on, check that relevant services
> are running, even moved the RDP port from 3389 to 4489.
>
> Ran wireshark to monitor network activity and have noticed lots of TCP
> checksum error, first 4 packets are good, then errors as below
>
> Source Destination Proto Info
> 10.0.1.242 10.0.1.241 TCP warmspotMgmt > 4489 [SYN] Seq=0
> Win=16384 Len=0 MSS=1460
> 10.0.1.241 10.0.1.242 TCP 4489 > warmspotMgmt [SYN,
> ACK[ Seq=0 Ack=1 Win=65535 Len = 0 MSS=1460
> 10.0.1.242 10.0.1.241 TCP warmspotMgmt > 4489 [ACK] Seq=1
> Ack=1 Win=17520 Len =0
> 10.0.1.242 10.0.1.241 TCP warmspotMgmt > 4489 [PSH, ACK]
> Seq=1 Ack=1 Win=17520, Len = 19
> 10.0.1.241 10.0.1.242 TCP 4489 > warmspotMgmt [PSH, ACK]
> Seq=1 Ack=20, Win=65516 [TCP CHECKSUM INCORRECT]
> 10.0.1.242 10.0.1.241 TCP warmsportMgmt > 4489 [PSH,ACK]
> Seq=20 Ack=12 Win=17509 Len=428
> 10.0.1.241 10.0.1.242 TCP 4489 > warmsportMgmt [PSH, ACK]
> Seq=12 Ack=448 Win=65088 [TCP CHECKSUM INCORRECT]
>
> Funny thing when a remove XP SP3 RD worked, but other problems occured
> which did not relate to RD. So I reinstalled SP3 and once again cannot
> establish connection.
>
>
> Would be truely grateful from help, lost on this one myself.
>
> Many thanks in advance!
>
 
Jeff

Thank you for your time, I am grateful.

I have disabled and re-enabled the remote desktop as you suggested but still
no better.

Tried "telnet localhost 4489", soon as I press a key connection drops back
to command prompt.

Interesting if I carry out same procedure on laptop "telnet localhost 3389"
the connection is still there when I press a key or sequence of keys.

Even when I move RDP back to 3389 on desktop connectio still drops back to
command prompt.

Could this be something to do with security certificates / encryption?
 
There are security settings that can be set and forced. Is your laptop part
of a domain? A level of required security may be set on either side that
isn't compatible on the other.

Jeff Pitsch
Microsoft MVP - Terminal Services

"Marcus" <marcusuk@ntlworld.com> wrote in message
news:Q7Ilk.118665$Lc6.60153@newsfe18.ams2...
> Jeff
>
> Thank you for your time, I am grateful.
>
> I have disabled and re-enabled the remote desktop as you suggested but
> still no better.
>
> Tried "telnet localhost 4489", soon as I press a key connection drops
> back to command prompt.
>
> Interesting if I carry out same procedure on laptop "telnet localhost
> 3389" the connection is still there when I press a key or sequence of
> keys.
>
> Even when I move RDP back to 3389 on desktop connectio still drops back to
> command prompt.
>
> Could this be something to do with security certificates / encryption?
>
>
>
 
Jeff

Neither the laptop or the desktop is part of domain. The network just
consists of a cable modem router and two PC's.

Once again I am grateful for your time.

Regards Marcus
 
On Aug 4, 2:22 pm, "Marcus" <marcu...@ntlworld.com> wrote:
> Jeff
>
> Neither the laptop or the desktop is part of domain. The network just
> consists of a cable modem router and two PC's.
>
> Once again I am grateful for your time.
>
> Regards Marcus

Marcus:

Did you ever get a solution to this, I am experiencing the same
issues.

Would appreciate if you have an answer.

Colin
 

Similar threads

J
xhost+ (wireshark saw network packets exchange), but fail display
Replies
0
Views
522
javanoob
J
Back
Top