Any things that I should look into with Manuel?
Get a copy of his actual segments? He mayhave a non-regular
'character' stopping it all up?
re-add R88 over R80 but also the request did not go through,
So the nodelist entry for R88 is back this week. But connecting to the single node in that region is not possible. So should it be there, or should it just be removed because the node is gone?
issuesre-add R88 over R80 but also the request did not go through,
So the nodelist entry for R88 is back this week. But connecting to the
single node in that region is not possible. So should it be there, or
should it just be removed because the node is gone?
I spoke with Patricio, he was experiencing some connectivity
by then. I tested today and could make it, if you want to give it a try..
# telnet mastodontbbs.hopto.org 2323
Trying 190.211.29.29...
telnet: connect to address 190.211.29.29: Connection timed out
If this is still the right hostname and portnumber: It's not working.
Hello Carol.
26 Nov 18 18:54, you wrote to me:
Any things that I should look into with Manuel?
Get a copy of his actual segments? He mayhave a non-regular
'character' stopping it all up?
I do have a copy of the actual segments... We have been trying to se it over MakeNL, but somehow it does not work...
Flavio
... "O Aladdin est quicando na vara" - Reptile Shaman
Hello Carol.
26 Nov 18 18:54, you wrote to me:
Any things that I should look into with Manuel?
Get a copy of his actual segments? He mayhave a non-regular
'character' stopping it all up?
I do have a copy of the actual segments... We have been trying to se it over MakeNL, but somehow it does not work...
Flavio
... "O Aladdin est quicando na vara" - Reptile Shaman
Wilfred van Velzen wrote to Nighthawk <=-
This was from last year, and R88 hasn't been in the Z2 nodelist since early this year, so I had to find a nodelist from last year, to get the connect info:
# telnet mastodontbbs.hopto.org 2323
Trying 190.211.29.29...
telnet: connect to address 190.211.29.29: Connection timed out
If this is still the right hostname and portnumber: It's not working.
Wilfred van Velzen wrote to Nighthawk <=-
If this is still the right hostname and portnumber: It's not working.
Now I'm getting a login prompt from a mystic bbs, but no binkp connect
on that port...
On the binkp port there's no connect.
@MSGID: 4:801/188 ede0230a
@TID: Mystic BBS 1.12 A42
@TZUTC:
Wilfred van Velzen wrote to Nighthawk <=-
This was from last year, and R88 hasn't been in the Z2 nodelist
since early this year, so I had to find a nodelist from last year,
to get the connect info:
# telnet mastodontbbs.hopto.org 2323 Trying 190.211.29.29... telnet:
connect to address 190.211.29.29: Connection timed out
If this is still the right hostname and portnumber: It's not working.
Well, at least something good should have come up from rescanning
FN_SYSOP: I can finally access several messages that needed an
answer.
We've had an issue back in 2019 that R88 (Chile) was stripped out
of the nodelist by accident. This has been fixed now.
The only problem is that Patricio hasn't been very active lately.
We will check on him and update if necessary.
If this is still the right hostname and portnumber: It's not
working.
Now I'm getting a login prompt from a mystic bbs, but no binkp
connect on that port...
On the binkp port there's no connect.
I spoke with Patricio, he was moving his system from Mystic
to Synchronet. Please test again, all is good now.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 32:52:21 |
Calls: | 141 |
Files: | 5,058 |
Messages: | 220,694 |