Ports used as standard

  Process Listening port Incoming connections from Protocol Encryption Description
versiondog Server VDogAdminServer.exe 64001 versiondog Clients Proprietary TLS1.2 Contact point for AdminClient or configuration management
  VDogCheckInCheckOutServer.exe 64002 versiondog Clients Proprietary TLS1.2 Check-In and Check-Out versions
  VDogScheduler.exe 64003 versiondog Clients Proprietary TLS1.2 Scheduler for backup jobs
  VDogOsServer.exe 64004 versiondog Clients Proprietary TLS1.2 API mapping of operating system functions
  VDogReportingServer.exe 64006 versiondog Clients, WebServer Proprietary TLS1.2 Report data for the web server and clients
  VDogSecureConnect.exe 64021 versiondog Clients Proprietary TLS1.2 Metadata management
  VDogApi.exe 64023 versiondog Clients HTTP2.0 TLS1.3

Client authentication

The hub uses the API interface port to find all of the other ports that it requires.

 
Agent VDogUploadAgent 64010 versiondog Server Proprietary TLS1.2 Execute uploads via the versiondog server from the agent
  VDogCompareAgent 64011 versiondog Server Proprietary TLS1.2 Execution comparisons via the versiondog server from the agent
 
Gateway VDogGateway 64012 Depending on use Proprietary Depending on use. Forwards communication between the versiondog server, clients or PLC (depending on the configuration)

Modifying standard ports

The ports shown above are the default ports configured for a standard versiondog server. These ports may be changed.

To change any port number, follow this procedure:

  1. Stop the VDogMasterService service.

  2. In your vdServerArchive folder, open the file \VD$A\Configuration\csc.ini.

    Every process that listens to a port has a section.

    Change the key 4852 in the corresponding section to the new port number.

    For example, if you want to change the port of the VDogAPI process to port 64024, the section in the ini file should look something like this:

    [VDogApi.exe]

    4850=1

    4852=64024

    4851=localhost

  3. Change your firewall configuration to allow the communication through the new port. See your local system administrator to do that.

  4. Restart the VDogMasterService service again.

Process/ Service Local address Remote address Protocol Remote ports Local ports Changeable port Description
Hypertext Transfer protocol versiondog Server - TCP TCP 80 Dynamic port range No data  
Microsoft Active Directory-domain services, Windows shared folder versiondog Server - TCP TCP 445 Dynamic port range No data  
NetBIOS Name Service versiondog Server - UDP UDP 137 Dynamic port range No data  
NetBIOS Session Service versiondog Server - TCP TCP 139 Dynamic port range No data  
VDogAdminServer.exe/ VDogToDoServer.exe versiondog Server / Agent SMTP TCP TCP 25 Dynamic port range No data  

 

Image: Required ports