Unable to start TS session with a remote server

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I just got a new laptop at work, but before swapping out my old PC, I copied
my profile to the new laptop. Among the desktop items copied was a mstsc.exe
shortcut which worked fine on the old PC. The icon on the laptop desktop
looks slightly different (slicker) than the original. When I click o the
options radio button, there are 6 tabs instead of 5 (the extra tab is titled
"Advanced"). Also in the logon settings there is no username and underneath
there is a line that says "You will be asked for credentials when you
connect." I tried copying the RDP file from the old icon to the new icon, but
it didn't help. I was able to connect to another remote server but not that
one... Any ideas?
 
kp400 said:
I just got a new laptop at work, but before swapping out my old PC, I
copied my profile to the new laptop. Among the desktop items copied
was a mstsc.exe shortcut which worked fine on the old PC. The icon on
the laptop desktop looks slightly different (slicker) than the
original. When I click o the options radio button, there are 6 tabs
instead of 5 (the extra tab is titled "Advanced"). Also in the logon
settings there is no username and underneath there is a line that
says "You will be asked for credentials when you connect." I tried
copying the RDP file from the old icon to the new icon, but it didn't
help. I was able to connect to another remote server but not that
one... Any ideas?

I'm confused about your mentioning mstsc.exe in the context of a shortcut,
as the shortcut to any RD session is an .rdp file you create. The new PC is
evidently running the newest version of the RD client - you may need to
recreate your shortcut by running the RD client and filling in the relevant
bits.
 
At a minimum it should have failed to "autoconnect" and prompt you for
credentials ..


"Lanwench [MVP - Exchange]"
 
Just discovered that I'm unable to ping that server; I can ping other servers
without any problem. I know the server is up & running, because other
coworkers who are still using their old PCs can ping the server & connect
with TS. I would think if the problem was with the *.rdp file I wouldn't be
able to connect to any other server...
This is truly weird.
 
It's 2 days later and I've re-imaged the laptop 3 times and I'm still unable
to launch a TS session or ping 1 particular server in the domain ( I can
attach to & ping all the other servers (including the loopback address, DHCP
& DNS servers). And this server is on the same subnet as my laptop. The
following error code has come up at least once a day in the System Event
Viewer log:

"The browser service has failed to retrieve the backup list too many times
on transport \Device\NetBT_Tcpip_{07535886-0A0B-4C6E-A911-D1B73F2C35DA}. The
backup browser is stopping."

Any ideas?

regards
 
Back
Top