Sage installation on windows : browser cannot connect

[Matthias L]

Dear group,

I've tried to install Sage on Windows 7 following the installation guide linked below. It seems to work until step 4, I get the same console window as shown in the screen shot there ("Open your web browser"). But if I do so, I can't connect to Sage and receive a 404 error instead.

Installation guide
http://wiki.sagemath.org/SageAppliance

Virtual Box 4.1.10, Sage 4.8

Some ideas?

Thank you, Matthias

[Jean-Pierre Flori]

I think I had the same problem although the VirtualBox port forwarding was correctly configured and I could not resolve it in the little time I had.
My late conclusion was that maybe the Windows firewall is blocking the connection (even though it's a local one...) ?
Could you try connecting to the Sage notebook after disabling the firewall ?
It's not a proper solution but my give us some hint.

The other solution is to wait for a Sage in VirtualBox on Windows :)

[Matthias L]

I've tried, but the firewall settings don't have any influence, and also the port forwarding should be correctly configured.

[Maarten Derickx]

Actually the 404 error sais that you alreade got past the firewall and have reached the server so the trouble should be somewhere else indeed.

Does the 404 error say more (i.e. does it say what is not found?). A screenshot might be usefull.

p.s. I assume that you don't already have your own webserver running on localhost:8000 ;)

[emil]

Maybe you try to change the "network settings" of Virtual Box from "NAT" to "Bridged Adapter". Your VirtualBox session will get an ip adress like any other machine on the LAN.

Then you connect to the sage notebook with http://ip-adress:8000

 

[Volker Braun]

Does http://127.0.0.1:8000 work?

You are either running a web server on localhost:8000 already or your system is resolving localhost to a non-local ip. In the latter case you probably have a spyware/virus problem. Since you'll have to reinstall, why not try Linux? ;-)

On Thursday, March 29, 2012 1:03:30 PM UTC+1, emil wrote:

Maybe you try to change the "network settings" of Virtual Box from "NAT" to "Bridged Adapter". Your VirtualBox session will get an ip adress like any other machine on the LAN.

Don't do that unless you are aware of the security implications. In any case it won't help with your problem.

[Matthias L]

No, http://127.0.0.1:8000 doesn't work either ... as far as I know I'm not running a a web server ... maybe I should run a virus check instead...

[Volker Braun]

When you get the 404 error, there is usually some fine print about which server replied with the error. Maybe that'll give you some hint of what is going on.

[Robert]

I also am stuck, but my problem is a Virtualbox problem. I have Sage-4.8 running, but I don't know how to see it from another computer. If I have it to NAT I can see the notebook on my PC. If I make it bridged, what is the IP address I'd use? If it were local I'd use http://localhost:8000. My machine has a fixed IP. Do I use aaa.bbb.ccc.ddd:8000? That isn't working for me. Do you have any suggestions?

[Volker Braun]

If you set the networking to bridged the IP address of the virtual machine will be determined by dhcp. If you don't have a dhcp server, it will not set up networking.

[Robert Blanchette]

OK. So if my Windows machine isn't also a DHCP server for the Sage Virtualbox, there will be nothing. Good to know. Thanks!

--
To post to this group, send email to sage-s...@googlegroups.com
To unsubscribe from this group, send email to sage-support...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-support
URL: http://www.sagemath.org

--
Robert Blanchette
robert.bl...@gmail.com
@TeamGeofrog

[Volker Braun]

Yes, except that any machine on the LAN can act as a dhcp server. Not just the VM host.

On Tuesday, April 17, 2012 2:45:05 PM UTC-4, Robert wrote:

OK. So if my Windows machine isn't also a DHCP server for the Sage Virtualbox, there will be nothing. Good to know. Thanks!

On Tue, Apr 17, 2012 at 2:40 PM, Volker Braun <vbrau...@gmail.com> wrote:

If you set the networking to bridged the IP address of the virtual machine will be determined by dhcp. If you don't have a dhcp server, it will not set up networking.

On Tuesday, April 17, 2012 2:30:04 PM UTC-4, Robert wrote:

On Wednesday, March 28, 2012 9:06:31 AM UTC-4, Matthias L wrote:
> Dear group,
>
> I've tried to install Sage on Windows 7 following the installation guide linked below. It seems to work until step 4, I get the same console window as shown in the screen shot there ("Open your web browser"). But if I do so, I can't connect to Sage and receive a 404 error instead.
>
> Installation guide
> http://wiki.sagemath.org/SageAppliance
>
> Virtual Box 4.1.10, Sage 4.8
>
> Some ideas?
>
> Thank you, Matthias

I also am stuck, but my problem is a Virtualbox problem. I have Sage-4.8 running, but I don't know how to see it from another computer. If I have it to NAT I can see the notebook on my PC. If I make it bridged, what is the IP address I'd use? If it were local I'd use http://localhost:8000. My machine has a fixed IP. Do I use aaa.bbb.ccc.ddd:8000? That isn't working for me. Do you have any suggestions?

--
To post to this group, send email to sage-s...@googlegroups.com

To unsubscribe from this group, send email to sage-support+unsubscribe@googlegroups.com

For more options, visit this group at http://groups.google.com/group/sage-support
URL: http://www.sagemath.org

[Jean-Pierre Flori]

There is some Sage meeting this afternoon in Paris.
I have a Windows 7 installation on my laptop, I'll give a VirtualBox installation a try, maybe I'll be more lucky than last time.
That was particularly painful to have people ready to try Sage on their computer at a previous meeting, but being unable to connect to the Sage notebook server running inside the virtual machine.

By the way, I have had no problems running a notebook server within a VirtualBox virtual machine on a Debian guest, and having a dozen of students connecting to it from distant hosts...

[emil]

 > If I make it bridged, what is the IP address I'd use?

stop the sage notebook server (with Ctr-C) and type "ifconfig". This should show you your IP address on the network.

It should also show in the startup message of the notebook server.

[Jean-Pierre Flori]

Today at some Sage meeting in Paris, we encountered this problem once more with Sage 4.7.2 vbox image within Windows 7.
The image was correctly (or seemingly correctly) preconfigured with 8000 on the outside pointing toward 8000 on the inside and 2222 into 22.

Once more it was possible to ssh from the outside into the inside (using putty and port 2222 as expected).
Nonetheless accessing localhost:8000 or 127.0.0.1:8000 gave a "Not found" error.

After some random stupid ideas, changing the port forwarding of Virtualbox to redirect 8888 (a random good looking number which has no special reason to be in use or forbidden) from the outside to 8000 inside the virtual machine solved the problem!
Don't ask me why Windows 7 does not like the 8000 port... nor why it preferred the 8888 one.

On Wednesday, March 28, 2012 3:06:31 PM UTC+2, Matthias L wrote:

[Jean-Pierre Flori]

And I think that the port 8000 was dysfunctional because some service already listened on that port (I don't have the computer at hand anymore so cannot check...)
as suggested by this result from a simple google query:
http://superuser.com/questions/360236/why-is-system-listening-on-port-8000

On Wednesday, March 28, 2012 3:06:31 PM UTC+2, Matthias L wrote:

On Wednesday, March 28, 2012 3:06:31 PM UTC+2, Matthias L wrote:

[Volker Braun]

On Wednesday, May 9, 2012 10:33:22 AM UTC-4, Jean-Pierre Flori wrote:

http://superuser.com/questions/360236/why-is-system-listening-on-port-8000

My money is on the following answer posted on the above ask page: "There are a few trojans / backdoors that use 8000, so perhaps booting an Antivirus disk and doing a full scan would be a good idea."

If you can't figure out what is binding port 8000 then you should take your zombie offline before it sends out more spam.

[Jean-Pierre Flori]

You could also be too lazy to learn how to check what is listening on which port in Windows and also have a legitimate program that is already listening to that port...

For example some maintenance software from your laptop vendor (as the Sony VAIO stuff mentioned on the same page).

In fact I would put my money on this because I had the same behavior on my laptop a long time ago and have little chance to have any trojan or malicious stuff on it because the first thing I used to do when I booted into windows was to update it and I never installed anything exotic except for VLC.
And I definitely had a bunch of Lenovo crappy software installed by default and which would do plenty of stuff I was not even aware of.
You could argue that such software is actually malware.