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

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? 

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)?

The command line is  uniface.exe /asn=app.asn /ust=mark1234 demo tcp:  where demo is the startup shell. 

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.

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

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.

Thanks for sharing.