How to setup two Radio RRCs within same network

[N4QS]

I have been using RRC1258 Elecraft twins successfully for many years.  I would now like to install a second Radio RRC at a second operating position at my remote farm location.  They would both be part of the same LAN.  The first Radio RRC is setup as 192.168.0.228 and I setup the second Radio RRC as 192.168.0.227.  In the second Radio RRC what port numbers do I use under Advanced settings.  Can I use the same (default) ports as I do in the first Radio RRC?  13002, 13001 and 1300?  Or do I have to change these ports to not conflict with the first Radio RRC?  If so, what port numbers should I use?  So far I cannot get my Control RRC to sync with the second Radio RRC.  Thanks in advance for any assistance.  73,  Dave, N4QS

[sm2o]

Hi

you must have different portnumbers to be able to make portforwarding in the router I use to increase to 13100,13101,13102 for the second RRC and 13300... etc for the third

73 de mike

[N4QS]

Thanks Mike.  That's what I thought.  Do you also have to have different Web Server ports?  The user manual says that the web and telnet ports have to be different for each Radio RRC.  Is that correct?

Dave, N4QS

[N4QS]

Mike, I changed my ports for the second Radio RRC to 13102, 13101 and 13100.  Now I can turn on the radio from the control K3(0) mini, but the mini then goes into Term mode.  No control of radio and no audio.  I assume that means the SIP port is working -- 13100.  But why are the cmd and audio ports not working?  Any thoughts?  I have port forwarded all three ports in the router.  Dave, N4QS

[sm2o]

Hi
The Telnet port should never be forwarded. The webserver port is only for the human interface, but need to have a unique port if you use it. If you forward the webserver port be sure to use password in the RRC.

check that the second K3 has correct baudrate settings compared to the RRCs

you can email me exportered settings(html) files from both units so I can have a look

73 de mike

[N4QS]

Mike,

I got it working.  Turns out it was a cabling issue with the K3.  Thanks for the help on port forwarding.

73,

Dave, N4QS