|
|
|
M-Net is co-locating to WWNet in Livonia on Monday, December 27. This is the item we will use to help people reach the new M-Net via telnet, dialin, or whatever.
46 responses total.
The co-location process is now under way after a one-day delay.
leave it to the heroes moving the system to wait until we get hit with winds and snow. big ego boost to everyone involved.
ah shore hope they brought some tahr chains 'n kitty litter! shew wee!
Doh!
<hugs cy>
Anytime you can post the Phone numbers, it would be greatly
appreciated.
(I can wait, mind you. But mom likes to hot-chat as a thirteen
year old female. don't ask... :> )
Hm. I'm still getting an endless ring on the patron line, 994-5131.
As I read the account, only one number is being answered by M2-net, 994-4644 I think. I don't have time to play with it myself.
I just used grex's implimentation of lynx to check Arbornet's
web page. It still has the old Number (734)996-4644. Perhaps something to up-
date when staff has time?
(I'm still without membership here, or I'd just telnet in. $60
is a LOT of money right now...)
734 585 0010 at login prompt: mnet at password: <ret> proceed as before...i think u actually have to hangup on exit now or somethin.
It's great news that at least M-Net is up!
I just tried calling 996-4644 and the blasted modem would not connect to mine. Thanks for the phone number.
Last night I dialed 585-0010 and got a WWNet login prompt. I tried "mnet" followed by "<CR>". No joy. I tried "m-net". No joy. I tried "arbornet". It hung up on me. WTF do you have to do to get to M-Net now?
no problem for me <shrug>
"mnet" worked for me. No problem...
mnet No -. When you type mnet, it will give you a password prompt. If you hit return there, it should connect you.
I've found the connection/interface flakey at times, Russ. Just keep trying, and it WILL log you in, and transfer you to the Arbornet/m-net login.
http://www.arbornet.org/m-net/ still has outdated information on it.
I have tried reaching M-Net through WWNet, and all I have seen after the WWNet login/password prompts is a dead line (with an active echo). No M-Net login prompt, though M-Net is accessible from Grex via telnet.
Don't know what to say, russ. I've found a simple tap of the enter key after the modem connects will prompt WWNet's login, after that I've had very few problems. It (WWNet) does seem to have longer pauses when Internet traffic is high, but that's about it.
I wonder if the mix of CR and LF matters on the "simple" Enter tap?
Re #20: The pauses I've seen are upwards of 40 seconds. Talk about a huge waste of time.
I sign on early in the morning, or after midnight. Is it safe to assume you're an evening user?
It could be a parity issue.
Today when I hit the return after the password prompt my cursor jumped to the left (staying on the same line) and did not move me to the individual log in prompt. When I tried to telnet to m-net.arbornet.org (which is what I think I used in the past) I got a UM/ITD system. WTF is going on? (I also tried mnet.arbornet.org and got nothing).
it appears that either wwnet is offline or the m-nut box needs a reboot. in any event ya can't log on either by telnet or dial-up.
I've been trying to get my mom dialed into M-Net (which she has been using for Email for some time now). She has an antique computer with a US Robotics 2400 baud modem set at N-8-1. It seemed to work fine with Grex, but wouldn't connect to 585-0010 at all. So I dug up an slightly less old 9600 baud Practical Peripherals modem (I'm not sure her computer could handle anything much faster). Dialing to 585-0010 with it set to N-8-1 I got the first login prompt just fine. I typed "mnet" at "login:" and hit return for "password:" It gave me a screen full of garble, containing just enough coherent characters to convince me that it was a mangled version of M-Net's banner. I tried playing with parity settings, trying E-7-1 and a few other less likely things, but everything was even worse than N-8-1, with even fewer coherent characters. I thought maybe 9600 was too fast for my mom's computer, so I dialed into Grex. It connected fine. I could cat really big files without any garbling of the data at all. Since 585-0010 is the same number I dial to connect to my ISP, I dialed there again, and instead of logging in as "mnet" logged into my own account. Worked fine through the password prompt, but after the password prompt it was all garbled, with just enough small fragments to be recognizable as the Linux version number and such like that crush always prints when I log in there. So I'm rather baffled.
I had the same problem with Mom's apple IIe. What it turned out to be, I'd set up an entirely new BBS profile, instead of changing the number on the old one. I had to go into the guts of the program, and change the terminal emulation to get it to work right. You might want to try that with the software you're using...
That doesn't sound right. I didn't set up a new profile. I used the old one and only changed the phone number and then when I switched to the faster modem, the baud rate. The garbage I was getting wasn't like when you have the terminal emulation set wrong. It looked more like a parity error, with a few letters coming through OK, and others missing or garbled. It didn't happen only when I started something terminal aware - like vi or pico. It happened as soon as I started talking to the M-Net computer instead of the terminal server. The software I'm using is Telix.
Re #27: I've seen this elsewhere, including on Grex. It appears to be a problem with faulty hardware flow control on the ISP end. The computer is far faster than your connection, and when the modem's buffers fill up stuff just gets hosed. If the modem is faster, the system latencies show the problem seldom if ever. Of course, buffering in the modem hoses software flow control too (ever send ^S and find there's 20K of data yet to be dumped on you? not fun). This is one reason I don't care for modems to have huge buffers unless they are doing error correction.
Who is the I? Make that ISP. (I'm using Microsoft Telnet 1.0 Windows 95. Cann't say enough bad things about it.
Re #27 - it sure sounds like parity to me. Some terminal programs have
an option to send "space" parity on output, and ignore parity on
incoming data. This might fix the problem. Also, if it's parity, you
may be able to tell a difference between even & odd parity characters:
Here's a selection of common non-printable and all printable characters,
classified by parity:
even:
^@ ^C ^I ^J ^Q ^X !"$'(+-.03569:<?ABDGHKMNPSUVYZ\_`cefijloqrtwx{}~
odd:
^D ^G ^H ^M ^S ^U ^V space #%&)*,/12478;=>@CEFIJLOQRTWX[]^abdghkmnpsuvyz|^?
If the terminal cares about parity, it may either show a blotch (some
sort of block character that's not part of ascii) or nothing when it
detects bad parity. Most modern PC terminal programs display funny
non-ascii characters when they are in 8-bit mode and receive something
with the parity bit set.
Here's m-net's banner in "even" parity (all odd-parity characters
replaced with _):
_elco_e__loc_l___e_t...
_elco_e_to_t_e___ce_______t_re_M-Net_
BSD__BSD__S_3.__(_-_et._r_or_et.or___(tt_q__
__ter___ew__er___t_t_e_lo_i___ro__t_to_cre_te____ew__cco__t
__ter_____r__e___t_t_e_lo_i___ro__t_to_fi___o_t___o_t_i_cre__e___cce__
BSD__BSD__S_(_-_et._r_or_et.or___(tt_q__
lo_i_:_
Here's m-net's banner in "odd" parity (all even-parity replaced
with _):
W____m_, ___a_ gu_s_______W____m_ __ _h_ On__ and Fu_u__ _____ ____I
___/O_ __1 _m_n___a_b__n_____g) ___y_2)__En___ n__us__ a_ _h_ __g_n
p__mp_ __ ___a__ a n__ a___un__En___ upg_ad_ a_ _h_ __g_n p__mp_ __
__nd _u_ ab_u_ _n___as_d a___ss______I ___/O_ _m_n___a_b__n_____g)
___y_2)____g_n_
Here's crush with even parity:
_elco_e_to__i__x__.0.36.
cr____lo_i_:_
Here's crush with odd parity:
____W____m_ __ L_nu_ 2___________ush __g_n_ _
Since ^J has even parity, but ^M odd parity, with odd parity output,
everything may print on one line. With even parity, the carriage
returns may not print, so the output may actually look more like:
_elco_e_to_t_e___ce_______t_re_M-Net_
BSD__BSD__S_3.__(_-_et._r_or_et.or_
__(tt_q__
&etc.
Since Jan says he saw the linux version number, that suggests that he
saw the ".0.36." which means he's probably seeing even parity
characters, but not odd parity, so it's very likely something is forcing
even parity by setting the parity bit on all odd parity characters.
That is, 7E1, which was at one time pretty much the standard for these
things. Since the string mnet<return> is odd,odd,even,even,odd parity,
if the terminal server itself wants to see "space" parity, but the
terminal is sending (and expecting to receive) even parity, then you'd
have to temporarily set the terminal to 8n1 or odd parity to send the
'mn' and <ret> characters, to ensure the parity bit isn't set on those
characters.
There's probably a way to configure the terminal server to avoid all
this nonsense.
I use 9600 N-8-1 and a 9600 Hayes modem. Works great on GREX and M-net. The DOS Procomm I use will send out the init string to the modem to go to 9600 in case I use the 14.4baud modem connected to another machine.
M-NET Access Information (Updated 12/30/99)
Dialin Access Numbers:
Ann Arbor 734 585-0010
734 661-1234
Belleville 734 529-0522
734 448-1234
Birmingham 248 430-0556
248 284-1234
Brighton 810 224-0004
810 222-1234
Farmington 248 957-0531
Dialing any of these numbers, you will be prompted with a Login: prompt,
at which, you would enter 'mnet', and then when prompted for a password,
you should just hit return. This will connect you to m-net, at which
point you will be prompted with the standard M-net login prompt.
Telnet Access:
ttyp0-p7 patron.arbornet.org patron WWnet
ttyp8-pf member.arbornet.org member WWnet
ttyq0-r3 guest.arbornet.org guest (local) WWnet
ttyr4-sf guest.arbornet.org guest (remote) WWnet
Anyone with access to an Internet account on another machine may
'telnet m-net.arbornet.org' (same as guest.arbornet.org)
Members should use member.arbornet.org and patrons should use
patron.arbornet.org instead.
WWnet=World Wide Net, Our Internet Service Provider.
THERE! that's the info on the colocation numbers.
Re #34: When uploading ASCII, remove linefeeds. Also, I've been unable to get through on any of the Ann Arbor numbers today. The modems will not connect to mine. Did they make some change that obsoletes 14.4 kbps modems?
Mom's using a 9.6 kbps modem with her apple IIe, and doesn't have a problem. I'm fairly sure, however that the 14.4's got sold, and we're simply using WWNet's modem bank and phone lines instead of something special.
Re #36: I was talking about WWNet's modems. I could not get a connection on 585-0010 or 661-1234 for a couple days. Lots of noise, but no connection. I was able to get on this evening. Did WWNet do something to obsolete 14.4k modems on some of their lines?
I'm fairly certain WWnet's Modems are 56k. My modem, a software
upgradable V.90 connects at 32k most of the time. As for the noise problem,
Mom or I haven't eperienced it. I STILL have to hit the return/enter key
once to get WWnet's login prompt on occasion.
If they "obsoleted" 14.4k modems, Mom wouldn't be able to sign on,
and she hasn't told me about it.
If your v.90 modem connects at 32k, you are experiencing a noise problem.
|
|
|
- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss