Re: Unable To Bind To Port 6400 [ScanMail found this email to be virus-free.]

[email protected] Tue, 28 Sep 2004 15:47:45 +0200
Newsgroups gmane.linux.suse.domino
Message-ID <[email protected]>
Hi,


port 6400 seems a bit confusing to me. Reguarly this port ist used by some 
seagate software. For getting it right you need to figure out which 
application binds to port 6400. You can verify it by: $lsof -i TCP | grep 
[notesUserName]. Your given output represents all open ports of Lotus 
Domino. If you find your port or 'info-apps' either your domino 
configuration, or your configuration of a domino application/ plug-in is 
the reason - i'd rather direct my attiontion on the second alternative.

You can check several other things:
- Exceeds this port the port range of my system? -> $cat 
/proc/sys/net/ipv4/ip_local_port_range
- Is there any established connection on this port? -> $netstat -ant | 
grep 6400
- Maybe some appliation controlled by inetd/ xinetd uses it.  Grep for it 
;)

I know that this only of little help at first sight but this might help 
you to get aware of the problem causing application.

hth

stefan


Mit freundlichem Gruß/ Kind regards

Stefan Schreiner

S&W Communication und Software Development GesmbH
Rilkeplatz 1
1040 Wien

t: +43 1 505 39 26 - 28
f: +43 1 504 29 76
m: [email protected]

[email protected] wrote on 28.09.2004 14:50:27:

> 
> Hi out there, 
> 
> I hope you can help me with a curious problem I am experiencing. 
> I've set up a new domino server (5.0.12) on SLES 9.0. When starting 
> the SMTP Task, the following error message is generated on the 
> domino console log every 20 seconds: 
> 
> "Unable to bind to port: Port=6400 errno=98 "Address already in use" 
> "SMTP Server Listener Failure - The requested TCP/IP Port is already
> in use on this system." 
> 
> I always thought that SMTP listens on Port 25 if not told to do 
otherwise. 
> When viewing the tasks of the domino server it tells me "SMTP: 
> Listening on port 25". 
> So what is this Port 6400 all about ? I couldn't really find 
> anything about this by googling, except for some Trojan called 
> "TheThing" which I can rule out as the new server is running 
> isolated in a testing environment as yet. 
> 
> I'm not exactly a Linux pro, so any advice on this is very much 
appreciated. 
> 
> Thanx in advance. 
> 
> Torsten -- 
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]