Connecting to Virtual Machine from local PC

I have created a virtual machine Windows server on Azure. The name of the machine is 'training'. It has given me a public ip address.
I can ping this server from my PC using the ip-address and also by name training as i have entered the server name in the hosts file

i have created a database and started it on the virtual server using service no. 4001

I connect to the virtual machine by RDP from my PC

I can connect to the openedge-server if i connect to the virtual machine(thru RDP)

Now i want to connect to the openedge-server using my PC (without RDP) like client-server mode.
I use following parameters
-H training (hosts file entry training n.nn.nn.nnn) where n.nn.nn.nnn is the actual ip address of azure virtual machine
-S wpos (4001/tcp)
-N tcp

the actual command is
C:\11dbase\bin\prowin.exe illuminate -H training -S wpos -N tcp -ld prodata -d dmy -ini illuminate.ini -p c:\promac\programs\userlog.w

i get error connecting to the server error-code 1432

Can anyone please help where I am going wrong and where i should change.

I am open to other suggestion to connecting. I want to move my server from on-premises to cloud.


Quite urgent please.
Thank you in advance.
 
When an ABL or SQL client connects to a database via TCP, it needs to make two connections:
  • First, to the login broker on its service port (the value of -S for the broker).
  • Once connected, the broker sends the client the port number of the server it should connect to.
  • The client disconnects.
  • The client connects to the server on the provided server port number. It remains connected to this port until the session ends or it programmatically disconnects from the database.
The server port number will fall somewhere within the login broker's specified -minport/-maxport range. You should always explicitly specify these parameters when you configure a login broker.

In summary, you will need to create firewall rules to allow connections to the broker port and the entire range of server ports. If the database has multiple login brokers (e.g. one for ABL and one for SQL), there will need to be multiple sets of firewall rules.
 
Back
Top