Cannot even access 127.0.0.1

[Johan van Zyl]

I run my Server.exe on a small LAN but cannot access 127.0.0.1 from the server or any of the of the WS.

This web page is not available
The connection to 127.0.0.1 was interrupted.
Here are some suggestions:
Reload this web page later.
Check your Internet connection. Reboot any routers, modems or other network devices that you may be using.
Add Google Chrome as a permitted programme in your firewall or antivirus software's settings. If it is already a permitted programme, try deleting it from the list of permitted programmes and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure that the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the spanner menu > Options > Under the Bonnet > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.

[Koen Tjoa]

Hi Johan,

I am not sure if this is a question or a tip, but are you sure you didn’t forget to name the server in the URL when accessing it from a server. Something like \\<ServerName>\127.0.0.1

And maybe you need to add http:// before your URL. I experienced it was needed when using IE. Didn't figure out yet why.

Cheers,
Koen

[ccordes]

Unless you are running a server on port 80, just putting 127.0.0.1 in the address bar will return an error.
If you have iis or apache running, then you will get the default home page.
If you are running a Nettalk webserver, you will need to include the port number in the address that you assigned to your project.
I think the default is 89. Then http://127.0.0.1:89  will request a response from your server.

HTH
chris

[Johan van Zyl]

In my case it is 127.0.0.1:90, I tried that first - that gave the same error - then I tried 127.0.0.1 and even that does not work not on any WS or the Server itself.

[Koen Tjoa]

Try did same, but with http://, so that will be http://127.0.0.1:90
Or maybe http://localhost:90 will work, although it should not make a difference.

Regards,
Koen

[ccordes]

Johan
Are you in a browser on the same machine as your NT web server application?
You can also use the ip address of the machine where the application is running.

You can try stopping your firewall for a minute while you test.

[Bruce]

127.0.0.1 is the number for "this machine" . So it's guarenteed that you cannot access 127.0.0.1 from another machine on the lan (or another virtual manchine anywhere).

Use the Lan address (eg 192.168.2.45) to access the machine from another machine on the lan.

If you are not using port 80, then you will need to append :portnumber to the address.

If you are using Port 80 then make sure  no other program on the machine is using port 80.

On the server be sure to add the exe as an exception to the firewall software.

If nothing else works, turn on error reporting in the server to see if it's telling you anything useful.

cheers
Bruce

[Johan van Zyl]

Hi

OK I'm on my own PC(the "server"). I run the Server app - then 127.0.0.1:88 in browser and all is well I can see my Menus, Browses etc.

But I cannot get it to work on any other PC on the LAN (SBS)

What must I enter  in the browser of other PC's in the LAN to run the app as well?

Also 127.0.0.1:88?
Or \\ServerName:88
or whatever?

Must I add the Server.EXE in FireWall on my PC(the "server") only or on all participating PC's on LAN?
Must I open port 88 in Firewall on the "server" only or on all participating PC's on LAN?

[Bruce]

>> Also 127.0.0.1:88?

no, as I said;
127.0.0.1 is the number for "this machine" . So it's guarenteed that you cannot access 127.0.0.1 from another machine on the lan (or another virtual machine anywhere).

>> Or \\ServerName:88
no, that's not a valid address in your browser.
http://servername:88
will probably work. or
http://192.168.1.1:88
(substitute 192.168.1.1 with the actual IP address of the server).

>> Must I add the Server.EXE in FireWall on my PC(the "server") only

yes

>> Must I open port 88 in Firewall on the "server" only

yes.

cheers
Bruce