Uniface urouter over VPN Windows 10 Home. | Uniface Deployment | Forum

Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

—  Results per page  —








— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters
For a group of consecutive words like 'end of support' use Match phrase

sp_Feed Topic RSS sp_TopicIcon
Uniface urouter over VPN Windows 10 Home.
31 Mar 2017
4:18 pm
Avatar
Iain Sharp
Member
Forum Posts: 648
Member Since:
01 Oct 2012
sp_UserOfflineSmall Offline

We have a customer who is trying to connect a uniface client to a server via VPN. 

The client is a windows 10 home netbook, and the VPN is CiscoAnyconnect. 

I can connect to their server from my PC, using VPN Client Version 5, and run our app. 

I can connect to another customer’s server using CiscoAnyconnect, and run our app. 

The DNP is set in the asn file (and I’ve tried it in the command line) as TCP:SERVER+13001|userver|PASSWORD

The error returned is (Leaving the exact names in deliberately)

DNP Logon (TCP:marksconvertibletablet.pndomain.local+13001|mark wood||mark) failed with status -18, Failed to connect to URouter
Fatal error: 9024 – Application stopped due to logon error.

Is there a problem where the user name has spaces in it? It’s the only difference I can think of? 

 I do get (a version of) this error from my PC when my VPN is not connected, but I can browse to and ping the server from the netbook. 

03 Apr 2017
11:09 am
Avatar
diseli
Admin
Forum Posts: 935
Member Since:
01 Oct 2012
sp_UserOfflineSmall Offline

A user name with spaces should not be a problem.

But is the server name correct? Or is the server running locally on the netbook?

Just a couple of ideas: have you tried to use the IP or the machine name without the domain (e.g. marksconvertibletablet) instead of the full machine name?

Hope this helps.

Kind regards,
Daniel

03 Apr 2017
11:14 am
Avatar
Iain Sharp
Member
Forum Posts: 648
Member Since:
01 Oct 2012
sp_UserOfflineSmall Offline

This is the bit I never understand about this ‘cannot connect to urouter’ message. 

We never use the local PC name etc in any of our assignment settings or command line. 

The assignment setting is :-

$DNP=TCP:SERVER+13001|SERVER|userver|PASSWORD

This asn file is in use successfully on 30 other clients for this customer. 

Any idea where the local machine name is found to ‘log on’ to userver? 

03 Apr 2017
12:10 pm
Avatar
diseli
Admin
Forum Posts: 935
Member Since:
01 Oct 2012
sp_UserOfflineSmall Offline

Do I understand it correctly that in the ASN file you specify SERVER+13001 and this will result in a logon attempt to marksconvertibletablet.pndomain.local+13001? That’s weird. It basically would mean that a lookup of SERVER returns marksconvertibletablet.pndomain.local.

I’m, however, not sure why you specify user name and password for the $DNP path. The $DNP path (Default Network path for Postmessage) only accepts the following arguments:

  • Protocol
  • HostID (optional)
  • PortNumber (optional)
  • ClientID (optional)

Syntax: $DNP {=} Protocol:{HostID}{+PortNumber}{|||ClientID} 

And where do you specify the client ID mark? Is this done on the command line or in code (using the open statement)?

03 Apr 2017
12:24 pm
Avatar
Iain Sharp
Member
Forum Posts: 648
Member Since:
01 Oct 2012
sp_UserOfflineSmall Offline

The command line is 

uniface.exe /asn=app.asn /ust=mark1234 demo tcp: 

where demo is the startup shell. 

03 Apr 2017
1:20 pm
Avatar
diseli
Admin
Forum Posts: 935
Member Since:
01 Oct 2012
sp_UserOfflineSmall Offline

Iain Sharp said
This asn file is in use successfully on 30 other clients for this customer.

Does any other client use Windows 10 Home or is this the only one?

And is there any TCP related error logged in the putmess log file (or transcript window) right before the DNP Logon error?

Thanks.

03 Apr 2017
1:20 pm
Avatar
Arjen van Vliet
Member
Forum Posts: 175
Member Since:
01 Oct 2012
sp_UserOfflineSmall Offline

Hi Iain,

Me and a fellow Uniface developer are experiencing a kind of similar behaviour when working from home:

DNP Logon (TCP:leo-laptop.sitecom.router+13001|u97server|BEBFBEB2-CC8E-4952-BA60-B2F60607D960|webstart -drv=ANY) failed with status -18, Failed to connect to URouter

and

DNP Logon (TCP:DESKTOP-9SJV6QJ.dynamic.ziggo.nl+13005|u97server|E0B7649A-D07C-41BA-9824-3EB83A47C77F|wasv -drv=ANY) failed with status -18, Failed to connect to URouter

where ‘leo-laptop’ and ‘DESKTOP-9SJV6QJ’ are our computer names.

My research up until now points towards Consumer-targeted internet connections (at Ziggo, a large cable provider in NL), with a dynamic WAN IP addresses that regularly changes. The provider does this to be able to rotate the limited number of IPv4 addresses.

Remedy seems to be to get a business connection (with fixed IP address) or set-up your fixed IP address at dyndns.com or one of the free equivalents

Cheers,
Arjen

03 Apr 2017
1:56 pm
Avatar
diseli
Admin
Forum Posts: 935
Member Since:
01 Oct 2012
sp_UserOfflineSmall Offline

Arjen van Vliet said
Hi Iain,

Me and a fellow Uniface developer are experiencing a kind of similar behaviour when working from home:

DNP Logon (TCP:leo-laptop.sitecom.router+13001|u97server|BEBFBEB2-CC8E-4952-BA60-B2F60607D960|webstart -drv=ANY) failed with status -18, Failed to connect to URouter

and

DNP Logon (TCP:DESKTOP-9SJV6QJ.dynamic.ziggo.nl+13005|u97server|E0B7649A-D07C-41BA-9824-3EB83A47C77F|wasv -drv=ANY) failed with status -18, Failed to connect to URouter

where ‘leo-laptop’ and ‘DESKTOP-9SJV6QJ’ are our computer names.

My research up until now points towards Consumer-targeted internet connections (at Ziggo, a large cable provider in NL), with a dynamic WAN IP addresses that regularly changes. The provider does this to be able to rotate the limited number of IPv4 addresses.

Remedy seems to be to get a business connection (with fixed IP address) or set-up your fixed IP address at dyndns.com or one of the free equivalents

Cheers,
Arjen  

I have similar issues when I’m not connected to the company network and try to use the locally installed Uniface server. When trying to resolve the localhost the full domain name is used (e.g. client123.uniface.local) and this will fail since the DNS of my ISP does not know this machine. In order resolve this issue I’m using the ASN setting $DEFAULT_TCP_HOST to specify the name of my machine (e.g. $DEFAULT_TCP_HOST = client123). This works for me regardless if I’m connected to our company network or my ISP.

But if I understood Iain correctly then he specifies in the ASN as target of the $DNP path the host with the name (e.g.) server1 and during start-up Uniface will try to open the path using the local machine name (e.g.) client123 instead. So it would seem that resolving the host server1 results in the host name client123. But maybe I’m missing something here.

07 Feb 2018
7:42 pm
Avatar
markhascole
New Member
Forum Posts: 1
Member Since:
07 Feb 2018
sp_UserOfflineSmall Offline

Thanks for sharing. 

Forum Timezone: Europe/Amsterdam

Most Users Ever Online: 131

Currently Online: Adrian Gosbell, tommyb42
18 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

ulrich-merkel: 1762

Iain Sharp: 648

Theo Neeskens: 353

gianni: 297

rogerw: 251

istiller: 235

Knut: 201

lalitpct: 197

Arjen van Vliet: 175

sochaz: 173

Member Stats:

Guest Posters: 3

Members: 8444

Moderators: 0

Admins: 8

Forum Stats:

Groups: 1

Forums: 62

Topics: 2161

Posts: 9344

Newest Members:

briancoleman@aurion.com, kevinmckeever@aurion.com, WarrenNob, brigittebr18, agrohimcsh, englewtat, AbbalibaJor, HanhitCholo, RobertEdumb, lenorajr69

Administrators: admin: 23, Adrian Gosbell: 303, diseli: 935, Bob Maier: 3, Nico Peereboom: 75, Michael Rabone: 4, richiet: 406, JanCees: 28