Very Computer

I use NT 4's DUN and a ZyXEL omni.net to dial an Ascend MAX 4000.
There's a problem: The setup takes about one second but the
verification of my ID takes approximately 20 secs.

As I'd like to isolate the problem I tried disabling everything in my
omni.net that had "CHAP" in its name. No luck. EMailing the admin
didn't help either. He blamed it on NT, wrote something about NT
trying to use NetBEUI but I didn't select NetBEUI. Did I miss a dialog
and it's default somewhere? I posted this question to a different
newsgroup a while ago and somebody replied that Ascend doesn't condone
to certain RFCs which forces NT to timeout before proceeding or some
such. He added that one could modify a setting in the Ascend to
circumvent this behaviour but didn't mention which one.

If you know something that might help me please let me know.
--

             | or ask your favourite key server

Quote:>I use NT 4's DUN and a ZyXEL omni.net to dial an Ascend MAX 4000.
>There's a problem: The setup takes about one second but the
>verification of my ID takes approximately 20 secs.

>As I'd like to isolate the problem I tried disabling everything in my
>omni.net that had "CHAP" in its name. No luck. EMailing the admin
>didn't help either. He blamed it on NT, wrote something about NT
>trying to use NetBEUI but I didn't select NetBEUI. Did I miss a dialog
>and it's default somewhere? I posted this question to a different
>newsgroup a while ago and somebody replied that Ascend doesn't condone
>to certain RFCs which forces NT to timeout before proceeding or some
>such. He added that one could modify a setting in the Ascend to
>circumvent this behaviour but didn't mention which one.

>If you know something that might help me please let me know.

On Sat, 21 Jun 1997 17:37:03 +0100, Richard Baldwin