CS> > + 22:29 [3636] call to 1:1/123@fidonet CS> > 22:29 [3636] trying f123.n1.z1.binkp.net [107.155.113.11]... CS> > ? 22:30 [3636] connection to 1:1/123@fidonet failed: {W32 API error CS> > 10065} A socket operation was attempted to an CS> unreachable hos CS> > 22:30 [188] the queue is empty, quitting... CS> > CS> > So... I don't think so...
CS> Umm, have you tried his actual URL?
I have a bundle for Ozz's 1:1/123 which the system is trying to deliver, but to no avail.
Ozz simply has no functional contact info in the nodelist at this time.
His previous (until yesterday) saltairbbs.com entry yielded this information...
+ 03 Dec 09:52:28 [4444] call to 1:1/123@fidonet 03 Dec 09:52:28 [4444] trying saltairbbs.com [107.155.113.11]... ? 03 Dec 09:52:49 [4444] connection to 1:1/123@fidonet failed: {W32 API error 10060} Connection timed out
... and his current exchangebbs.com entry isn't available either, not on IPv6 (which he has, Michiel will be pleased) nor on IPv4 (see below).
+ 03 Dec 10:01:28 [8024] call to 1:1/123@fidonet 03 Dec 10:01:28 [8024] trying exchangebbs.com [2001:470:1f18:12d::2]... ? 03 Dec 10:01:49 [8024] connection to 1:1/123@fidonet failed: {W32 API error 10060} Connection timed out 03 Dec 10:01:49 [8024] trying exchangebbs.com [107.155.113.50]:24554... ? 03 Dec 10:02:10 [8024] connection to 1:1/123@fidonet failed: {W32 API error 10060} Connection timed out
I understand you have some affinity to him, but the fact for the moment remains ... he is unreachable. And he does not have a regular nodenumber in a net somewhere.
Maybe he is getting it sorted out ...
Take care,
\%/@rd
--- D'Bridge 3.99 * Origin: Do not meddle in the affairs of wizards (2:292/854)
