Re: krdc error when trying to connect

Ramon wrote:

Geoffrey Clements wrote:
Ramon wrote:

[snip]

Ok then, if this is a firewall issue then:

[1] Open the ports that VNC (or RDP) uses
[2] Look at the log of the firewall. The log file may be in the
/var/log directory. Since I am using Guarddog, my log file is in
/var/log/messages. If krdc is being blocked by the firewall, it will be
registered in the log file.

To view the last blocked connections use the tail command.

I'm using guarddog too.

The relevant line in the log is:
Oct 18 18:28:06 spock kernel: [32912.852855] DROPPED IN= OUT=eth0
SRC=192.168.1.1 DST=239.255.255.253 LEN=86 TOS=0x00 PREC=0x00 TTL=8 ID=0
DF PROTO=UDP SPT=1131 DPT=427 LEN=66

This happens whenever I try to connect to another desktop.

eth0 is my wired LAN and is unused at the moment (I'm on wireless using
wlan0) and its IP address is 192.168.1.1.

I have followed the directions at
https://help.ubuntu.com/community/HowToZeroconf and set up guarddog to do
multicast, I have checked it by doing:
$ ping spock.local
which works ok.

I don't understand why port 427 is being tried as I believe this is for
the NCP filesystem which is a Novell protocol. In any case I have added
239.0.0.0/8 to my "multicast" zone (along with 224.0.0.0/8) and
enabled "NCP File System - Novell NetWare(TM) protocol" on this zone to
serve all other zones but still no luck.


Port 427 is used by the SLP and SLP is used by krdc
(http://docs.kde.org/kde3/en/kdenetwork/krdc/faq.html).

Oct 18 18:28:06 spock kernel: [32912.852855] DROPPED IN= OUT=eth0
SRC=192.168.1.1 DST=239.255.255.253 LEN=86 TOS=0x00 PREC=0x00 TTL=8
ID=0 DF PROTO=UDP SPT=1131 DPT=427 LEN=66

What the above line means is:
That the destination UDP port 427 is being blocked by the guarddog. You
must open that port.

[1] Important to open port 427 UDP.
[2] Save the guarddog configurations, and retry to use the krdc.
[3] If it does not work, then type the following command "tail
/var/log/messages" and read the last blocked entry. Open the port of
one of the last entries. Go to step [2]...

Hope it helps.

Thanks - you have been very helpful.

I have enabled port 427 in every zone and yet I still get the error message.
It may be because not all zones are "connected" but it seems to me that it
should only need enabling in the "multicast" zone to serve the "local"
zone. It may be that I'm tickling a bug in guarddog but I don't fancy going
through hundreds of lines of iptables commands in /etc/rc.firewall!

So far the only way I can avoid the error message is to switch off guarddog
completely which I don't want to do.

The answer is in the guarddog configuration I'm sure, the problem is finding
it :-/

Cheers,
--
Geoff Registered Linux user 196308
Replace bitbucket with geoff to mail me.
.

Relevant Pages

  • Re: CUPS, Sarge/Debian/GNU/Linux and Mac OS X
    ... blocking port 631 on your linux box? ... # This is the CUPS configuration file. ... the access log file; if this does not start with a leading / ... determines whether the scheduler will allow new printers ...
    (Debian-User)
  • Re: FTP Send Port doesnt transmit messages!
    ... < 230 User TestSFTP logged in. ... retransmitted after the retry interval specified for this Send Port. ... The "FTP" adapter is suspending an outbound message going to destination ... The log file shows only the above text repeated three times!!! ...
    (microsoft.public.biztalk.general)
  • Re: router port forwarding ssh to a zone
    ... linksys router, I forwarded port 9022 to the zone's IP. ... Port 22 is forwarded to my global zone. ...
    (comp.unix.solaris)
  • Re: Cant access site from internet
    ... on which port do you try to access to your site from LAN? ... > Zone: Internet ... > Internal URL: http://mycomputername:50000 ... I could install WSS on it, and set up a site properly, but can't manage to access it from the internet. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: IIS 6 - post problem at port 80
    ... Are you sure that your ISP/network-environment is not blocking port 80 ... Please check your W3SVC log file to see if the POST request is in the log ...
    (microsoft.public.windows.server.security)