remote desktop issue for xp
hi
one of my users has an issue with remote desktop on windows xp, he logs onto our term serve and it goes in fine but after about 30 seconds it just closes, i have tried with my term serve account and it does the same thing, i have tried to remote to another server, from his laptop and it does the same thing. and if he uses another laptop it works fine.

got any suggestions where to start looking on this one, i have checked and change stuff the looks like it might have something to do with this, and even some settings that have nothing to do with it, but still no luck.
ok, none of the suggestions above helped, but i removed the saved shortcuts and ran mstsc /admin and recreated the shortcut and that seemed to work fine.
Dear Jay Nelish


Your Question is incomplete


is the specific system is not on Network? its might be a problem discovered last year, that system ping but not share any data, or cannot access the system


you click on start menu and then click on run  

type serivces.msc  

and run the computer browser service, Remote Procedure call service, Server, and Client service


and your problem will resolved  

but actually this is because of virus change your antivirus program and scan your system wtih updated A/V first try testing your RAM (goldmemory or memtest)
  

  
if the memory pass the tests try reparing your xp, if repair doesn't pass from any reason, pull your HD take it to your friend, back up the data, and reinstall OS We currently have all our machines still on Windows XP and have only just upgraded some with Office 2007.


Budget dollars just have been too cost prohibitive to upgrade all 1,000 of our workstations. At some point due to licensing and availability we will be forced to upgrade. 


The one thing I’ve noticed difficulty with right off the bat has been the ability to connect via RDP to a Windows Server 2008 box. Without some registry hacks/mods in XP this can be problematic if the server is set to the newest (and more secure) RDP protocol. Windows 7 doesn’t have this issue. The question is can you get out of your computer and after that the thing to check is can you resolve any domain names. Try going to a command prompt and checking to see if you can ping your computers IP address then the gateway then try to resolve domain names.


ipconfig /all


Will give you the information you need to check these things.


nslookup google.com


If that does not come back with a IP address then you have problems with your DNS server. i assume your new router is wireless?

limited access with wireless usually means you don't have a valid ip address assigned. you need two things for a working internet connection. 1. you need a physical connection, known as layer 1 and layer 2. 2. you need a logical connection known as layer 3.

if you've got the limited access message that means your laptop has a working wireless connection at layers 1 and 2. what you don't have is the layer 3 connection i.e. an ip address.

there could be a number of reasons why this is happening. i would suggest that you start by powering your pc down - shut it off completely not just hibernate it or just shut the lid. next power down the router, pull the power cord out of it. let the router sit unplugged for about 2 minutes. power the router back up......wait about 2 min more. power your pc back up.

learn how to use the command line command "ipconfig". you access the command line via the accessories folder on windows. when you get the c:/> prompt - enter the command "ipconfig" hit enter. in the group of stuff on the screen you want to see an ip addess assigned to the wireless interface. when you get the limited access message the first thing you want to do is check to see if you have an ip address assigned.

if the above trick doesn't work, then i suspect there is something wrong with your network configuration on your pc. if you take your laptop to a starbucks does it work there? try a quick flight on any server and make sure to tap “end flight”. that should restore it :) sorry i took so long to respond on this post. i’ve had a busy week! so i found the issue. in my template for endpoints i realized i accidentally set them to provision using the external ip address of my pbx. changed it to internal and this fixed my issues :stuck\_out\_tongue: the problem has been solved.

i got in contact with our provider and they were able to apply the proper access to the folder for verification.

thank you for all of your help and patience. this thread can now be closed. it looks like your intent is to use host networking, can you add

network\_mode: host

also you can try netstat -tupln | grep 32400

to see if you are listening on 32400 for plex you can try a factory reset. push and hold the reset button for 15 seconds and then release. the button should be located on the back of your gateway/modem/router, and you will need a ballpoint pen or toothpick. you should then be able to access your gateway using the standard means with the passwords listed on the label on the gateway.  \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_how can you be in two places at once, when your not anywhere at all?i really want to become a procrastinator, but i keep putting it off.there are three kinds of people, those that can count, and those that can't.'our great democracies still tend to think that a stupid man is more likely to be honest than a clever man, and our politicians take advantage of this prejudice by pretending to be even more stupid than nature has made them.' :bertrand russell