I think I may have found a slight hiccup in the new alpha version of Mystic.
In this version, I'm not able to telnet from within Mystic as I did before. I have a connection to my game server computer set up via SSH, and I can't connect now. I tried SSH and telnet, and get the "unable to connect" error. I tried to connect via Netrunner, and didn't have any problems.

I then took a look at the BBS list that I'm using, gy-bam, and I can't
connect to other BBS through there either.

I'm not sure what might have been changed in that area...


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 04/22/17, Black Panther said the following...

I think I may have found a slight hiccup in the new alpha version of Mystic. In this version, I'm not able to telnet from within Mystic as I did before. I have a connection to my game server computer set up via

Nevermind. It was my Windoze firewall giving me issues. It's working fine now...


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 04/22/17, Black Panther said the following...

I think I may have found a slight hiccup in the new alpha version of Mystic. In this version, I'm not able to telnet from within Mystic as I did before. I have a connection to my game server computer set up via
SSH, and I can't connect now. I tried SSH and telnet, and get the
"unable to connect" error. I tried to connect via Netrunner, and didn't have any problems.

I then took a look at the BBS list that I'm using, gy-bam, and I can't connect to other BBS through there either.

I'm not sure what might have been changed in that area...

Check the ports being used compared to what you used in the past - there
could be two servers trying to use the same port (22 for SSH or 1022 which
I've heard as a default for Mystic). The default port might have changed, if
so it's just a matter of how you setup the Server under Mystic and what's running by default on that system.

--- Mystic BBS v1.12 A31 (Linux)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

On 04/22/17, bcw142 said the following...

I think I may have found a slight hiccup in the new alpha version of Mystic. In this version, I'm not able to telnet from within Mystic as did before. I have a connection to my game server computer set up via

Check the ports being used compared to what you used in the past - there could be two servers trying to use the same port (22 for SSH or 1022
which I've heard as a default for Mystic). The default port might have

When I upgraded to the new alpha version of Mystic, my Windoze firewall
blocked the outbound access. Once I realized it and corrected the settings, it's working fine.

Thanks,


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

Hi All,

Anyone who is running the new A32 alpha of Mystic, take a look and make sure your nightly maintenance is running properly. For some reason, none of my events that are set up as 'Shell', are executing. They were running fine
under A31.

Here is a screen shot of the setup for my nightly maintenance:


Active � Yes
Description � Nightly maintanence Sun � Yes
Exec Type � Shell Mon � Yes
Exec Hour � 4 Tue � Yes
Exec Min � 0 Wed � Yes
Shell � c:\bbs\mystic\maint.bat Thu � Yes
Semaphore � Fri � Yes
Node � 0 Sat � Yes
Warning � 0


Knowing my luck, I changed something, and now I'm blaming it on Mystic...

Anyone else having this issue?


---

Dan Richter
aka Black Panther
Sysop - Castle Rock BBS
telnet://castlerockbbs.com
The sparrows are flying again...

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

* An ongoing debate between Black Panther and All rages on ...

make sure your nightly maintenance is running properly. For some
reason, none of my events that are set up as 'Shell', are executing.

I have all my shell events run by Windows Task Scheduler so I dunno, FYI


.- Keep the faith, --------------------------------------------------.
| |
| Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
| Email: fido4cmech(at)lusfiber.net |
| Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

... Never confuse moving fast with going somewhere.
--- GoldED+/LNX v1.1.5-b20170303 ... via Mystic BBS!
* Origin: FSXNet - Positronium Pi: telnet://cmech.dynip.com:2323 (21:2/117)

On 04/28/17, Black Panther pondered and said...

Anyone else having this issue?

No with Agency all is fine

[snip]

Apr 29 00:45:18 Executing "Nightly Maintenance"
Apr 29 00:45:18 Command line: bbsmaint.bat
Apr 29 00:58:21 Process result 0

[snip]


and fsxNet HUB 1/100 also fine...

[snip]

Apr 29 04:00:23 Executing "Nightly Maintenance"
Apr 29 04:00:23 Command line: bbsmaint.bat
Apr 29 04:02:30 Process result 0

[snip]

Best, Paul

--- Mystic BBS v1.12 A32 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)