Remote Access to RSLogix

[AGENTTINFOIL]

Originally Posted by Bob O

I am happy that it works for you but it doesn't for me and RA confirmed it.

Edit..Maybe one of RA gurus will let us know why it works in your case and not mine.

Not really sure why it works for me and not you... I would like to know why it does not work for you? Hopefully some one could elaborate more on this issue for us. I am not really sure why RA would confirm something like that anyway. When you remote into any PC that gives you full control over the box and all applications. I do not see why RSLogix would be any different especially if you have the activation installed on that PC. Is your activation installed on your PC? My comment was not intended to be an argument, just simply to state I do this all the time as well as our engineering dept. I can not really think what is different from yours and mine, remote desktop works the same on any box with XP Professional.

Taking you through the steps that I go through to connect from my home.

1. Setup a VPN connection to my work network.already have IP
2. Connect to the network
3. Open Remote Desktop
4. Type in IP for my box and connect. already have IP
5. Once online with my box open the RSLogix software from
the short cut on my desktop.
6. Comms,whos active go online,select PLC and I am online from
Home.

This is how I make the connection. It should work the same for you.

[infineum]

Based on the discussion, I guess there are two options; connect to the nework, logon the server and run the RSLogix instance on the server or connect to the nework, logon the server and run RSLogix from my computer using RSLinx Gateway on the server. (my computer is remote, server is on the LAN and connected to the PLCs) Can either of these options support more than one remote session, i.e. two people logging on simultaneously and trying to access PLCs? I am sorry for probably asking some basic questions but remote PC access is something that I have little experience or knowleldge with but am trying to learn. Thanks.

[AGENTTINFOIL]

Originally Posted by infineum

Based on the discussion, I guess there are two options; connect to the nework, logon the server and run the RSLogix instance on the server or connect to the nework, logon the server and run RSLogix from my computer using RSLinx Gateway on the server. (my computer is remote, server is on the LAN and connected to the PLCs) Can either of these options support more than one remote session, i.e. two people logging on simultaneously and trying to access PLCs? I am sorry for probably asking some basic questions but remote PC access is something that I have little experience or knowleldge with but am trying to learn. Thanks.

I can not tell you if this will support 2 people logging on simultaneously, I have never tried that before.
what I can tell you is that you can connect to your network and run RSLogix with no problem using the method in my earlier post. I know this is kinda confusing and I hope that I was able to help you out.

[Bob O]

I get the Fatal Error message box when I try to launch it remotely but when I am at the machine it starts without issue. I am working on Windows Server 2003 with Factory Talk Activation and XP.

I was on the phone with RA about something else when I tried to launch logix remotely forgetting that I had problems in the past and the tech on the phone said something to the effect “yeah you can’t do that, you need to be at the machine”.

I f I get a chance I will call in the morning and ask more about it.

[Alcoa Tech]

Hi, I have launched RSLogix5000 remotely using PCAnywhere. I had a VPN setup to save me from the 2am trips into work. I could open RSL5000 and get right online with the processor. I never had a problem.

[rdrast]

I use VPN all the time to get into our plant network, but I run RSLogix and Linx locally on my PC here. It's faster than Terminal Services of PCAnywhere, I don't have to rely on any particular computer being powered up at work, and I don't have to install background programs/services I don't need there.

If you can't go direct, then get a box set up with Logix/Linx at work, leave it up all the time, and put a remote-desktop server on it like PCAnywhere or "Beyond Remote"

[Bob O]

Just spoke with a very nice lady at RA and as of right now, remote desktop and the factory talk activation don't play well together and they are working on a fix.
She suggested other packages but again there is a known bug/issue with remote desktop and factory talk.

So, if you can use something other then remote desktop.

[lbredthauer]

I have two Win2003 servers connected to PLC's with RSLinx and RSLogix 500. One has the old EV activation, the other has the new Factory Talk activation. EV activation works perfectly with Remote Desktop; FT activation doesn't work at all with Remote Desktop. If you find any way to work through the option tags on the Terminal Services to enable this, let us know.

Also concerning Remote Desktop control of RSLinx, you should use the /console option flag when you need to access the RSLinx GUI remotely. Create a copy of your "Remote Desktop Connection" shortcut and change the target line from "%SystemRoot%\System32\mstsc.exe" to "%SystemRoot%\System32\mstsc.exe /console". Note that this login conflicts with any user physically logged in at the terminal.

[Nicodemus]

Are you using Node Locked or Concurrent activations? The remote computer can use the concurrent activation by making a connection to the Activation Server via TCP/IP.

[lbredthauer]

We are using node-locked activations. If I open RSLogix500 from the console physically in front of the machine, I can open Remote Desktop with /console and resume the console session remotely, using any program that I already had open (including RSLogix). If I close RSLogix, though, I cannot re-open the program remotely. I hope this helps.