Now i have tried to disable the firewall at all and at least "nmap ipnumber" say that there's that machine.
But if i digit "nmap hostname" it give me "failed to resolve hostname/ip"
Maybe is some configuration of mine?
I have made the hostname and host zeroconf at the same name....

Making up a simple example:

2 hosts on lan, 1 linux box called fred at 192.168.0.10 and 1 called george (Win or Lin, doesn't matter for this example) at 192.168.0.15, subnet mark 255.255.255.0, so both on same subnet.

Add to the linux box's /etc/hosts file the line 192.168.0.15 george (or 192.168.0.15 george.fullyqualifieddomainname george if you have a dns domain).

Now you should be able to ping george from the linux box and find george.

I think that "fish://..." and maybe "smb://..." will depend on host resolution. However, I think that lisa is supposed to find other hosts on the network by actively looking, so there may be other issues as well.

After a fresh install of mdk 9.2 in another pc i have at least resolved a thing.
Now i use the default configuration of lisa and if i write lan:/ i have lan://localhost/192.168.x.x and that's the router!
The strange thing is that the other pc now i see it...but with smb:// but it's not a win pc!
Hehe i think i'm near....and i think i screwed up some lisa configuration.
Like you say (i'm really really bad to network related problems...)i think its something related to hostnames....
Tomorrow after work i try various config and tell you the result.
For now i thank you for the patience

I have tried to disable at all the mandrake firewall and write the file /etc/hosts with the ip number and hostname of my pc.
If i write in konqueror lan:/"nomehost" now i see the host but with some filesystem i can't connect...the only one seems samba and fish (that share the whole pc...);and if i enter in my pc i see my shared folder but only with the samba protocol!
I have made some mistake elsewhere??(i think so)
If it's the firewall that block anything how can i use my lan without disable the firewall?(i think enabling some ports...but don't know why and if they are secure ouside my pc...)

of your setup might help people to see clearly what the issue is. I think I follow what you're saying, but I'm not certain.

Try posting something more detailed and specific like "my router is at 192.168.1.1, host apple (Mandrake) is at 192.168.1.11, s/n mask 255.255.255.0, host pear is a WinXP box at 192...", and so on.

You can make up the host names if you don't want to reveal details...as long as it accurately represents the network.

Then post /etc/hosts, exactly what was type in Konqueror, and the specific result.

One thing: a windows share will be seen with "smb://..", not with "fish://..". The fish protocol is for hosts running ssh, smb for Windows hosts or Samba servers using the smb/cifs protocol.

Gotta get a few things done and get to bed...I'll try to check back sometime tomorrow.

Ok heres the spec(masked ...but i think it's only for test)
My router is at 192.168.10.1
The win98 host Laura is at 192.168.10.3
The mandrake 9.2 host Turtle is at 192.168.10.2
And this pc,mandrake 9.1 host,Cow is at 192.168.10.4
All these host have the same subnet mask 255.255.155.0
My /etc/host file is:
127.0.0.1 localhost
192.168.10.2 Turtle
192.168.10.3 Laura
192.168.10.4 cow

So this same file is equal to /etc/host-allow and on /etc/host-deny is empty
The pc in some manner communicate (the smb protocol used by linneigborhood works...actually i use linneigborhood to share files under all the machine...so it's not a problem of subnetmask or similar....).

sometimes weekends are better for me .

So, given your last post, if you ought from Turtle to be able to "ssh Cow" or "ssh 192.168.10.4" and get to Cow. Same thing if you're at Cow: "ssh Turtle or "ssh 192.168.10.2" should get you there. If that works then "fish://..." in Konqueror should work. If not, check if the ssh daemon is running (sorry if I repeat something from earlier in the thread, it's late and I'm hurrying). From a shell "ps -ef|grep sshd" should show at least a line with /usr/sbin/sshd or similar. If not, /etc/init.d/sshd start probably would do the trick.

If ssh is running and you can't ssh to the box then either your router (as you suggested) or (more likely) the iptables firewall on the box needs to be adjusted. Most routers I don't think will block internal (LAN side) traffic, only traffic from the internet side. Probably checking whatever tools Mandrake has for adjusting the boxes' firewalls will do the trick if you can't ssh.

Sounds like from your comment about lin neighborhood the smb sharing is working. But does the smb share now show up in "lan:/" in Konqueror. You do realize that you'll only have ssh/fish to the Mandrake boxes unless you've setup Samba on them?

In general I have a better idea of your network, maybe post back if you can get ssh/fish to work and, if so, what you can then see in "lan:/".

I tend to not turn on the firewall on my internal machines. I use port forwarding on my router to forward the few ports I let through from the internet and any one services running inside I want to be available to the machines on my local network.

HTH.

if i disable the firewall i can ssh fish smb and all the stuff i think....
But i don't want to disable firewall 'cause i have my work files :P (i have a router that do firewall....but i want a firewall in my linux box also!)...so i don't know what port to open and if they are secure.....i want them only on my lan and not in internet.

The file /etc/services usually has all the ports listed.

Thanks!
Do you know where i can obtain information if these ports are secure or not?
Some sort of "book of permitted ports over a network"....

The ports are secure if the server that is running on them is secure. For instance if you are running openssh then you would keep an eye out for any openssh related bullitins. And if you are running samba you should keep samba up to date and always install the security related patches and updates.

If you are running only on a lan then you should set your firewall to only open the ports for IP's you expect to see on the lan.

There are many other security issues you should familiarize yourself with in time, but those basic steps will get you started. And of course read the documentation for any server you decide to run on your lan.

are not open to the internet. /bin/bash has given you some good pointers about ports (if you don't like to read /etc/services then try a Google search for common ports).

In summary, forward with the router's firewall only those ports that you want to be accessible from the internet. The rest are not a problem UNLESS someone cracks one of the boxes on your private network. Even if they do, there's not a problem that a firewall can address if you don't have a service listening on the port. Turn off services that you don't want; blocking with a firewall those that you do want running makes them inaccessible and makes no sense.

If you don't trust your router's firewall then you can also turn on the individual boxes' firewalls and allow only local traffic to the ports that you want open. It's just a matter of finding out what ports the services you want to run need to have open.

Ok i think i have to read many web-pages
Thanks,now i know that i block all my service with the firewall...and the bad configuration of the services makes the rest.