Hello,
we are using Active RMA to test remote Servers. Since we migrated some servers from W2K3 to W2K8 the only test that does not work after that is DHCP. Any hints what we have to change?
Thanks,
Thomas
DHCP-test fails on W2K8
-
- Posts: 34
- Joined: Mon Oct 26, 2009 2:55 pm
- Location: Duisburg, GERMANY
We cannot reproduce the problem.
What version of HostMonitor, RMA do you use?
Windows? 32bit? 64bit? Service Pack?
What exactly means "does not work"? What is test status? Bad? No answer? Unknown?
Do you use "Request IP: current local IP" option for the test? or you request specific IP?
Are you checking Windows built-in DHCP server?
Regards
Alex
What version of HostMonitor, RMA do you use?
Windows? 32bit? 64bit? Service Pack?
What exactly means "does not work"? What is test status? Bad? No answer? Unknown?
Do you use "Request IP: current local IP" option for the test? or you request specific IP?
Are you checking Windows built-in DHCP server?
Regards
Alex
-
- Posts: 34
- Joined: Mon Oct 26, 2009 2:55 pm
- Location: Duisburg, GERMANY
Hello Alex,
We use HM 8.54 with Active RMA 4.03.
Server OS of managed server is W2K8 R2 Standard 32bit AND 64bit (RMA-Manager says: Windows NT 6.0 Build 6002 Service Pack 2). We keep the servers up to date with WSUS.
The test status is "No answer".
We use the following parameters:
- Host: IP-address of the server that has RMA installed
- Timeout: 5000 ms
- Request IP: <current local IP>
Yes, we are checking the integrated DHCP-server-role of W2K8.
Hope that helps...
Thomas
We use HM 8.54 with Active RMA 4.03.
Server OS of managed server is W2K8 R2 Standard 32bit AND 64bit (RMA-Manager says: Windows NT 6.0 Build 6002 Service Pack 2). We keep the servers up to date with WSUS.
The test status is "No answer".
We use the following parameters:
- Host: IP-address of the server that has RMA installed
- Timeout: 5000 ms
- Request IP: <current local IP>
Yes, we are checking the integrated DHCP-server-role of W2K8.
Hope that helps...
Thomas
We tried to change some option, result is the same - everything works fine on our systems.
Are you sure DHCP server works fine? DHCP service started?
Could you try the DHCPCheck.exe utility, available at our site: http://www.ks-soft.net/download/utils/dhcpcheck.zip
By default, this utility sends DHCPInform packet instead of DHCPREquest packet. Probably, it it will work in your enwironment.
You may use -host: parameter to specify the destination DHCP server (e.g -host:192.168.1.1 ). For instance:
dhcpcheck.exe -host:192.168.1.1
In this case utility will send the DHCPInform packet to the DHCP server.
Also you may specify certain MAC-address to be sent within DHCPInform packet using -clientMAC: parameter, e.g -clientMAC:00-13-20-70-B8-03
dhcpcheck.exe -host:192.168.1.1 -clientMAC:00-13-20-70-B8-03
To find out the MAC-address of the network card on your machine you may use "ipconfig /all" command
dhcpcheck.exe is designed for "Shell Script test method: http://www.ks-soft.net/hostmon.eng/mfra ... m#chkShell
Regards
Alex
Are you sure DHCP server works fine? DHCP service started?
Could you try the DHCPCheck.exe utility, available at our site: http://www.ks-soft.net/download/utils/dhcpcheck.zip
By default, this utility sends DHCPInform packet instead of DHCPREquest packet. Probably, it it will work in your enwironment.
You may use -host: parameter to specify the destination DHCP server (e.g -host:192.168.1.1 ). For instance:
dhcpcheck.exe -host:192.168.1.1
In this case utility will send the DHCPInform packet to the DHCP server.
Also you may specify certain MAC-address to be sent within DHCPInform packet using -clientMAC: parameter, e.g -clientMAC:00-13-20-70-B8-03
dhcpcheck.exe -host:192.168.1.1 -clientMAC:00-13-20-70-B8-03
To find out the MAC-address of the network card on your machine you may use "ipconfig /all" command
dhcpcheck.exe is designed for "Shell Script test method: http://www.ks-soft.net/hostmon.eng/mfra ... m#chkShell
Regards
Alex
-
- Posts: 34
- Joined: Mon Oct 26, 2009 2:55 pm
- Location: Duisburg, GERMANY
dhcpcheck.exe could not get any answer from the DHCP-server as well.
But there is one more thing we found out. The aRMA was running on a W2K3-machine. As we migrated all services from this old machine to the new (W2K8R2) one, we also moved aRMA. The new W2K8R2-machine has aRMA now and at the samne time is the DHCP-server we wanted to chek. Since both aRMA and DHCP ar eon the same machine it works!
I have no idea what could avoid DHCP-check to fail throught the ethernet. All clients get their IUPs from DHCP, so it must be available.
For now everything is ok at the moment, but it would be interesting to know what the problem is. Maybe you have any more ideas...
But there is one more thing we found out. The aRMA was running on a W2K3-machine. As we migrated all services from this old machine to the new (W2K8R2) one, we also moved aRMA. The new W2K8R2-machine has aRMA now and at the samne time is the DHCP-server we wanted to chek. Since both aRMA and DHCP ar eon the same machine it works!
I have no idea what could avoid DHCP-check to fail throught the ethernet. All clients get their IUPs from DHCP, so it must be available.
For now everything is ok at the moment, but it would be interesting to know what the problem is. Maybe you have any more ideas...
-
- Posts: 34
- Joined: Mon Oct 26, 2009 2:55 pm
- Location: Duisburg, GERMANY