BS>>> Fx. 2:236/100 (fido.kofobbs.dk), the transfer fails if it goes
 BS>>> over port 23, if it goes over 60177/60179 there is no problem.

 BS> It should be 2:236/150

no matter for my stuff... 153, actually, if going by the nodelist... gert
has 150-153...

 BS>>> Does anyone knows the difference about those ports?

 ml>> technically speaking, there is nothing about the ports, themselves,
 ml>> that is any different from any other port... it must be something on
 ml>> the software side of the destination port that is causing the
 ml>> problem...

 BS> Uhm. He's using argus.

i figured as much... either argus or radius... what version of argus?
perhaps you/he has found a bug that's fixed in radius? radius is a
derivitive of argus and argus isn't under development any more...

 ml>> i'm performing a scan on that system now and currently see that only
 ml>> ports 21 and 23 are open... port 21 is being handled by the xitami
 ml>> ftp server... i'm not yet sure about what's handling port 23 and my
 ml>> scanner hasn't gotten up to the other ports, yet...

 BS> port 60177 and 60179 should be open too...

they are/were once my scan got there... they did give me EMSI hits before
displaying the banner to hit escape twice... the only other ports open were
80 and 110...

 BS> BTW portscanning is illegal in dk.

i'm not in dk...

 ml>> i'll see what turns up in a bit when the scan completes and what i
 ml>> can determine by manually accessing those ports...

 BS> ok

i've not been able to turn up much of anything, at this time... and i've
somehow gotten my argus stuck in connect mode with that system and can't
get it unstuck ;-(

does gert have any ideas? it doesn't seem possible to have seperate
settings on each IP port unless one is possibly running seperate argus'...

what OS is he running?

)\/(ark