OT: Linking a new network to the LAN
Boaz Bezborodko
boaz at mirrotek.com
Thu Dec 29 06:00:43 PST 2011
>> Message: 4
>> Date: Wed, 28 Dec 2011 23:46:26 -0500 (EST)
>> From: Jay Ashworth<jra at baylink.com>
>> Subject: Re: OT: Linking a new network to the LAN
>> To:filepro-list at lists.celestial.com
>> Message-ID:
>> <2512704.2346.1325133986020.JavaMail.root at benjamin.baylink.com>
>> Content-Type: text/plain; charset=utf-8
>>
>> ----- Original Message -----
>>> From: "Boaz Bezborodko"<boaz at mirrotek.com>
>>> I have a machine using an Allen-Bradley PLC that is addressed to
>>> 10.1.1.x while my LAN is 192.168.1.x. I need to let the machine's
>>> designer have access to the PLC via the internet in order to make a
>>> small change to the program. I have set up a VPN server connection on
>>> my computer for him to access the network, but he still can't access the
>>> PLC. His A-B support told him that I would need to add a router to the
>>> machine and set it up to look at my network as a WAN while using port
>>> forwarding to access the PLC.
>> Bill's right; if there's no particular reason why the device needs to be
>> in 10.1/16, you should move it to the 192.168.1/24 network the rest of your
>> LAN is already using.
>>
>> Do note that if the remote guy's LAN is also 192.168.1/24, that won't work,
>> unless your VPN router is quite intelligent (I think that's called NAT444).
>>
>> When you say "I have set up a VPN server connection on my computer", it's not
>> at all clear what you mean by that; incoming VPN sessions generally terminate
>> on the network's edge router, not on a workstation.
>>
>> Can you clarify some?
>>
>> Cheers,
>> -- jra
>> -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I
>> Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000
>> Land Rover DII St Petersburg FL USA http://photo.imageinc.us +1 727
>> 647 1274
I set up a VPN server on my XP machine and forwarded port 1723 to my
machine. Supposedly he was able to see the PLC with his software, but
unable to connect to it. The reason, according to his A-B support guy
was that they were on different networks.
More information about the Filepro-list
mailing list