Reply To: WDM Scheduled packages never deploy

#22214
Avatarpufthemajicdragon
Member
  • Total Post: 11
  • Regular Joe
  • ★★

I changed the bindings in IIS for http and ftp to only bind the public interface – didn’t work. I did use MDTools 3.0 to edit the database table “Servers” and found a few entries with the wrong address – editing these manually, saving, and rebooting got the right IP addresses to show up in the diagnostic, but hServer is still showing as failed in the diagnostic.


Software Repository Information
Started 5/2/2012 11:16:40 AM...
Status Name Path Protocol Status
CONNECTED MASTER 192.168.102.175 FTP Connection to the repository succeeded.



HServer Information
Started 5/2/2012 11:16:40 AM...
Status Server Port Checked In Checked Out Response
FAIL 192.168.102.175 80 5/2/2012 8:05:52 AM Could not connect



Standard Service Information
Status Server Port Checked In Checked Out
CONNECTED 192.168.102.175 8008 5/2/2012 9:16:32 AM

If I visit the URL in IE http://vwmgr/hserver.dll?&V99 it works fine, returns the time stamp. If i view it by IP http://192.168.102.175/hserver.dll?&V99 it fails – not found. DNS returns the proper IP address when I ping the hostname.

So anywho, if this is binding order, how do I change the binding order for WDM?

:EDIT:
I’ve also disabled the second NIC in Windows, so it’s not even active now.

:EDIT2:
I had set hostnames in IIS as part of troubleshooting – removing those gets the IP to work now, so the diagnostic page comes up green all over. But my package is still not rolling out, and if I try to pull diagnostic information from the client, it returns: &00|