Did anyone try using Andreas's new Windows VM? It may fix this. If not, this problem should be sent to the Squeak development list, where more low level Squeak expertise is available.
Peace and Luck! Je77 On Mon, Feb 25, 2002 at 02:07:54PM -0000, Bill at GLO Ltd wrote: > Hi > > I'm sure the problem is the following > > in Visual Works I can explicitly set the socket address ... > > sa := IPSocketAddress hostAddress: (IPSocketAddress hostAddressByName: > 'BILLSMACHINE') port: 5678. > skt bindTo: sa. > > ... and I can see using a network monitor utility a socket listenting on > 5678 with a > local ip of 192.168.0.1 and this is accessible over the network. > > In squeak if I do ... > > Socket initializeNetwork. > (Socket newTCP) listenOn: 5678. > > ... I see a socket listening on 5678 with a local ip of 0.0.0.0 and this is > not > accessible over the network, but it it accessible on the local machine. > > There must be some configuration or something in squeak so that it uses the > right local ip when it makes a socket. > > In squeak ... > NetNameResolver localHostAddress ... gives ByteArray(192 168 0 1). > so that is not the problem. > > Regards > > Bill > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf > Of Frank Sergeant > Sent: Monday, February 25, 2002 5:34 AM > To: [EMAIL PROTECTED] > Subject: RE: [pws] problem running swiki on nt > > > "Bill at GLO Ltd" <[EMAIL PROTECTED]> wrote: > > The network is running with an ADSL link and fixed ip's. > > > > We have got a fire wall running , but it is configured to allow port 80 > > Apache works fine on the same machine. > > Ok. Fixed IPs on your internal machines, such as 192.168.1.10, > 192.168.1.20, and so forth? So, let's say you have your web server (ie > Swiki) running on 192.168.1.10 (an NT machine) on port 80. From that > same machine, you can access the Swiki via MSIE as http://localhost, > right? But, you go to another machine on your internal network, say > 192.168.1.20 and try http://192.168.1.10 and you cannot reach the Swiki? > If that is the case, try to ping the first machine from the second > (open a DOS box on ....20 and type 'ping 192.168.1.10') -- does that > work? There should be 'route print' and 'net' commands available in a > DOS box in case they shed any further light on things. > > Or, is it that you can reach the Swiki just fine from the other machines > in your internal network but outside machines cannot reach it? > > I had been running the latest Swiki ("Harvest") on my Windows 2000 > machine with no trouble connecting to it from another machine on my > internal network. I didn't have to do anything to the Swiki to > configure the port other than click on the right-hand button and choose > the port. I felt that WNT and W2K were similar enough that it is likely > that your setup should work about the same as mine. I currently have a > 3-machine network where one machine is 192.168.1.40 and another is > 192.168.1.10 and the firewall, running the floppy-based "Dachstein" with > PPPoE, is on 192.168.1.30. I do not use DHCP. > > I have recently switched the 192.168.1.10 machine to run Linux more or > less permanently and am now running the Swiki on that machine. I have > no trouble reaching it from internal or external machines. > > > I did try it on ports 8080 and 8888 > > but get the same results. I have tried this on two NT machines at > different > > sites, unfortunately I don't have access to any other Windows systems to > > try. > > If you can think of something I can help with, such as trying to connect > to your Swiki from an external machine, just let me know (posted or > emailed, whichever you prefer). > > > Is there anyway to tell Squeak what the local ip is ? > > I imagine 'Socket initializeNetwork' does everything necessary? > > > -- Frank
