Re: [SLUG] nmblookup and Konquerer lan browsing

2002-01-13 Thread Malcolm V

On Sun, 2002-01-13 at 14:34, Christopher Booth wrote:
[...snipped...]
 NETWORK appears ...
Ahh, I tend not use that view in Konqueror, so I never noticed, thanks.
As an aside, you can add rlan:/ , smb:/ , etc to the bookmarks (and the
bookmarks toolbar).

 UpdatePeriod=300# Refresh period ?
This is the base refresh period, if no call is made to lisa/reslisa
 during this time it will double (up to four(?) times, so left alone it
will only update every 2400 seconds.

 
 My questions ?
 
 With my settings above, would a machine with X.Y.107.21 be allowed ? 
Yes, that should be shown.
X.Y.143.187?
No, by your config only X.Y.104-107.* would be checked. You should be
able to specify the IP range using this method, eg: X.Y.100-150.0-20
should be accepted by res/lisa.

 How much do lisarc and reslisarc rely on settings in smb.conf ?
I don't really know however I think it is only (partially) used for the SMB parts,
the FTP and HTTP parts are determined seperately.

 Should I put Wins Servers addresses in the line PingNames ?
PingNames is only used to specify address to check by name rather then
IP number, if you have already specified them in AllowedAddresses there
is no need to add them here again (err, well see below).
 
 In smb.conf there are two lines
 remote browse sync
 and
 remote announce
[...snipped...]
 Should remote browse sync be the ip address of the wins server ?
 Should remote announce be set to X.Y.107.255 ?

Correctly configuring your samba server is another whole kettle of fish,
but I don't think you need to change anything there to get res/lisa
working.

An example (untested) reslisa configuration file that should check
192.168.0.0 through to 192.168.25.255, as well as the single machine at
193.0.0.5 :

PingNames = # Not needed (see below) 
AllowedAddresses = 192.168.0-25.0-255;193.0.0.5
SearchUsingNmblookup = 1
FirstWait = 30  
SecondWait = -1 
UpdatePeriod = 300  
DeliverUnnamedHosts = 1 #also publish hosts without name
^^^ Does Your config have this line?
MaxPingsAtOnce = 256


I found res/lisa would not report a machine which could be pinged but
offered no services (eg no samba, no ftp, etc), even with
DeliverUnnamedHosts set to 1 it still failed to do this. However they
are reported if you specifically name them (although by IP only), so if
you wanted to able to use this to check your mailserver is still on the
network you could add mailserver.localnet to PingNames.


-- 
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug



Re: [SLUG] nmblookup and Konquerer lan browsing

2002-01-12 Thread Christopher Booth

Hi Malcolm
 [...snipped...]
 Where are you clicking on network?

NETWORK appears like network neighbourhood in Windows underneath the Folders etc... on 
the left hand side of konqueror
 
 This is an interesting feature. lan connects to lisa and rlan connects
 to reslisa. Lisa opens a port (7124 by default I think), reslisa does
 not do this. Lisa itself uses this port to talk to other lisa servers
 running on the network, and also the konqueror client uses it (so if you
 have lisa only running on machine homer and you are on machine marge,
 lan://localhost wont work, but lan://homer will).
 
 Reslisa does everything lisa does except it's output is taken from a
 specially created pipe(?) in /tmp, instead of a port. Rlan:/ connects
 konqueror to this pipe (so rlan only works on machines where reslisa is
 running locally).
 
 I'm not sure why some machines are not resolved to hostnames, my best
 guess is that those not found by nmblookup stay as numbers. All my
 machines are detected by reslisa and lisa, what does your
 reslisarc/lisarc file look like, particulary the PingNames,
 PingAddresses and AllowedAddresses fields?
 
KDE control panel has (on Mandrake) 2 configuration things for this, 
Under Configuration,KDE,network, there is Windows Shares and Lan Browsing
These update files 
/$HOME/.kde/share/config/kio_lanrc
/$HOME/.kde/share/config/lisarc
/$HOME/.kde/share/config/rlisarc

While looking for these lisarc and rlisarc files, I came across - 
/$HOME/.kde/share/apps/konqueror/dirtree/lan.desktop

it has a line which says URL=lan:/
which is the problem I changed that to URL=lan://localhost/localhost and it works by 
displaying the active network shares for my computer as defined in the KDE control 
center

I then changed it to read rlan:/

This then should display the machines on the network

Both lisarc and rlisarc, I have setup mostly the same (added comments here)

AllowedAddresses=X.Y.0.0/255.255.252.0  # local lan addresses and subnet mask
BroadcastNetwork=X.Y.107.255/255.255.252.0  # only in lisarc for range X.Y.105.30
FirstWait=99# time to wait for reply in 1/100 sec
MaxPingsAtOnce=256  # unexplained meaning
PingAddresses=X.Y.0.0/255.255.252.0 # only in lisarc -address range
PingNames=X.Y.104.121;X.Y.199.9.116;X.Y.10.45 # these are wins servers on the lan
SearchUsingNmblookup=1  # this is self explanatory
SecondWait=99   # as first wait
UpdatePeriod=300# Refresh period ?

My questions ?

With my settings above, would a machine with X.Y.107.21 be allowed ? X.Y.143.187?
How much do lisarc and reslisarc rely on settings in smb.conf ?
Should I put Wins Servers addresses in the line PingNames ?

In smb.conf there are two lines
remote browse sync
and
remote announce

In Windows Network Neighbourhood, the Domain is displayed, as the domain covers 
multiple sites, and ip ranges, eg.  X.Y.0.0-X.Y.?.? and X.Y.104.0-X.Y.107.255
They all see each other, no problem
What should my settings be in smb.conf ?
My IP is X.Y.105.30
Should remote browse sync be the ip address of the wins server ?
Should remote announce be set to X.Y.107.255 ?

Trying to get this happening

Chris

 I hope this helps more then it confuses.
It did help somewhat, thanks
-- 
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug



Re: [SLUG] nmblookup and Konquerer lan browsing

2002-01-11 Thread Malcolm V

On Fri, 2002-01-11 at 12:55, Christopher Booth wrote:
[...snipped...]
 Clicking on Network brings an error
[...snipped...]
Where are you clicking on network?

This is an interesting feature. lan connects to lisa and rlan connects
to reslisa. Lisa opens a port (7124 by default I think), reslisa does
not do this. Lisa itself uses this port to talk to other lisa servers
running on the network, and also the konqueror client uses it (so if you
have lisa only running on machine homer and you are on machine marge,
lan://localhost wont work, but lan://homer will).

Reslisa does everything lisa does except it's output is taken from a
specially created pipe(?) in /tmp, instead of a port. Rlan:/ connects
konqueror to this pipe (so rlan only works on machines where reslisa is
running locally).

I'm not sure why some machines are not resolved to hostnames, my best
guess is that those not found by nmblookup stay as numbers. All my
machines are detected by reslisa and lisa, what does your
reslisarc/lisarc file look like, particulary the PingNames,
PingAddresses and AllowedAddresses fields?

I hope this helps more then it confuses.



-- 
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug



[SLUG] nmblookup and Konquerer lan browsing

2002-01-10 Thread Christopher Booth

Hi guys

I've got a question, using samba 2.2.1 on Mandrake 8.1, Konqueror using lisa and 
reslisa daemons.

I've been trying to setup the lan browsing through Konqueror, talk about undocumented 
features.
I've finally worked most of it out.
Clicking on Network brings an error - cannot connect to localhost as it trys to 
connect to lan://localhost
change it to read lan:/hostname and it works depending on lisa configuration shows 
FTP, SMB, HTTP and NFS shares/connections
clicking on SMB changes the address in the address bar to read smb://hostname
and shows shares

FTP does likewise and asks for authentication and allows you to broswe the ftp site a 
la explorer/konqueror file manager style.

typing in the address bar rlan:/ scans the local subnet for machines, but doesn't name 
resolve them all or list them all for that manner

(gnomba when scanning via ip finds heaps more and name resolves them)
Very strange state of affairs.

Has anyone got this set up successfully

Christopher Booth
-- 
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug