W2003 vs. inet vs. inets ?

Robert Raschke <>
Thu Jul 16 20:21:29 CEST 2009


Hi,

I've come across a weird issue with the last R12B release (erts 5.6.5)
running on Windows 2003 Server.

When I start my node (long or short name makes no difference) I can find out
about my IP address. But when I start inets and fire off an http request
(which for a currently unknown reason times out), then I am no longer able
to find my IP address:

()1> inet:getaddr("localhost", inet).
{ok,{127,0,0,1}}
()2> inet:getaddr("vm-153013-2", inet).
{ok,{172,16,3,32}}
()3> inets:start().
ok
()4> inet:getaddr("localhost", inet).
{ok,{127,0,0,1}}
()5> inet:getaddr("vm-153013-2", inet).
{ok,{172,16,3,32}}
()6> http:request("http://www.google.com").
{error,timeout}
()7> inet:getaddr("localhost", inet).
{error,timeout}
()8> inet:getaddr("vm-153013-2", inet).
{error,timeout}
()9>

Has anyone seen something like this? And where would I start hunting?
(I'll try R13 tomorrow.)

Thanks for any pointers,
Robby


More information about the erlang-questions mailing list