Home > Location Management > Locations > Screen Shots/Explanations > Locations - Communications
This tab will allow you to set up communications details for this location. The right side of the screen is not considered a standard part of the system and only exists for backwards compatibility for some clients.
Figure: Example Locations Screen
Communications
ConfigurationWhen a user starts the main menu, the system will work out the user's location and download these communication details. This tells the system how that user should be connected to the back end servers.
See Communications Configuration for further details
|
Primary Connection |
The configuration code that should be used for the primary connection to the back end servers. |
|
Backup Connection |
If there is a fault with connecting, the programs will attempt to use this second code. |
|
Backup Connection 2 |
If the second attempt fails, it will switch to the third one. |
Transfer Files
Only used if you are using the FileTransferService to transfer files between locations.
|
Use Torex BE Comms |
Check on if you are using File Transfer Service to transfer files for this location. If not required for comms then set to unchecked. |
|
IP Address |
This is the IP Address of the computer used to connect to this location. This can be a numeric IP address or a DNS name, for example micros.com |
|
RAS Name |
This is the name of the Dial Up Networking connection used to connect to the computer. If this is entered, then File Transfer Service will use RAS (Remote Access Service) to connect to this location. If you have a direct TCP/IP connection to the computer then you can leave this empty. |
|
Transfer Files Communications Profile |
Communications profile to be used by the File Transfer Service for this location. |
|
File Transfer Service Communications Profile |
Communications profile to be used by the File Transfer Service for this location. |
|
FTP User Name |
User name to log on to the ftp server. |
|
FTP Password |
Password to log on to the ftp server. |
| Converted from CHM to HTML with chm2web Pro 2.85 (unicode) |