@MSGID: 1:340/1101 00c955e1
@REPLY: 75662.sync@723:320/1 2e87f700
@PID: EleBBS/W32 v20130208.d
@NOTE: IceEdit 2.35 K96741
@TID: FastEcho 1.46.1 43288

* In a message originally to MARTIN KAZMAIER, Dumas Walker said:


 > Worst case scenario is that he can tell binkd to listen on another port,
 > which would allow binkit to answer your "calls" on 24554 without
 > interference.

 > If he is trying to run them both, I would imagine that synchronet/binkit
 > is probably complaining about the port already being in use (because
 > binkd  has already been bound to it). He should be able to see that
 > in his logs.

Yeah, he was running both.  It`s fixed now!  Thanks to everyone!

--
Shurato, Sysop Shurato`s Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss, ssh utf-8) (22,23,110,21,119,999,2222) shsbbs.net FREQ Me!


---
 * Origin: Shurato`s Heavenly Sphere telnet://shsbbs.net (1:340/1101)
SEEN-BY: 1/19 100 16/0 19/37 40 50/109 105/81
106/201 123/130 128/10 187
SEEN-BY: 129/14 142/104 153/7715 154/110 203/0
218/700 221/0 1 6 226/30
SEEN-BY: 227/114 229/110 112 114 206 317 400 426
428 470 700 705 240/1120
SEEN-BY: 240/5832 266/325 512 280/464 5003 291/111
300/6 301/1 113 320/119
SEEN-BY: 320/219 319 2119 322/757 762 326/101
340/0 101 200 400 800 1100 1101
SEEN-BY: 341/66 342/200 396/45 60 423/81 460/58
463/68 633/280 712/848 902/26
SEEN-BY: 5000/111 5020/101 715 848 1042 4441 12000
5030/49 1081 5060/900
SEEN-BY: 5061/133 5075/35 128 5083/444
@PATH: 340/1101 400 128/187 229/426 320/219 221/1
301/1 5020/1042 4441