ejabberd on Win2003 unable to make outgoing s2s connection - not even bothering to look up hosts?

Hi All,

Just ran into a very odd problem with a fresh install of 2.1.2 on windows server 2003.

On an XP box making an outgoing s2s looks like this: (hostnames x'ed out)

=INFO REPORT==== 2010-01-20 13:20:30 ===
I(<0.373.0>:ejabberd_s2s_out:1142) : Trying to open s2s connection: ws-xxxxx -> xxxxx-wiq

=INFO REPORT==== 2010-01-20 13:20:30 ===
D(<0.373.0>:ejabberd_s2s_out:195) : open_socket: {"ws-xxxxx",
                                                  "xxxxx-wiq","1841853697",
                                                  false}

=ERROR REPORT==== 2010-01-20 13:20:30 ===
E(<0.373.0>:ejabberd_s2s_out:1060) : The DNS servers
  []
timed out on request for "xxxxx-wiq" IN SRV. You should check your DNS configuration.

=ERROR REPORT==== 2010-01-20 13:20:30 ===
E(<0.373.0>:ejabberd_s2s_out:1060) : The DNS servers
  []
timed out on request for "xxxxx-wiq" IN SRV. You should check your DNS configuration.

=INFO REPORT==== 2010-01-20 13:20:30 ===
D(<0.373.0>:ejabberd_s2s_out:1006) : srv lookup of 'xxxxx-wiq' failed: timeout


=INFO REPORT==== 2010-01-20 13:20:30 ===
D(<0.373.0>:ejabberd_s2s_out:1091) : inet of xxxxx-wiq resolved to: [{172,
                                                                         22,
                                                                         28,
                                                                         1}]


=INFO REPORT==== 2010-01-20 13:20:30 ===
D(<0.373.0>:ejabberd_s2s_out:266) : s2s_out: connecting to {172,22,28,1}:5269

..which is fine: The DNS server doesn't have it, so it looks in the hosts file and resolves the name.

But on the windows 2003 install this happens:

=INFO REPORT==== 2010-01-20 13:44:32 ===
I(<0.373.0>:ejabberd_s2s_out:1142) : Trying to open s2s connection: ws-xxxxx -> xxxxx-wiq

=INFO REPORT==== 2010-01-20 13:44:32 ===
D(<0.373.0>:ejabberd_s2s_out:195) : open_socket: {"ws-xxxxx","xxxxx-wiq",
                                                  "612262113",false}

=INFO REPORT==== 2010-01-20 13:44:32 ===
I(<0.373.0>:ejabberd_s2s_out:227) : s2s connection: ws-xxxxx -> xxxxx-wiq (remote server not found)

In other words it just fails instantly. The remote host is correctly in the hosts file and can be pinged or telnetted into on 5269.

Has anyone else run into this?