TZUTC: -0400   
   MSGID: 58556.sync_sys@1:103/705 2d1662de   
   REPLY: 58555.sync_sys@1:103/705 2d15dc68   
   PID: Synchronet 3.19b-Win32 master/a2a9dc027 Jan  2 2022 MSC 1928   
   TID: SBBSecho 3.29-Linux master/27cbebcb9 Aug 10 2025 GCC 12.2.0   
   BBSID: RICKSBBS   
   CHRS: UTF-8 4   
   FORMAT: flowed   
   >   Re: MRC crashes SBBSCTRL after 50 minutes of connect time   
   >   By: Rixter to Codefenix on Wed Aug 27 2025 07:18 pm   
      
   > This error means you got a HTTP request attempt on port 5000/5001. It means   
   > those ports are open to the outside on your server, and some port scanner   
   > probably tried accessing them, causing the connector service to log the   
   > error.   
      
   > Ports 5000/5001 shouldn't be open (nor do they need to be for MRC to work),   
   > so I suggest fixing this on your router and/or firewall settings.   
      
   > That said, I doubt this what's causing your SBBSCTRL to crash. Usually   
   > "invalid message" just means the incoming message didn't look like an actual   
   > MRC message, but it's otherwise harmless.   
      
   > Are you absolutely certain the crashes happen when you're running mrc-client?   
   > Have you tried leaving yourself idle at, say, the main menu for an hour?   
      
   > |15 ¨ ¨ ¨ codefenix ¨ ¨ ¨ ConstructiveChaos BBS ¨ ¨ ¨ ¨   
   > ¨   
   > |08 ¨ ¨ ¨ (https/telnet/ssh)://conchaos.synchro.net ¨ ¨ ¨   
   > |07   
   > ---   
   >  ¨ Synchronet ¨ -=[ ConstructiveChaos BBS | conchaos.synchro.net ]=-   
      
      
   Codefenix,   
    I can leave it open to the IBBS page for days watching people on other BBSs   
   log in and out, IRC for days, the same for the main menu. I will open a web   
   page in a message group like fidonet mail area and see what happens after a few   
   hours, the same on the telnet ansi side. So far only the MRC is causing the   
   synchronet to fail and restartoncrash.exe to catch this failure, clear the on   
   screen dialogue pop up message, and restart synchronet. I have noticed this on   
   3 unique machines, all running windows 10 with the ntdvmx64 patch. Maybe the   
   patch is the culprit? I do not think MRC needs that though to run. But, maybe   
   it is causing a conflict. A true mystery. Have a great day Codefenix.   
      
   Rixter   
   telnet://ricksbbs.synchro.net:23   
   http://ricksbbs.synchro.net:8080   
      
   ---   
    þ Synchronet þ Rick's BBS telnet://ricksbbs.synchro.net:23   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/13 705 105/81 106/201 124/5016 128/187 129/14 153/757   
   SEEN-BY: 153/7715 154/10 30 110 203/0 218/700 221/0 226/30 227/114   
   SEEN-BY: 229/110 206 317 400 426 428 470 700 705 240/1120 5832 263/1   
   SEEN-BY: 266/512 280/464 5003 5006 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 902/26 5020/400 8912 5054/30   
   SEEN-BY: 5075/35   
   PATH: 103/705 280/464 460/58 229/426