RDC working-one session per boot

  • Thread starter Thread starter MDBJ
  • Start date Start date
M

MDBJ

I'm having an annoying problem,
my RDC connection works once, then it won't work again until I reboot (or
call and beg the wife to) the serving machine..

anyone haven any idea where to begin?

it appears from the welcome screen of my server the machine considers the
account still logged on if I close the connection (the yellow bar's x) or if
I log off from the start button on the serving machine.-- it's obviously not
logging off my session (and I'll bet therefore it's an issue with the
disconnect)
 
On Wed, 30 Mar 2005 20:14:29 -0500, MDBJ wrote:
I don't have a solution but I do have the same problem. Maybe we can
compare notes.
I just recently started using RDC after upgrading Windows XP Pro to SP2 and
Norton Antivirus 2005 on both the host and client.Since I have no
experience with RDC prior to this, I do not know if the problem is related
to the upgrades. In my RDC tests I have been using admin accounts for both
the client and host.
My research suggests that the fact that the account is still logged on
after the connection is ended may not be indicative of a problem. I think
there are security policies that can be set to manage what happens when the
connection ends, including loging off the account after x minutes.
What is significant I think is that, as you indicated, manually logging off
the host account does not clear the condition. In fact, I have tried using
a second different client and host admin account to establish an RDC
session after disconnecting the first and experience the same failure. So I
think the fact that the host account is still logged on after the
disconnect, is not the crux of the problem.
My supicion is that the port used for RDC (I think its something like
3389?) is in an abnormal state after the disconnect. Maybe it remains
allocated to the session (port can only serve one session at a time?) or is
no longer listening. I will try some tests to confirm that.
You have not mentioned another symptom that may be related to this problem
and is identified in another post ("Remote not working while not logged
in"). In my case and the other poster, an RDC session cannot be established
with a host account unless the host account is already manually logged on.

To compare notes, can you post the host and client Windows version and
level you are using and if you are using Admin accounts or if your accounts
belong to an RDC group. Which firewalls (if any) are you using? Are you
using Norton Antivirus? NAV web worm protection? All of these filter
certain network traffic which might prevent a proper disconnect.
 
connection ends, including loging off the account after x minutes.
What is significant I think is that, as you indicated, manually logging
off
the host account does not clear the condition. In fact, I have tried using
a second different client and host admin account to establish an RDC
session after disconnecting the first and experience the same failure. So
I
think the fact that the host account is still logged on after the
disconnect, is not the crux of the problem.
My supicion is that the port used for RDC (I think its something like
3389?) is in an abnormal state after the disconnect. Maybe it remains
Indeed, in testing, instead of a reboot, an
IPCONFIG /release /renew clears it for the next connection

i.e- today I discovered a release & renew renables the next session
of RDC from my serving machine-without having to reboot.
allocated to the session (port can only serve one session at a time?) or
is
no longer listening. I will try some tests to confirm that.
netstat reports it as just listening before and after my one session.
You have not mentioned another symptom that may be related to this problem
and is identified in another post ("Remote not working while not logged
in"). In my case and the other poster, an RDC session cannot be
established
with a host account unless the host account is already manually logged on.

To compare notes, can you post the host and client Windows version and
XPprosp2 both- both are from xp2 upgrade cd's, however, the one that is
serving up
my failing connection was done as a clean installation
level you are using and if you are using Admin accounts or if your
accounts
belong to an RDC group. Which firewalls (if any) are you using?

Admin accounts both ways
firewalls OFF at both ends at the momment, both machines behind routers,
only opening appropriate ports for need
(however, it happens if I do it url/url over the open web, or over the VPN
which is set up from
my pc at work-passed through the work router- router at home accepting the
VPN- not the serving xp machine)

Are you using Norton Antivirus? NAV web worm protection?
nope.- not on the serving machine.
All of these filter
certain network traffic which might prevent a proper disconnect.

not on either machine under discussion, but on a different machine, I set a
5min arp cache flush via yhe instructions at
http://www.sixdifferentways.com/archives/007675.html

the part as
SCHTASKS /CREATE /SC MINUTE /MO 5 /TN ARPFLUSH /TR
C:\WINNT\system32\netsh\interface\ip\delete\arpcache

for a workarounf
I'm wondering if a similar process for ipconfig renew might not be set for
at the end of a RDC setting
or, creating a bat file that contains ipconfig/renew and calling that bat
file from the
"program to run at the end of an RDC session" option in the client mstsc.
 
indeed
I made a bat file
ipconfig/release
ipconfig/renew
and saved it to desktop

when I finished with my session, I clicked it on the server
I "lost" rdc my connection- but the next connection was available
 
Back
Top