[ale] DHCP and M$

[Robert Coggins]

One other suggestion to the .BAT file thing.  Maybe put it in the 
startup menu so it will run when they login it will run. Or maybe even 
in the registry.... just my 2 cents. :)

James Kinney wrote:

>Many thanks!! The icon at the bottom is the best solution to the current
>hitch. I still can't get the Sonicwall VPN to authenticate a user inside
>the firewall with the AD server yet. The logon script is not run by the
>VPN client as directed. When I run it manually, it gripes about an error.
>When I run it automatically from inside the network, it works just fine
>and maps drives and printers correctly.
>
>Linux is so much easier..... (except OpenLDAP which is a real monster! If
>this is "lightweight" ...)
>
>  
>
>>Responding to my own message....  :-)
>>
>>Another nice feature in the WinXP network configuration window
>>is the new "Support" tab under the Status window.  It shows
>>the current IP address/mask/gw and whether it's static or DHCP.
>>It also has the same Repair button mentioned below to release
>>and renew the DHCP lease.  And, if you click on Details, it
>>basically shows what you see from ipconfig /all (including
>>MAC address, DHCP server address, lease details, etc.), in a
>>much more user-friendly format.
>>
>>Alan
>>
>>--On Wednesday, February 25, 2004 2:08 PM -0500 Alan Dobkin
>><ALE at omnicomp.org> wrote:
>>
>>    
>>
>>>Here's a solution for you to try:
>>>
>>>Since you mentioned WinXP specifically, it has a feature called
>>>"Repair" in the network  control panel, which is basically the
>>>same thing as an ipconfig /release && ipconfig /renew.  One
>>>difference is that it works for regular (non-admin) users.
>>>
>>>So, the solution is to enable the checkbox that says "Show
>>>icon in notification area when connected" for your network
>>>card, which will put the icon in the systray.  Then your
>>>users can simply right-click on it and select "Repair".
>>>
>>>Alan
>>>
>>>--On Wednesday, February 25, 2004 12:14 PM -0500 James Kinney
>>><jkinney at localnetsolutions.com> wrote:
>>>
>>>      
>>>
>>>>Sorry to ask this here as it is truly a M$ problem.
>>>>
>>>>WinXP seems to aggressively cache DHCP client settings. So much so
>>>>that plugging in a laptop into another network and rebooting will
>>>>not reset the ip address. It will keep the original one unless
>>>>ipconfig /release, ipconfig /renew are run manually.
>>>>
>>>>The problem: User must be a power user or higher to run those
>>>>commands. _THESE_ users should never have power user status
>>>>
>>>>Some setup details: The DHCP server that passes the address that
>>>>won't go away is set to have lease times of days. For the desktop
>>>>machines, this is OK. For the in-and-out laptops, this is a mess.
>>>>Could the extra long lease time be adding to the misery?
>>>>
>>>>The more I use M$ servers the more I like pencil and paper.
>>>>
>>>>--
>>>>James P. Kinney III
>>>>CEO & Director of Engineering
>>>>Local Net Solutions,LLC
>>>>770-493-8244
>>>>
>>>>http://www.localnetsolutions.com
>>>>
>>>>GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics)
>>>><jkinney at localnetsolutions.com>
>>>>Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
>>>>
>>>>_______________________________________________
>>>>Ale mailing list
>>>>Ale at ale.org
>>>>http://www.ale.org/mailman/listinfo/ale
>>>>        
>>>>
>>>_______________________________________________
>>>Ale mailing list
>>>Ale at ale.org
>>>http://www.ale.org/mailman/listinfo/ale
>>>      
>>>
>>_______________________________________________
>>Ale mailing list
>>Ale at ale.org
>>http://www.ale.org/mailman/listinfo/ale
>>
>>    
>>
>
>
>  
>