[Vm-dev] Fwd: [Pharo-project] Show stopper network bug on Windows

[Igor Stasenko]

Hello guys, those, who not subscribed to the Pharo list.

I think you should read this:
  http://code.google.com/p/pharo/issues/detail?id=961

since it seems there are some networking problems with Win32 VM.


---------- Forwarded message ----------
From: Igor Stasenko <siguctua at gmail.com>
Date: 2009/7/22
Subject: Re: [Pharo-project] Show stopper network bug on Windows
To: Pharo-project at lists.gforge.inria.fr


2009/7/22 Schwab,Wilhelm K <bschwab at anest.ufl.edu>:
>
> The lack of fully qualified names could easily be a windows stupidity.  My Dolphin code for lookups has long been a little complicated: look up this, clear that, do it again, and it always seemed that I was fighting lack of imagination from the general direction of Redmond WA - who would have thought that possible? :)  My favorite was win2k from (IIRC) pre-sp3: the only machine one could not find by name was the local host!
>

Concerning fully qualified host name. Yes. This is a well-known issue
of windoze.
For instance, my machine returns 'comp'
on #localHostName request. Which is nothing more, than a computer
name, i assigned in windoze settings.

I didn't assigned my PC to be a part of any (sub)domain, so this is
all it can report.

The problems with dns/windoze host naming is comes back to Windows
3.11 era when there was no 'internet' but a local networks and windows
used own identification mechanisms and protocols (NetBIOS, NetBEUI) to
connect different hosts into a 'workgroup' :)

However, next is getting interesting.
I having a following network interfaces on my PC (i have to translate
the text, because it prints things in russian) :

(( The engineers at Redmond renamed the well-known unix ifconfig
utility to ipconfig :) ))

C:\>ipconfig /all

Windows IP protocol settings
       Host name  . . . . . . . . . : comp
       Primary DNS-suffix  . . . . . . :
       Host type . . . . . . . . . . . . . : unknown
       IP-forwarding enabled  . . . . : no
       WINS-proxy enabled . . . . . . . : no

VMware Network Adapter VMnet8 - Ethernet adapter:

       DNS-suffix . . :
       IP-address  . . . . . . . . . . . . : 192.168.6.1
       Subnet mask . . . . . . . . . . : 255.255.255.0
       Gateway . . . . . . . . . . :

VMware Network Adapter VMnet1 - Ethernet adapter:

       DNS-suffix . . :
       IP-address  . . . . . . . . . . . . : 192.168.89.1
       Subnet mask . . . . . . . . . . : 255.255.255.0
       Gateway  . . . . . . . . . . :

VirtualBox Host-Only Network - Ethernet adapter:

       DNS-suffix . . :
       IP-address  . . . . . . . . . . . . : 192.168.56.1
       Subnet mask . . . . . . . . . . : 255.255.255.0
       Gateway  . . . . . . . . . . :

Network bridge - Ethernet adapter:

       DNS-suffix . . :
       IP-address  . . . . . . . . . . . . : 192.168.0.3
       Subnet mask . . . . . . . . . . : 255.255.255.0
       Gateway  . . . . . . . . . . : 192.168.0.1


Now, if i run:
C:\>ping comp

it starts pinging 192.168.56.1  address, which its thinks my
extenal/local adapter address, but its obviously not

i would expect that 'comp' should be resolved to 127.0.0.1 address (a
loopback adapter) but windows thinks differently :)

So, imagine i want to create a socket , listening for incoming
connections at 'localHostName' address:

NetNameResolver addressForName: NetNameResolver localHostName

it gives me the same result  as ping does:
192.168.56.1(192.168.56.1),0(0)

surely, using this address i will never receive any incoming connections.. :)

But what i didn't expected, it also opens a debug console and prints
some kind of error about getnameinfo() function
(again, translated, because my windoze is localized):

getnameinfo: requested name is allowed and its found in database, but
for this name the associated data is missing, which was allowed for
it..

But its not producing a primitive failure.

btw, same error shown in concole even if i do:

NetNameResolver addressForName: 'localhost'

i found that the error producing when i printing the instance of
SocketAddress (#hostName method)

weird...

Next, nslookup utility of course, unable to resolve 'comp' name:

C:\>nslookup
Default Server:  ns.ip.net.ua
Address:  82.193.96.6

> comp
Server:  ns.ip.net.ua
Address:  82.193.96.6

*** ns.ip.net.ua can't find comp: Non-existent domain
>

--
Best regards,
Igor Stasenko AKA sig.