curt2000
asked on
DHCP assigned metrics with Windows 7 clients
I have 100 Windows 7 laptops that, when docked, have an active wired and wireless connection at the same time. Our Windows Server 2008 R2 AD server issues DHCP addresses on a different subnet for for wired connections versus wireless connections.
I'm trying to configure a Metric for the wireless DHCP addresses using the scope option of "Microsoft Default Router Metric Base" and assigning a value of 0x1F4 (or 500 in decimal). This is to ensure that when laptops are docked with active wired and wireless connections that the wired connection will take priority. However, the scope option doesn't seem to be taking effect on the wireless adapter settings.
After renewing the DHCP addresses, running "ROUTE PRINT" on the laptop shows that the wired metric is 266 and the wireless is 276 - just as before. All other scope options are fine (router, gateways, etc.).
Manually changing the adapter and bindings settings on each laptop by moving the "Local Area Connection" to the top of the list is not feasible in this situation.
Any ideas?
I'm trying to configure a Metric for the wireless DHCP addresses using the scope option of "Microsoft Default Router Metric Base" and assigning a value of 0x1F4 (or 500 in decimal). This is to ensure that when laptops are docked with active wired and wireless connections that the wired connection will take priority. However, the scope option doesn't seem to be taking effect on the wireless adapter settings.
After renewing the DHCP addresses, running "ROUTE PRINT" on the laptop shows that the wired metric is 266 and the wireless is 276 - just as before. All other scope options are fine (router, gateways, etc.).
Manually changing the adapter and bindings settings on each laptop by moving the "Local Area Connection" to the top of the list is not feasible in this situation.
Any ideas?
ASKER
For the particular laptop I'm on now the wireless adapter does not have the option for enabling Priority or VLAN. The wired adapter does, but I'm trying to set a metric for the wireless adapter via DHCP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check this page:
http://technet.microsoft.com/en-us/library/cc782411%28WS.10%29.aspx
It says:
-------
Default Router Metric Base
This option can be used to set the default base metric for DHCP clients running Windows Server 2003. When this option is set, the DHCP Client service uses the value configured here as the base metric for its default gateways.
Code
3
Length
4 octets
Value
This value represents a specified router metric base to be used for all default gateway routes used by DHCP-enabled clients running Windows Server 2003. This value can be assigned as an integer representing a cost metric ranging from 1 through 9,999. It is used in calculating the fastest, most reliable, and least expensive routes. If a value is not specified, a default of either one (1) or the currently set interface-specific metric is used.
---------
If it works with WIn2003 clients, it might also work with Win7 clients.
Its in "microsoft options":
http://technet.microsoft.com/en-us/library/cc782411%28WS.10%29.aspx
It says:
-------
Default Router Metric Base
This option can be used to set the default base metric for DHCP clients running Windows Server 2003. When this option is set, the DHCP Client service uses the value configured here as the base metric for its default gateways.
Code
3
Length
4 octets
Value
This value represents a specified router metric base to be used for all default gateway routes used by DHCP-enabled clients running Windows Server 2003. This value can be assigned as an integer representing a cost metric ranging from 1 through 9,999. It is used in calculating the fastest, most reliable, and least expensive routes. If a value is not specified, a default of either one (1) or the currently set interface-specific metric is used.
---------
If it works with WIn2003 clients, it might also work with Win7 clients.
Its in "microsoft options":
Sorry, I pressed OK before being done !
I was saying, it is in "Microsoft Options":
Bb878031.cg040501-l-en-us-.gif
You get there this way:
DHCP/Server Options or Scope Options (or even options in reservations)
Advanced Tab
Select "Microsoft Options".
Tell us if this worked !
HTH
I was saying, it is in "Microsoft Options":
Bb878031.cg040501-l-en-us-.gif
You get there this way:
DHCP/Server Options or Scope Options (or even options in reservations)
Advanced Tab
Select "Microsoft Options".
Tell us if this worked !
HTH
ASKER
Sorry for the delay in responses, I was in meetings all day yesterday.
MarkieS - Thanks for the script. I'll have to try it out, but looks like it could work in our environment. Previously I found another person that was using a script for their solution too (found at http://www.myitforum.com/forums/m173977.aspx), but I was hoping I could accomplish my task by using a DHCP scope option. I'll try out your script and it's much appreciated.
vivigatt - Thanks for the info too, but that was the solution I started with before posting my question. I haven't been able to get it to work. Again, I used 0x1F4 for my metric base, but it doesn't seem to impact my Windows 7 machines. Do you think that this applies to only Windows XP and older clients maybe? I'll have to test this just to find out.
MarkieS - Thanks for the script. I'll have to try it out, but looks like it could work in our environment. Previously I found another person that was using a script for their solution too (found at http://www.myitforum.com/forums/m173977.aspx), but I was hoping I could accomplish my task by using a DHCP scope option. I'll try out your script and it's much appreciated.
vivigatt - Thanks for the info too, but that was the solution I started with before posting my question. I haven't been able to get it to work. Again, I used 0x1F4 for my metric base, but it doesn't seem to impact my Windows 7 machines. Do you think that this applies to only Windows XP and older clients maybe? I'll have to test this just to find out.
The metric assigned by DHCP is only for the route to the default gateway. But I admit that I never tried to use it... I'll try that later and if I understand how it works/what it does, I'll tell you
If you want you can read my article:
https://www.experts-exchange.com/Software/System_Utilities/Remote_Access/VPN/A_2977-VPN-use-default-gateway-AND-access-your-local-network.html
With my NICIndex utility, you can use
route change
to change the metric of a specific route.
A script run on the client side then becomes as simple as:
If you want you can read my article:
https://www.experts-exchange.com/Software/System_Utilities/Remote_Access/VPN/A_2977-VPN-use-default-gateway-AND-access-your-local-network.html
With my NICIndex utility, you can use
route change
to change the metric of a specific route.
A script run on the client side then becomes as simple as:
NICIndex.exe /IPPrefix=193.105.13. /Type=Ethernet > %temp%\SetNIC.bat
if exist %temp%\SetNIC.bat call %temp%\SetNIC.bat
route change 192.105.13.0 MASK 255.255.255.0 %NICIP% Metric 50 IF %NICIDX%ASKER
This is the solution that worked for us. Thanks for sharing!
ASKER
Oops, I should state the script from MarkieS is the solution.
Try the options to see if it helps.
(refer: http://www.tomshardware.co.uk/forum/31846-17-select-wireless-internet-wired-internet ) for some guidance
See the image at the end of the document