• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Best way to setup remote desktop?

Status
Not open for further replies.

EQTitan

Diamond Member
Ok, this is what I'd like to be a able to do. Currently the company I work for wants to be able to run two systems as a remote desktop that 1-8 technicians have access to. These two systems have a piece of software that each tech. needs to be able to use and access from there remote machines.

Basically 2 Main systems both running the same software needed to be accessed by two different locations in the company structure (North and South). We have 8 technicians connecting to the north machine, and only 2-3 technicians connecting to the south machine. I thought it would be a good idea instead of going to these machines everyday that we could login to them via an internet connection anytime of day 24/7. So, would using WinXP Pro built in remote desktop be a viable option?

Please reply if your confused or can help us out....

Thanks

 
Remote desktop is very easy to set up. I just set it up myself and you don't need an Internet Connection.

1) On the computers you need to access, right-click My Computer and select Properties. Then click the Remote tab and tick the box that says 'Allow users to connect remotely to this computer. These computers MUST be running Windows XP Pro and must be turned on in order to be connected to.

2) Now, when you need to access these computers go to Start > All Programs > Accessories > Communications > Remote Desktop Connection.

3) A box will pop up, just type in the ip address or computer name of the computers you need to access and click Connect. Before you cannot you can click 'Options' which have more advanced options. Once you have connected you need to type in the username and password of the computer your trying to access (not the computer you are on). If there is no password leave it blank. That's it!

Hope I'v helped.
 
Yes, but that will only work for 2 consecutive logons. Cant do more than that on XP Pro -- you'd have to run a version of Windows Server for that. And to correct antsct, the computers connecting to the XP machine do not have to be running XP, they can be running 2K, or even OS X!
 
Originally posted by: Doug117
Yes, but that will only work for 2 consecutive logons. Cant do more than that on XP Pro -- you'd have to run a version of Windows Server for that. And to correct antsct, the computers connecting to the XP machine do not have to be running XP, they can be running 2K, or even OS X!

consecutive?? you can't have concurrent logins with windows xp.
 
Originally posted by: Doug117
Yes, but that will only work for 2 consecutive logons. Cant do more than that on XP Pro -- you'd have to run a version of Windows Server for that. And to correct antsct, the computers connecting to the XP machine do not have to be running XP, they can be running 2K, or even OS X!

No need to correct me 😉 I never said the computers connection to the host need Windows XP
 
XP allows ONE login, if you are on the console, and someone remotes in, it locks the screen and boots you off. No 2 session, only one. With terminal server in Admin mode (2k Server, 2k3 server) you can have ONE console session + 2 REMOTE sessions, for a total of 3 max. There is no way to change that setting.
 
Originally posted by: nweaver
XP allows ONE login, if you are on the console, and someone remotes in, it locks the screen and boots you off. No 2 session, only one. With terminal server in Admin mode (2k Server, 2k3 server) you can have ONE console session + 2 REMOTE sessions, for a total of 3 max. There is no way to change that setting.
Confirm 2 with W2K3, but I thought W2K allowed more than that (we were discussing with MS how to get past 2 connections without installing Terminal Server).

BTW, Terminal Server might be the answer. I have no experience setting it up. Or Citrix?

 
I think you might be mistaking terminal services Admin mode versus terminal services Application mode. Admin mode allow 2 (might be 3) cuncurrent remote sessions to the box. Application mode allows multiplle connections to access a piece of software? (I havn't ever used it in app mode). Both are "Terminal Server"
 
um, competing for the session....

VNC is a great tool, and has it's place, but it's not here. You can have multiple users connect to the VNC server, but they can't all do different things at once.
 
Confirm 2 with W2K3

2003 actually can do 3. Two administrative (like 2000), and the console. The console can be accessed through remote desktop, so that makes three remoteable connections without full fledged TS and TS licensing.
 
I just need to be able to setup one account as such

Login : Tech
Password : password

And all 2-3 tech in the south would share this login for the one main machine we'd all need to connect to via the internet.

Secondly, the main machine in our south location has a dynamic IP should this pose a problem?
 
Originally posted by: STaSh
Confirm 2 with W2K3

2003 actually can do 3. Two administrative (like 2000), and the console. The console can be accessed through remote desktop, so that makes three remoteable connections without full fledged TS and TS licensing.

Yep.

mstsc /console
 
Originally posted by: EQTitan
I just need to be able to setup one account as such

Login : Tech
Password : password

And all 2-3 tech in the south would share this login for the one main machine we'd all need to connect to via the internet.

Secondly, the main machine in our south location has a dynamic IP should this pose a problem?

Give them each a logon. Best idea.

Dynamic IP isn't an issue as long as you know what it is. You talking DHCP dynamic IP? Just connect it to a dynamic capable DNS server and you can stick with an unchanging name.


 
If you have 2000 Server, remember that TS CAL comes with each copy of XP. So you in essence don't have to "activate" the server with the MS Clearinghouse.

2003, OTOH doesn't allow this.
 
Originally posted by: Doug117
Yes, but that will only work for 2 consecutive logons. Cant do more than that on XP Pro -- you'd have to run a version of Windows Server for that. And to correct antsct, the computers connecting to the XP machine do not have to be running XP, they can be running 2K, or even OS X!

There is a hack that does allow more two or more concurrent remote desktop connections for XP, but the computers can't be a domain member.
 
Originally posted by: rdubbz420
Originally posted by: Doug117
Yes, but that will only work for 2 consecutive logons. Cant do more than that on XP Pro -- you'd have to run a version of Windows Server for that. And to correct antsct, the computers connecting to the XP machine do not have to be running XP, they can be running 2K, or even OS X!

There is a hack that does allow more two or more concurrent remote desktop connections for XP, but the computers can't be a domain member.

Didn't know there was a hack. Bummer that it can't be on a domain though. It would be a huge benefit if we could just have ONE concurrent connection in the background without locking the console.
 
Originally posted by: EQTitan
I just need to be able to setup one account as such

Login : Tech
Password : password

And all 2-3 tech in the south would share this login for the one main machine we'd all need to connect to via the internet.

Secondly, the main machine in our south location has a dynamic IP should this pose a problem?

Mweaver has made some good, and accurate points. If they can share the console session, then a VNC server would work (I still prefer the basic version of RealVNC). If you want them to be able to log on concurrently, and each run the program seperately, then you will have to use Windows Server (2k or 2k3) and if you want more than 2 to log in (in the background) you will have to purchase the Terminal Services licensing (or some people prefer Citrix).
 
No, everyone will have a set time they can log in and use the software. I need to use something simple to have these techs connect to the main machines, they are not all that computer savy.
 
Originally posted by: EQTitan
No, everyone will have a set time they can log in and use the software. I need to use something simple to have these techs connect to the main machines, they are not all that computer savy.

Well, in that case, using remote desktop on Windows XP should work fine. Just enable it in the My Computer properties, and then enable the exception in the Windows firewall. You may have to add the user account to allow remote desktop in the My Computer properties.
 
Status
Not open for further replies.
Back
Top