Hi Greg,
I had wondered about that, but had not explored it further as getting this far has take 3-4 days of trial and testing ;-). We have users who connect in via a web page from pcs anywhere in the world. This web page running Juniper Networks software then establishes an RDP session through to the terminal server TS1, which is then used to connect to the U2 Machine, U2M. Interesting enough if I rdp to localhost when on TS1 DL works, and sees this TS1 as the client. If I connect to another Windows 2003 terminal server, TS2 from TS1 then it does not (connecting to another Windows 2K terminal server TS3 does), although TS1 is on domain A and (TS2 and TS3) are on domains B - not sure if this makes a difference. Really confusing...... I will tried putting the entries of the web servers in the host file on the server to see if it makes a difference and it appears not. This is the error: 08:30:30 08/01/07 pid = 2760 U2GetMachId(): unable to get host information of hostname Error = 131 Opening u2licn.dll in ultraedit using ascii mode I can see a mention of U2GetMachId, this error and WTSQuerySessionInformation, but no mention of GetHostByName. Cheers, Phil. From: Greg L. Bonebrake [mailto:[EMAIL PROTECTED] Sent: Wednesday, 1 August 2007 6:00 a.m. To: phil walker Subject: RE: Device Licensing Phil - Haven't seen my response show up on the list so I thought I would email you directly. Your issue sounds similar to an issue I had a while back. - 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 Bonebrake Pick Professionals, Inc. Direct - 314-558-1481 Fax - 314-558-1481 [EMAIL PROTECTED] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
