Prev: Avast Update
Next: Freeware and Understanding
From: REM on 12 Apr 2010 18:06 > za kAT <zakAT(a)johnstubbings.invalid> wrote: >Can't you use their host name? If you use DDNS when they get IP from >DHCP it should register, if set to do that. >Even without DDNS you can get the host name and just look at the >leases on the DHCP server. That will take quite a bit more time than adding an app to quickly display the current domain IP for all users. The host names often resolve incorrectly.
From: B. R. 'BeAr' Ederson on 12 Apr 2010 18:00 On Mon, 12 Apr 2010 14:23:36 -0500, REM wrote: > I'm playing around with BGInfo: [...] > It's not quite what I had hoped for. It doesn't handle the display of > two IP addresses very well. BGInfo depends to some degree on Windows version and setup. Sth. that works on one PC may not on another. Usually the best way to ensure consistency between setups is to feed BGInfo with external information. Maybe take a look at these two sources, if you did not already checked them: www.datamgmt.com/index.php?module=pagemaster&PAGE_user_op=view_page&PAGE_id=70 http://forum.sysinternals.com/disabled-nics_topic18592_post115159.html#115159 HTH. BeAr -- =========================================================================== = What do you mean with: "Perfection is always an illusion"? = ===============================================================--(Oops!)===
From: za kAT on 12 Apr 2010 18:14 On Mon, 12 Apr 2010 17:06:10 -0500, REM wrote: >> za kAT <zakAT(a)johnstubbings.invalid> wrote: > >>Can't you use their host name? If you use DDNS when they get IP from >>DHCP it should register, if set to do that. > >>Even without DDNS you can get the host name and just look at the >>leases on the DHCP server. > > That will take quite a bit more time than adding an app to quickly > display the current domain IP for all users. > > The host names often resolve incorrectly. You replied to my spoofing friend. If you have a web server internally, you could set up a page using the same code as showmyip.whatever. Dead simple. Set up DNS to resolve http://showip. User stick it in browser, non scary. Job done. -- zakAT(a)pooh.the.cat - www.zakATsKopterChat.com
From: za kAT on 12 Apr 2010 19:45 On Mon, 12 Apr 2010 17:06:10 -0500, REM wrote: >> za kAT <zakAT(a)johnstubbings.invalid> wrote: > >>Can't you use their host name? If you use DDNS when they get IP from >>DHCP it should register, if set to do that. > >>Even without DDNS you can get the host name and just look at the >>leases on the DHCP server. > > That will take quite a bit more time than adding an app to quickly > display the current domain IP for all users. > > The host names often resolve incorrectly. If you have a web server internally, you could set up a page using the same code as showmyip.whatever. Dead simple. Set up DNS to resolve http://showip. User stick it in browser, non scary. Job done. See why I should be Webmeister 2011? Pooh sez "Go John". -- zakAT(a)pooh.the.cat - www.zakATsKopterChat.com
From: VanguardLH on 12 Apr 2010 20:35
REM wrote: >> REM <REMbranded(a)netscape.com> wrote: > >>http://gallery.technet.microsoft.com/ScriptCenter/en-us/c4aedd21-52a9-4cce-94e6-529af3aa0bba > >>They have lots of nifty scripts! > > That's just a small box that opens with the user IP. Life (for us) > would be so much simplier if I could find a small program that would > write the logon on the desktop background each user logon. > > Talking some of the folks through finding the icon for the script > above, clicking it, not freaking out and listing every icon on the PC > and then reading the IP address to me is more of a chore than you > might think. If this is the great chore that you claim, you are not well-prepared for when users call you with real problems. This is a picyune task compared to most user calls. Someone claiming that they cannot describe to their users on how to double-click on a desktop icon with a particular logo or that such a task is so onerous means that so-called tech isn't worth a gnat's fart for support. What's odd is that you even need to get the user involved in telling you what is the current IP address for their workstation. Why aren't you employing inventory software to monitor those hosts? Of course, you could eliminate the user altogether and simply use Remote Assistance or Remote Desktop to temporarily grab their host to go look for yourself. If this is for a domain where you can push policies, you could push a policy that has the user run a login script (located on a network drive that you identify using a UNC path, *not* a mapped drive). That login script could record the user's IP information into a table saved on a network drive. Of course, a script that only runs at login is no better than your idea of displaying the IP address on the background image for the desktop. Both would report the IP address at the time the user logged in and NOT get updated should the user change that IP address at a later time DURING their Windows session. If setting up the on-host firewall to port-forward for RDP, or pushing policies that enter the exclusion for Windows Firewall, or using RDP is beyond your skill set then start looking at some simpler schemes, like TeamViewer (but you can't use it for free for business use). Of course, with RDP (and probably VNC), you don't need an IP address. Just use the hostname for the workstation (and simply put a sticker on the user's monitor with their hostname). Whether you can get by with just a hostname or have to use a FQDN depends on how WINS works on your intranet. You don't even have to ask the user for their IP address. You could set up your own web page to which they connect and get their IP address from that. If you have to drill past the WAN-side IP address of a router then use Javascript in the web page to get the user's IP address (but that won't help you if they are using a NAT router which means they need to setup port forwarding in their router to point at one of their internal hosts ... trying to connect to their host's 192.168.x.100 IP address won't work). |