Igor:
One more thing...I noticed that the device discovery
has started to take longer. I ran a tcpdump on a Linux machine
on my LAN, and noticed this:
05:49:40.060495 192.168.123.130.4112 > 206.13.28.12.53: 2+ PTR?
4.123.168.192.in-addr.arpa. (44) (ttl 128, id 41721)
192.168.123.30 is the machine running Kaboodle.
206.13.28.12 is my ISP's DNS server. So...everything that
Kaboodle discovers on my LAN, it appears to be asking my
ISP's DNS for a PTR name. In this case, it was for device
192.168.123.4. I see about 12 of these requests per device,
which is over 100 requests for a LAN of eight machines.
The Kaboodle GUI doesn't update until all of these DNS
requests fail.
Is there an obvious reason why Kaboodle is looking
to my ISP in this situation?
-Scott
PS: I also noticed that the VNC scan doesn't happen at
startup. And when it does happen, all 100 ports (5900 thru
5999) are checked in a "shotgun" manner: 100 ports go active
on the Kaboodle machine all at once. This could be why Win98
isn't playing nicely. Perhaps instead of 100, you could send
them out in groups of 10 or 20. So, send 10 probes, check to
see if any made a connection, then send the next 10, and so
forth.
On Wed, 20 Feb 2002, Scott C. Best wrote:
> Igor:
> Hello! Some feedback on the 19 Feb deliverable:
>
> > 3.2 If the VNC server on PC2 is not running under Kaboodle control,
> > or if PC2 is not running Kaboodle at all ...
> > Status: implemented.
>
> This looks functional now, thanks.
>
> > 3.5 In the VNC PropertyTab, the user can specify what "display\port"
> > the server is running on...
> > Status: implemented.
>
> One trouble here: the display/port data field is greyed out when
> I'm using Kaboodle to start up a VNC viewer. Some servers (which I do not
> have control over) on my LAN may be running on 5901, display 2, or
> something else. So I need access to this data field.
>
> >7 Modification to support VNC options
> >Spec: 4.2.5 Allow ONLY Kaboodle users to connect to this machine.
> >Status: implemented.
> >Comment: We forbade all users to connect to Vnc listener except their
> >own PCs. For this we placed the string -:+MyIpAddress in value AutoHosts
> >of WinVnc registry key.
>
> Interesting. I need to give this some more thought. If Kaboodle is
> used to startup the VNC server, then setting LoopbackOnly in the registry
> should be sufficient. If Kaboodle is not controlling the startup of the
> VNC server, then any changes to the registry would require a server
> restart.I'm not sure Kaboodle can do that...?
>
> >9. Remote VNC server password are stored...
> >Status: implemented.
> >Comment: Remote VNC server password is stored in registry as an
> >encrypted string. This password is not sent to the network. ... When a
> >user hits "connect" in the PropertyTab, the session is connected without
> >the usual password prompt.
>
> Is the registry entry that stores the encrypted password set
> with any non world-readable file permissions?
>
> >10 Modification to auto-detect VNC server on LAN.
> >Status: implemented for WinNT and Win2000.
> >Comment: we have some problems with memory manager for Win98.
>
> This didn't seem to detect a VNC server on my LAN at startup. I
> went thru the "check again" process in the PropTab and it did, however.
> Even when I set the server to listen on 5911, the Viewer setup detected
> it correctly, and put the right into into the port/display fields. Cool.
>
> However, when a server isn't detected, the only thing in the VNC
> PropertyTab should be a "CheckAgain" and "Stop Check" button. Only after a
> server is detected should the PropertyTab show the VNC viewer controls.
> It's confusing to show those controls if there's no server.
>
> -Scott
>
>
>
>
_______________________________________________
Kaboodle-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/kaboodle-devel
