Subj : Re: Blam BBS List question To : alterego From : The Godfather Date : Tue May 26 2020 21:03:19 al> Ahh, I have an idea. al> If you edit your nodelist and change the INA: to an al> INA:: does it fix your problem? al> I dont think that should updset the IBN (binkp details), or any of the al> other flags (ITN,IFC).... al> It's not as much a nodelist issue as it is the specific script manya re using on their BBS's for their BBSlist. The script does not appear to be recognizing : and defaulting to port 23. While I could likely fix it on my BBS, I can't do so on others who have my BBS listed. This is where the nodelist, I THINK (not sure,) can come into play. I THINK, not sure, the network lead dude has to change my port within the nodelist or when others look me up, they'll be dialing into the wrong port. Well .. telnetting into the wrong port. In addition, the aforementioned script, has a cool feature of pulling up node lists and telnettting to those on the node list. So .. I'm not sure where the issue lies, one, the other, or both, but am hoping someone knows a fix or has one in the works? --- Mystic BBS v1.12 A45 2020/02/18 (Windows/32) * Origin: The Underground [@] theunderground.us:10023 <-port (21:1/165) .