30 Maret 2010 7:43
I have been using netsh extensivley for configuring and getting configuration information from all dhcp servers via the NETSH command in Windows 2000 and XP. My organization now has some users on Vista (both 32 and 64) and we are making our move to Windows 7. I am now finding that using NETSH from both Vista and Windows 7 is not working as it should. For instance with windows XP and 2000 I could use the command : NETSH DHCP SERVER xxx.xxx.xx.xx dump >C:\tsting.txt and I could get the entire configuration of a DHCP Server into that text file. While this works fine from 2000 Pro and XP (with the correct helper added) i dont get any results..
For Vista (Both 32 and 64) when running this command I get nothing in the text file. Also when using netsh then using DHCP, I get nothing back on the screen. It is like the commands are working, however there is no echo to the CMD window.
For Windows 7, I can use netsh dhcp fine and look at scopes, however if i run the command NETSH DHCP SERVER xxx.xxx.xx.xx dump >C:\tsting.txt i get the Server options, however all portions for adding scopes, scope options and reservations are blank.
Running these commands however from Windows 2000, 2003 and 2008 server works as they are expected to. \
Is there a work around for this or a known fix that I am missing? We try to limit login to server as much as we can as it is our understanding it is best practice from MS to use Server Management tools where ever possible.
any help for this would be greatly appreciated.
10 Mei 2010 4:34
I am having the same issue here after I got a new Windows 7 workstation. I have a vbscript that extracts the scope information using the netsh dhcp command and then adds the active leases etc to an access database for reporting. Now when I run this same script on Windows 7 the scope information is missing and the script fails saying the extract has 0 records.
Have you had any luck with this issue?
25 Mei 2010 9:31
No luck or response from MS on this. Seems to be the same with MS that they never seem to answer me on there new OS security enhancements or better known as removal of features. I gave up on trying to do this and now require all my users that used to be able to gather information on DHCP and move around scopes and such to now log into a central server in order to use the tool. Or have admins go back to Windows XP. I have just found another nice enhancement that is again going to kill me is that with the schedtasks command in windows 7 now by default checks the box "Run only if logged on" is checked and there is no option to uncheck this via the schedtasks command. With each new version of Windows seems MS is programatically breaking all automation tasks that people have been using for years. I dont understand it since MS stated years ago that best practice was to use remote managment tools whenever possible to keep you from logging into the server with admin rights, however with all the "enhancements" that they are making it impossible to do things remotely anymore.
Let me know if you have any luck with this or if you ever get a response. I am starting to think that these forums are pretty much a waiste of time for me and I should start opening up Premier support calls for all of this.
03 Juni 2010 3:40Thanks for your response but I have still not heard anything from Microsoft about this. I still have a Windows XP box from which to run this for now. When we migrate to Windows 7 I will need to review this then. For now, keep using Windows XP.
04 Juni 2010 9:05I have the same issue.
16 Juni 2010 23:03I see the same thing, NETSH DHCP SERVER is only available on servers with dhcp server role installed. This is not good for remote management. Anyone find a solution?
- Disarankan sebagai Jawaban oleh Tim Boggs 16 Juni 2010 23:21
16 Juni 2010 23:23Can't believe I forgot this, just had to install the Remote Server Administration tools, including the DHCP Server Tools. Works on both my 2008 R2 server and my Windows 7 desktop.
- Disarankan sebagai Jawaban oleh Tim Boggs 16 Juni 2010 23:23
23 Juni 2010 23:23
Thanks for the tip Tim!
Ill try tomorrow and see if it makes a difference, cant test on Vista, but will try on my Windows 7 machine.
25 Juni 2010 22:55I also experienced same problem playing with different combinations of Win2008 and Win2003. I was getting blank "Add Scope" section in the output of "netsh dhcp server <IP_Addr> dump" command if I executed this command on Win2008 with directing the request to Win2003 server. Same result if the command executed on Win2008R2 and directed to non-Win2008R2 srever.
02 Juli 2010 19:16I have the same issue, New build of Windows 7 no Add scope section in the dump, but I can create a new scope if I replay an existing dump file, any further thoughts?
24 Nopember 2010 9:36
No real movement here at all :( My work around was to just have my tool run from a 2008 box for collection. This worked fine as all my dhcp servers were moved to 2008, however my collection server crashed. I rebuilt this with Server 2008 R2 and yet again the exact same issue is happening. I need to go digging through my files as it has been months since I have opened up a premier case so I need to find my number, however I think that is going to be the ONLY way to get MS to answer this question.
I have tried to install the RSAT tools like suggested above, however I get "Update not Valid" for my 2008 R2 system. Looks like back to square 1!
24 Nopember 2010 14:06
I made a couple more tests today for this:
1. Installed DHCP Server on 2008 R2
2. Created a Test scope on 2008 R2 - left in disabled state
3. Query from 2008 R2 DHCP server --> 2008 DHCP server and I can NOT see any scopes in the DUMP file
4. Query from 2008 DHCP server --> 2008 R2 DHCP server and I CAN see the scopes in the DUMP file
5. Query the DHCP 2008 R2 server to look at local scopes. 2008 R2 CAN NOT see it's own scopes
Seems that the issue is even getting worste if you can not even create backups of your scopes via NETSH from the same DHCP server....
01 Desember 2010 13:48
Just wanted to give an update on this. I opened up a premier support case with MS for this issue. They were able to replicate the issue and determined that this is a bug, however they will NOT look at fixing this without a strong business case which I could not provide. They know that Server 2003 and Windows XP worked fine to querying systems below and above there OS level however they are fine leaving NETSH only being able to now query it's own OS Level.
to make a long story short MS knows this is an issue and dont care.
18 April 2012 19:48
I realize this topic is old, but this problem does still exist. Seems the only workaround I've found is using PsExec.exe from W7/2008/R2 to execute a ./PsExec.exe "\\RemoteServer" netsh dhcp server \\RemoteServer dump. In the PS script I'm using, I simply test for the local or remote machine version; if it's W7/2008/R2/etc attempting netsh dump on a remote Win 2003 machine, it will have to call PsExec.exe (stored somewhere local).
It is more inconvenient to depend on the PsExec utility, but once we're migrated to 2008, it shouldn't matter. They really should have fixed this, though. Hope this helps someone.
06 Desember 2012 8:03
For me the solution was to run the cmd.exe as Administrator.
If you just open it and type "netsh dhcp server <ip address> dump >c:\dhcp.txt" it creates file like this:
# Configuration Information for Server <ip>
# Add Classes
But from the elevated command prompt it works ok.
- Disarankan sebagai Jawaban oleh Igor Vyunov 06 Desember 2012 8:06