Ron G

OK, just got off with the IT guy. Explained that I am NOT seeing the ports open. He went into the settings of the router and sure enough, the Anonymous Internet Request box was checked. He unchecked it, and I could now see port 2222, but not 44818. Checking further, we found that he had set port forwarding on 44218, not 44818. Silly typo. Looks like we had multiple issues going here. Once he set port forwarding on 44818, I can connect to my machine. Thanks for everyon'e help. Ron

Hmmm, never used NMAP before. Nice tool. turns out that the ports are still closed, even though he setup Port Forwarding. Now that I know the ports are showing as closed from the outside, I did some research. It looks like there is a second setting in the WRT54G router that blocks all anonymous Internet Requests. If that box is still checked, the router will not respond. I will see what happens when their IT gets back to me. Thanks for all your help

That is exactly what I did, ping xxx.xxx.xxx.xxx:44818. I got a response, where simply pinging xxx.xxx.xxx.xxx gave me no response. Silly me, I was under the impression that this worked in a similar manner to entering the ip address and port number in a web browser. So, I am not really getting a response then? Argh. Thanks for the responses folks Ron

Ok, here's the situation. I have a customer that has one of our machines in another state. I am trying to remotely connect to the machine over the Internet. I am using the Remote Devices via Linx Gateway driver, trying to connect to a 1768-ENBT ethernet card on a compactlogix rack. I have used this driver for connecting to other machines in a similar manner. In fact, I can view a few machines around the globe with my current setup (This tells me that my local computer is capable of connecting). The customer has a simple peer to peer network behind a Linksys WRT54G router. I asked them to setup port forwarding on ports 2222 and 44818. This has been done. The IT guy can remote desktop into a machine on the network and from there, he was able to enter the local IP address of my ethernet card, 192.168.1.130 in a browser window. He was able to pull up the web page from the ethernet card showing its configuration. Using remote desktop to his machine (Yup, remote connecting to a machine that has a remote connection, ain't the Internet great?), I was able to see for myself that the ethernet card is setup properly, as well as the port forwarding on the router. The gateway on their router is 192.168.1.1. For some reason, I seem to recall hearing that using x.x.1.1 can cause issues with RSLinx. However, I can find no mention of this anywhere on the internet. I also checked with AB on this, they have no record of that being an issue for remote connections either. Anyone hear anything like that? On other customers' machines, after doing this, I enter the IP address of the customer in the RSLinx configure driver, Server's IP address or hostname. On the Configure Browser tag, I also enter the IP address of the ethernet card on the customer's netowrk. I did this for this machine and I see the message along the top of the RSLynx window "Browsing - Node 69.183.xxx.xxx not found (I editedt the IP for privacy). My next step is to ping the customer. I try to ping the IP address I was given, and no response. However, if I ping the specific ports, 2222 or 44818, I get a response back. To me, that says the machine is online, but somehow the router is not allowing me to connect. I contacted Rockwell, and they say that I have everything setup fine on my end, it must be a remote issue. I contacted the customer's outside IT guy and he has no experience setting up remote connections for Rockwell software. He spent a few minutes trying to explain to me how we should provide the customer with a full copy of RSLogix5000 so that they can perform the troubleshooting themselves, or that AB should provide a copy for free with every processor. This should tell you all you need to know about his past experience with Rockwell and AB <LOL>. Has anyone else experienced this issue where you can ping the machine, but cannot connect? Oh, I also am running RSLinx version 2.53, if anyone asks. Thanks in advance for any help anyone can provide. This one has me stumped. Ron

Ok, I am stumped, and the vendors cannot seem to either understand my questions, or just simply don't know the answers. I have a legacy system that I need to connect to. I want to go online with the Processor and monitor the program as it is running. The system is as follows: Mitsubishi A2USH cpu-s1 PLC Proface GP477R-EG11 HMI These two are connected with a ProFace GP070-MD11 (Two Port Adaptor) The cable between the processor and HMI is GP070-MDCB11 I am using Mitsubishi's GX Developer to go online with the program. I made two calls to my local Mitsu vendor, and they can give me no information on connecting the processor with the ProFace GP070-MD11 installed. They suggested I call ProFace. I called ProFace twice. The first time, they told me that I needed to buy the GP070-MDCB11 to hook my laptop to the PLC. This was incorrect. The second time I called, they told me that I should connect to the HMI's serial port (RS232) and I would be able to monitor the PLC from there. Well, there is a combination RS232/RS422 port on the back of that HMI. It already has the aforementioned GP070-MDCB11 cable connecting the HMI to the PLC. I would need to remove it to connect my laptop. Doing this will then disconnect my PLC from my HMI. My thinking is that the GP070-MD11 is where I should plug in. It has two ports on it labeled Computer and GPP. I tried connecting to both ports with no luck connecting on either. I tried using a simple serial cable with a 9-25 pin adaptor, no luck. I tried using an SC-09 cable (RS232/RS422 converter), no luck. I found that I can pull the GP070-MD11 off the processor and plug in my SC-09 cable and go online with the processor, so I know that cable is ok, as well as the port on the processor. I have used various Mitsu products over the years starting with the old DOS Medoc. I am familiar with the occasional issues communicating with their processors when combined with various HMI's.....but this one has me stumped. My thinking is that the port on the GP070-MD11 is simply bad and will not allow me to communicate. But I do not want to jump in and replace it only to find out I was using the wrong cable or setting. Is there anyone out there that has had a similar experience or knows how to make this GP070-MD11 work for me? To sum it up.......All I want to do is go online and monitor the PLC program for troubleshooting purposes. Thanks in advance for any help you can provide Ron