Remote desktop unexpected behaviour in Windows 2003

[Rosivaldo Fernandes Alves]

I'm relatively familiar with Remote Desktop with Windows XP, but in Windows
2003 it behaves somewhat different. If I log on remotely, close the
connection, keep the session alive and log on locally, I get another
session, not the session I had kept open. The same occurs if I log on
locally first, lock the console and log again remotely. How can I get the
same session I was working with? Some times, I need to interact with an
application open in a specific session.

Another matter is that I've just reinstalled the Windows 2003 Server and
changed its computer name, but Remote Desktop always says that the remote
computer can't be found. I can only connect if I use the computer name the
Windows 2003 had before the reinstallation!

Could someone help me, please?

Rosivaldo.

 

[Chris Priede]

get another session, not the session I had kept open. The same occurs
if I log on locally first, lock the console and log again remotely.
How can I get the same session I was working with?

You can connect to the console session remotely by running mstsc.exe with
/console switch, as described here:

http://www.microsoft.com/resources/...2003/standard/proddocs/en-us/ts_cmd_mstsc.asp

The command line switch works with mstsc.exe included with Windows XP, as
long as the remote is running 2003 Server.

However, if you do this often and from the same computer(s), I would suggest
installing the 2003 Server admin tools pack and using the MMC "Remote
Desktops" snap-in, which provides a GUI checkbox for this option:

http://support.microsoft.com/kb/309375

 

[Rosivaldo Fernandes Alves]

Thanks, Chris. I'll try your suggestion. What about the confusion of names.
Any hint?

Rosivaldo.

 

[Chris Priede]

Thanks, Chris. I'll try your suggestion. What about the confusion of
names. Any hint?

It is hard to even come up with a reasonably short checklist without knowing
more about your network, because Windows can resolve names in a number of
ways. Here are some ideas:

1)If you are using local DNS with dynamic updates, make sure "Register this
connection's addresses in DNS" is checked in your advanced TCP/IP
configuration, the machine is using the right DNS servers, and run "ipconfig
/registerdns".

2)If you are using hosts files (as might be the case on a very small
network), update them on all the other machines.

3)If you are not using either, then your name resolution was probably
working through NetBIOS and you might want to make sure that NetBIOS over
TCP/IP is enabled (also under advanced TCP/IP configuration).

 

[Rosivaldo Fernandes Alves]

I came to work today and the name confusion simply has vanished. I don't
know what has happened, but I will worry if the problem returns. Until then,
perhaps I have learned a bit more about name resolution in an MS network on
TCP/IP. Thank you very much anyway, and forgive my inexperience.

Rosivaldo.