|
|
| Author |
Message |
| 25 new of 181 responses total. |
janc
|
|
response 125 of 181:
| 
Nov 10 19:14 UTC 1998 |
Did our trunk hunt get messed up when we dropped those two lines?
|
scott
|
|
response 126 of 181:
|
Nov 10 21:04 UTC 1998 |
SHouldn't be. In any case, the numbers were the last 2, and when I got
the problem there weren't that many people on thru the modems. I'll
have to drop by and reprogram the modems and probably reboot the
terminal server as well.
|
mcnally
|
|
response 127 of 181:
|
Nov 10 23:18 UTC 1998 |
I got the same thing.. Dialed into 761-3000, no login prompt.
Hung up and dialed 761-5041 and everything was peachy. Didn't
bother to track it down any further in the hunt sequence but
I'm sure you've got a flaked-out modem..
|
scg
|
|
response 128 of 181:
|
Nov 10 23:28 UTC 1998 |
761-5041 is now the second modem in the hunt, so assuming nobody else was
calling in or logging off at the same time, that will have tracked it down.
|
scott
|
|
response 129 of 181:
|
Nov 11 01:16 UTC 1998 |
It may be intermittant. Last time we had odd troubles, I just reprogrammed
all the modei. That's not a big deal, actually, since I've got scripts on
my Newton to do the programming.
Interestingly, the newer modems without the dumb mode seem to be more stable
than the older ones. Mind you, that's a 0.001% problem given how much traffic
these modems carry.
|
keesan
|
|
response 130 of 181:
|
Nov 11 03:24 UTC 1998 |
5159 works perfectly.
|
scott
|
|
response 131 of 181:
|
Nov 11 11:52 UTC 1998 |
(I'd be much happier if everybody used 761-3000, only going to other numbers
as a last resort, BTW)
|
dpc
|
|
response 132 of 181:
|
Nov 11 15:06 UTC 1998 |
I had the same problem as the others on the morning of 11/10 when I
dialed into 761-3000. I got in on 761-4931, which is the number I
always try second, for reasons lost in the mists of time.
|
remmers
|
|
response 133 of 181:
|
Nov 11 15:48 UTC 1998 |
Grex was off the net early this morning but is back on again.
|
keesan
|
|
response 134 of 181:
|
Nov 11 19:48 UTC 1998 |
5159 works faster than 3000.
|
scott
|
|
response 135 of 181:
|
Nov 11 19:56 UTC 1998 |
With identical hardware?
|
tpryan
|
|
response 136 of 181:
|
Nov 11 22:47 UTC 1998 |
Could 761-4931 be the old break between fast and slow modems.
|
scg
|
|
response 137 of 181:
|
Nov 12 04:55 UTC 1998 |
Nope, that was 761-5041. We rearranged the hunt group to try to get people
to dial into the beginning of the hunt group, which makes various things much
easier for the staff.
|
keesan
|
|
response 138 of 181:
|
Nov 16 21:30 UTC 1998 |
Last night the grex phones were busy from 8:20 to 8:30 and this afternoon from
4:03 to 4:16. If this ends up adding up to 30 minutes/week for more people
than me, I suggest restoring one phone line, or is there some problem with
the phone lines at present? Apart from Sunday at 8 and weekdays at 4, what
other busy times should I beware of?
|
keesan
|
|
response 139 of 181:
|
Nov 17 01:30 UTC 1998 |
I think the problem may have been my dialing 5159, apparently if the numbers
near the end of the trunk are busy I do not get routed to the beginning. I
will figure out how to change the timeout period in Procomm so as to use 3000.
|
scg
|
|
response 140 of 181:
|
Nov 17 02:46 UTC 1998 |
Right. You only get all the lines if you dial in on 761-3000. That's why
people should dial in on 761-3000.
|
hhsrat
|
|
response 141 of 181:
|
Nov 17 16:19 UTC 1998 |
11am-1pm is a pretty busy time to telnet in
|
tsty
|
|
response 142 of 181:
|
Nov 18 11:40 UTC 1998 |
i started out as #87 in line... 2.5 hours ago...
|
krj
|
|
response 143 of 181:
|
Nov 18 16:48 UTC 1998 |
I started item:128 for whining about the telnet queue.
(Yes, I'm one of the whiners.)
|
keesan
|
|
response 144 of 181:
|
Nov 18 22:39 UTC 1998 |
I have been unable to reach grex for two days, after changing to dialing 3000
instead of 5159. Jim set Procomm up to time out after 30 sec, I have not been
able to figure out how to make this longer, anyone happen to know? I finally
dialed 5159 again and got connected immediately. Sent a couple of files via
M-Net and they don't seem to support x or y modem. Is there some way to set
up the trunk thing so that if the last couple of numbers are busy it goes back
to the beginning?
|
davel
|
|
response 145 of 181:
|
Nov 19 02:48 UTC 1998 |
Sindi, is this DOS Procomm Plus? It's been a long time, but I might be able to
check ...
|
davel
|
|
response 146 of 181:
|
Nov 19 02:53 UTC 1998 |
(If it's Windows Procomm, change it thus: open the dialing directory. In the
menu bar at the top, click on Options, then on Call Settings. But I think
I remember that you're using DOS Procomm ... vague memory says to me that it's
somehow through the dialing directory in that, too; could be wrong.)
|
bean
|
|
response 147 of 181:
|
Nov 19 04:11 UTC 1998 |
20 waiting, 26 remote, 4 local users, 72 max remote users, 6735 head
Okay, I give up, why are 20 waiting if only 26 are on?
|
scott
|
|
response 148 of 181:
|
Nov 19 11:55 UTC 1998 |
If DOS, try hitting the End key while it is dialing.
|
keesan
|
|
response 149 of 181:
|
Nov 19 18:21 UTC 1998 |
I hit the end key while dialing, but also had to hit return key in order for
the count to resume. Reset to 60 sec, it still timed out on both 3000 and
5141 at 9600. After five or so tries, I finally tried 3000 at 2400 and
connected in 12 sec total. The attempt at 9600 gave me a high-pitched squeal
at about 25 seconds that continued to 60 sec. (5059 gets a recording, this
number no longer in service). This problem started two days ago. I dialed
M-net okay and got through to 3000 at 9600 yesterday, so assume my modem ok.
Can anyone explain why the lower speed will connect but not 9600?
|
