Phil UniVerse does not require an extra <CR>. Are you appearing to hang in the login after User ID and Password? Hitting <CR> to get past the hang? If so - then waiting long enough and you should get past the hang on a timeout (if it is what I suspect) - though DL would not be activated.
This looks like either a delay/timeout problem or characters getting massacred in the TELNET data stream. I have seen this problem on Unix servers with some of the past issues with DL - resolution upgrade client and server. "STTY" settings being the issue to point, or timeouts due to delays in the data stream. On Windows though I haven't seen this. If you are using SSH I wouldn't be surprised if it didn't work - There's SSL inbuilt into DC and UniVerse which I recommend you use as an alternative. Otherwise if you are accessing via a PAD, VPN or network concentrator which slows the TELNET data stream or filters it? Does it make a different if you login in one of these scenarios? 1. From the server console using DC as a local administrator. 2. From a client PC using DC as a (server) local administrator 3. As 1 and 2 as a (server local) power user? Note: LOCAL users please not DOMAIN. Also make sure the administrator you use is an administrator in their own right - not as a result of inheritance via a tiered domain user structure. It works fine on my standalone fully patched Windows 2003 server with XP clients and DC using 10.2.anything server and DC. Regards JayJay <snip> DynamicConnect and Telnet on PC running Windows 2003 Server Service Pack 1 or 2 - does not work Get the following error messages in U2devlic.err file in directory: 11:26:08 06/28/07 pid = 3180 U2GetMachId(): unable to get host information of hostname Error = 131 12:56:16 06/28/07 pid = 1748 U2GetMachId(): unable to get host information of hostname Error = 183 During the uv login process a return is required to continue the login. This is before the license check is done, as if there are no licenses available this is displayed after pressing the return. When System(51) is displayed it shows 0.0.0.0 For the other scenarios which work, no return is required to complete the login process. System(51) displays the correct information and multiple sessions can be established under the same license. Interesting is that I RDP into the box A which is running Windows 2003 Server from my remote office through the corporate firewall and then RDP into box B which is running Windows 2000 and connect via AccuTerm then this works and System(51) gives the information pertaining to box A. However when I try and connect via AccuTerm directly from box A, then it does not. A firewall issue, or a Windows 2003 Server issue. Has anyone got U2 Device Licensing running under Windows 2003 Server or through a firewall? I suspect the U2GetMachId() function is doing something which is getting blocked by something???? What though?? Any ideas anyone??? Cheers, Phil. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
