Local Network - Localhost not Found
If I attempt to browse my local network in the Konqueror file manager (tree: K -> Home Directory -> Network -> Local Network), I get a popup which says "Could not connect to localhost." I have checked the SuSE references, but nothing seems to address this issue, or related topics. Anyone know why this is occurring? -- burns
On 6 Oct 2001, burns wrote:
If I attempt to browse my local network in the Konqueror file manager (tree: K -> Home Directory -> Network -> Local Network), I get a popup which says "Could not connect to localhost."
I have checked the SuSE references, but nothing seems to address this issue, or related topics. Anyone know why this is occurring?
What kind of network are you talking about here? NFS, SMB, etc. What's the server and its IP? -- noodlez: Karol Pietrzak PGP KeyID: 0x3A1446A0
I've experienced this too. You can "fix" this by using the host name (See sysadmin, network setup, change host name in Yast) and asking for pages on http://hostname.local/ instead of http://localhost/ I don't know why this happens, but it doesn't happen consistently and seems related to the way you connect to your ISP. If you connect on initialisation or don't connect at all localhost seems to work always. If, like me, you don't have two 'phone lines and use kppp (or wvdial) to connect as needed, the localhost problem emerges occasionally. JDL burns wrote:
If I attempt to browse my local network in the Konqueror file manager (tree: K -> Home Directory -> Network -> Local Network), I get a popup which says "Could not connect to localhost."
I have checked the SuSE references, but nothing seems to address this issue, or related topics. Anyone know why this is occurring? -- burns
There's an easier way - in /etc/hosts, add a line for localhost. Here's what I have; # /etc/hosts 127.0.0.1 localhost localhost.localnet # local loop back interface 192.168.1.1 xena xena.localnet # primary workstation 192.168.1.10 peewee peewee.localnet # wife's Winblows notebook 192.168.1.100 evilware-2 evilware-2.localnet # Winblows machine for pda/mp3 192.168.1.250 slave slave.localnet # the main server 192.168.1.254 gateway gateway.localnet # the modem server / firewall machine # end /etc/hosts This works fine and has since version 6.1. Jon
I've experienced this too. You can "fix" this by using the host name (See sysadmin, network setup, change host name in Yast) and asking for pages on http://hostname.local/ instead of http://localhost/
I don't know why this happens, but it doesn't happen consistently and seems related to the way you connect to your ISP. If you connect on initialisation or don't connect at all localhost seems to work always. If, like me, you don't have two 'phone lines and use kppp (or wvdial) to connect as needed, the localhost problem emerges occasionally.
JDL
burns wrote:
If I attempt to browse my local network in the Konqueror file manager (tree: K -> Home Directory -> Network -> Local Network), I get a popup which says "Could not connect to localhost."
I have checked the SuSE references, but nothing seems to address this issue, or related topics. Anyone know why this is occurring? -- burns
On October 7, 2001 04:39 am, Jon Biddell wrote:
There's an easier way - in /etc/hosts, add a line for localhost. Here's what I have;
# /etc/hosts
127.0.0.1 localhost localhost.localnet # local loop back interface 192.168.1.1 xena xena.localnet # primary workstation 192.168.1.10 peewee peewee.localnet # wife's Winblows notebook 192.168.1.100 evilware-2 evilware-2.localnet # Winblows machine for pda/mp3 192.168.1.250 slave slave.localnet # the main server 192.168.1.254 gateway gateway.localnet # the modem server / firewall machine
# end /etc/hosts
This works fine and has since version 6.1.
Thanks Jon. I am running SuSE 7.2 Pro My /etc/hosts file looks somewhat different than yours and somewhat different than I am used to. It uses IPv6: # special IPv6 addresses 127.0.0.1 localhost 192.168.1.3 CR792449-A.slnt1.on.wave.home.com CR792449-A ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts -- burns
On October 7, 2001 04:20 am, John D Lamb wrote:
I've experienced this too. You can "fix" this by using the host name (See sysadmin, network setup, change host name in Yast) and asking for pages on http://hostname.local/ instead of http://localhost/
I don't know why this happens, but it doesn't happen consistently and seems related to the way you connect to your ISP. If you connect on initialisation or don't connect at all localhost seems to work always. If, like me, you don't have two 'phone lines and use kppp (or wvdial) to connect as needed, the localhost problem emerges occasionally.
Thanks John, I'll play around with that, as well, and see if it makes a difference. Iam connected continuously via broadband cable through my gateway and a in-home class C subnet. Again, 'Ta' -- burns
Hi, as noted a few weeks ago, when someone else asked this: You need to start LISA for the konqueror and LAN dig around and find /opt/kde2/share/apps/lisa/README and go through that I found that I had to log in as root in order to start it up with the command lisa -K I might have also had to create the (ie copy from the readme file) the basic config file and put it in the right place for lisa to find. Then I could browse the network between linux and windows boxes, with the former showing up where I'd put in samba shares.On Sunday 07 October 2001 01:16, you wrote:
If I attempt to browse my local network in the Konqueror file manager (tree: K -> Home Directory -> Network -> Local Network), I get a popup which says "Could not connect to localhost."
I have checked the SuSE references, but nothing seems to address this issue, or related topics. Anyone know why this is occurring?
-- Cheers Bruce
participants (5)
-
Bruce Scharlau -
burns -
John D Lamb -
Jon Biddell -
Karol Pietrzak