Great input, Tony. But be warned WJ, if your client PCs are external to your network, then Private Addressing and NAT may make this whole exercise nugatory. For example, if your host network / server is on your 10.x.y.z (or 192.168.a.b) and your remote client is on his 10.x.y.y (or 192.168.a.c), then you may end up resolving the name for the remote client as being whatever has 10.x.y.y (or 192.168.a.c) assigned on its local network. IPv4 addresses are legitimately non-unique.
Regards Mike -----Original Message----- From: u2-users-boun...@listserver.u2ug.org On Behalf Of Tony Gravagno Sent: Friday, 7 September 2012 1:48 p.m. To: email@example.com Subject: Re: [U2] [Windows] Here are a number of ways to link a telnet client into UV back to its respective hostname. There's some redundancy here as not all commands work everywhere. [snip] I'm sure none of that was helpful to WJ who will say "no, that's not it at all, what I really want is..." but I trust it will benefit someone else. T _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users