Notes |
(0000468 - 162 - 162 - 162 - 162 - 162 - 162)
andreas
10-19-04 03:10
|
Anyone able to reproduce this? We might have fixed this in the meantime so I'd be very interested to hear if you've seen this problem earlier but not lately. - ar |
|
(0000495 - 187 - 187 - 187 - 187 - 187 - 187)
smdesai
10-20-04 19:34
|
I still get traceback messages. I've uploaded the SqueakDebug and a snapshot of the error. The connection was attempted between two PCs running on the same subnet with the latest updates. |
|
(0001546 - 424 - 448 - 448 - 448 - 448 - 448)
dgd
05-30-05 13:40
|
In my linux box I get exactly the same error. The problem is that 'NetNameResolver localHostAddress' answers 127.0.0.1 in some configurations.
The actual asumption, in NetNameResolver and SocketPlugin, of gaving one and only one ip address per machine is wrong.
I didn't find the way to look for all the ip address for a machine, so a simply hack is goind to save us: Just ask the user for the IP in these bugy cases. |
|
(0001547 - 57 - 57 - 57 - 57 - 57 - 57)
dgd
05-30-05 13:42
|
I just attached one simply changeset containing the hack. |
|