Using IP or Hostname in RMS devices
RMS devices must all be programmed with the location of the RMS Software.
When using RMS-CLOUD this is preprogrammed (RMS.ROTRONIC.COM).
When using on-premise the RMS server address must be added. You can use a servers' IP address or Hostname.
For testing I always advise using IP address first.
However using a hostname has benefits, but often when using the server hostname devices will lose communication to RMS server especially on larger corporate networks!
This can be for several reasons...
> If using a Hostname you must also include Domain Name Server details in device IP configuration (DNS servers translate Hostname >> IP eg MyRMSServer >> 192.168.10.10).
> Devices must also have access to DNS servers (via DNS ports typically port 53)
> Often in large networks the Hostname and DNS is still not sufficient. You may need to use Fully Qualified Domain Name (FQDN).
IMPORTANT... When testing RMS Hostname settings from RMS-Config software, the test is only confirming communication from your PC to the Server. RMS devices will have different network access to that of a user PC so this test does not confirm RMS device network access.
When using RMS-CLOUD this is preprogrammed (RMS.ROTRONIC.COM).
When using on-premise the RMS server address must be added. You can use a servers' IP address or Hostname.
For testing I always advise using IP address first.
However using a hostname has benefits, but often when using the server hostname devices will lose communication to RMS server especially on larger corporate networks!
This can be for several reasons...
> If using a Hostname you must also include Domain Name Server details in device IP configuration (DNS servers translate Hostname >> IP eg MyRMSServer >> 192.168.10.10).
> Devices must also have access to DNS servers (via DNS ports typically port 53)
> Often in large networks the Hostname and DNS is still not sufficient. You may need to use Fully Qualified Domain Name (FQDN).
RMS Server Hostname = MyRMSServer
FQDN = MyRMSServer.CompanyName.Local
FQDN = MyRMSServer.CompanyName.Local
IMPORTANT... When testing RMS Hostname settings from RMS-Config software, the test is only confirming communication from your PC to the Server. RMS devices will have different network access to that of a user PC so this test does not confirm RMS device network access.
Brief update.
Using the RMS web server IP address or Hostname you can confirm the FQDN via CMD.
Open CMD and type
eg ping 192.168.1.50 -a
or ping RMS_001 -a
The ping response will include the FQDN (see below server pst-rms-02 is the host and pst-rms-02.processsensing.com is the FQDN)
Using the RMS web server IP address or Hostname you can confirm the FQDN via CMD.
Open CMD and type
ping [RMS Hostname or IP] -a
eg ping 192.168.1.50 -a
or ping RMS_001 -a
The ping response will include the FQDN (see below server pst-rms-02 is the host and pst-rms-02.processsensing.com is the FQDN)
Guest wrote:RMS devices must all be programmed with the location of the RMS Software.
When using RMS-CLOUD this is preprogrammed (RMS.ROTRONIC.COM).
When using on-premise the RMS server address must be added. You can use a servers' IP address or Hostname.
For testing I always advise using IP address first.
However using a hostname has benefits, but often when using the server hostname devices will lose communication to RMS server especially on larger corporate networks!
This can be for several reasons...
> If using a Hostname you must also include Domain Name Server details in device IP configuration (DNS servers translate Hostname >> IP eg MyRMSServer >> 192.168.10.10). snow rider 3d
> Devices must also have access to DNS servers (via DNS ports typically port 53)
> Often in large networks the Hostname and DNS is still not sufficient. You may need to use Fully Qualified Domain Name (FQDN).RMS Server Hostname = MyRMSServer
FQDN = MyRMSServer.CompanyName.Local
IMPORTANT... When testing RMS Hostname settings from RMS-Config software, the test is only confirming communication from your PC to the Server. RMS devices will have different network access to that of a user PC so this test does not confirm RMS device network access.
I have the same question!
No matching posts in this thread.