I went round and round with IBM regarding a Device Licensing issue under terminal services earlier this year. Not certain this applies to your situation but here is some information.
I had an issue with Device Licensing not working properly when connections were made to a terminal server via a Non-Windows based thin client. I contacted IBM support and they told me that Device Licensing on a terminal server uses the WTSQuerySessionInformation() API call to determine the IP of the end point of the connection to apply to Device Licensing. However, it turns out they really use the deprecated (according to Microsoft) system call GetHostByName(). I was able to get around my particular issue by making DHCP reservations on my server for each of my non-windows based thin clients, and then making host entries on the terminal server so those IP's would resolve to unique host names. I suspect you may be having a similar issue. Each of your connections to a terminal server needs to resolve to a unique hostname via GetHostByName(). I may have an exe you can run for testing of this. Hope this helps, I fought IBM on this one for several weeks. Greg -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of phil walker Sent: Monday, July 30, 2007 8:51 PM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Device Licensing Guys, I have narrowed the problem down further. It appears that Win2K3 SPx is not the issue, as when I rdp to myself and then connect to the U2 machine using Accuterm then device licensing works. So what appears to be happening, is that the uvdls shell script is interrogating the connecting machine to get the machine name of the machine, or the connecting machine in the case of a terminal server. The examples are as follows: a,b, and d work, c does not. a) standalone PC inside firewall/juniper networks, e.g. PC1, connecting to the U2 server. Then the client name returned by SYSTEM(51) is PC1. b) standalone PC inside firewall/juniper networks, e.g. PC1, connecting to a terminal server, e.g. TS1, connecting to the U2 server. Then the client name returned by SYSTEM(51) is PC1. c) standalone PC outside firewall/juniper networks, e.g. PC1, connecting to a terminal server, e.g. TS1, connecting to the U2 server. Then the client name call fails. Reason to be determined. DNS or Port Blocking???? d) standalone PC outside firewall/juniper networks, e.g. PC1, connecting to a terminal server, e.g. TS1, connecting to a terminal server, e.g. TS2, connecting to the U2 server. Then the client name returned by SYSTEM(51) is TS1. I have spent enough time at the moment trying to get this to work, so for the moment I will terminal serve in through the firewall and then do it again to localhost to get DL working. When I get some breathing time I will see what is causing the name lookup to fail through the firewall/juniper networks software. Cheers, Phil -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Powell Sent: Monday, 30 July 2007 11:45 a.m. To: u2-users@listserver.u2ug.org Subject: RE: [U2] Device Licensing Phil, What happens when you open a "dos" box (on the 2003 server) and type "nslookup your_uv_host_here"? Also, have you tried using the IP address of your target host? To open a dos box on win2k3 from the start menu select run and type "cmd" in the dialog. You should get a console with a black background. It seems to me that your Win2k3 server isn't resolving the host by name. This could be a DNS issue. If so check to see if your domains match between the win2k & win2k3 machines. Jeff On Sun, 2007-07-29 at 22:28 +1200, phil walker wrote: > Hi all, > > Okay, I now have the following cases: > > DynamicConnect and Telnet on PC running Windows 2000 logged in locally - > works > AccuTerm and Telnet on PC running Windows 2000 logged in locally - works > AccuTerm and SSH on PC running Windows 2000 logged in locally - works > Accuterm and SSH on PC running Windows 2000 Server logged in via RDP - > works > DynamicConnect and Telnet on PC running Windows 2000 logged in via RDP - > works > Accuterm and SSH on PC running Windows 2003 Server Service Pack 1 or 2 - > does not work > 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. > > ------------------------------------------------------------------------ > > As others have posted: > > Device Licensing works for both U2 databases as long as you have a > license > which is one of: > > * Workgroup > * Enterprise > * Server with device licensing (a recent offering) > > In order that this will work you need a TELNET client that supports > Device > Licensing, and as there have been some changes in DL internals over time > they should also concurrent in release - ideally (of course) the latest > releases or fairly close. > > IBM supply SBClient, wIntegrate and Dynamic as Telnet clients that work > with > DL - on wIntegrate and DC you need to remember to check the "Use Device > Licensing on Unix" check box if that is you server platform. DL will > also > work with UniObjects and ODBC (for example) thought you should read up > on > the use of subkeys for UO. > > Some 3rd parties have arrangements with IBM to use the DL software > libraries > with their software, and they offer DL compatibility with their TELNET > clients. It is worth noting the point above though, DL internals have > changed over time. You might find that older versions of the TELNET > clients > may not work correctly froma DL viewpoint with more recent copies of > the > databases. That being the case then an upgrade from your friendly local > TELNET client provider to a current build with updated software should > resolve it. > > Issues which got in the way in the past related mostly to combinations > of > "stty" settings in Unix, all (even vaguely) recent versions got the code > modified so that's not an issue. There was also an issue more recent) > where > ODBC sessions (for example) used a different DL user pool to TELNET > sessions. So ODBC would allow up to 10 sessions as one license, and > TELNET > would do the same - but each connection would use a separate slot. In > those > circumstances (for example) one UO and one TELNET would take 2 licenses > (fixed). > > Always a useful test - try using Dynamic Connect from the current client > software............that should work fine and act as a check on any 3rd > party software. > > Hoping this answers any queries - please post if any follow-ups. > > Regards > > JayJay > ------- > ------- > u2-users mailing list > u2-users@listserver.u2ug.org > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
