Hello everybody,

I have a very depressing and very urgent problem, please help.

I have problems connecting to AS2000 server over LAN: the Connect statement
lasts 9 seconds.
Simply 9 seconds - never less, never more.
I thought that the reason is ADOMD net client, but the same problem appears
even if I connect from MDX Sample Application. The Connect statement lasts 9
seconds, then everything works fine and very fast.
(In fact, from MDX Sample App, only the first Connect lasts 9 seconds; the
second and every subsequent Connect lasts only 4 seconds. But I think it is
too much as well.)

The configuration is:
"server": Win2003 server standard edition + SP1, SQL2000 + AS2000 + SP4
installed,
"client": Win2003 server standard edition + SP1, SQL2000 + AS2000 + SP4
installed
(I run MDX Sample App on the "client" and connect to the "server"),
both machines connected with fast Ethernet (1Gb),
both machines are in the same workgroup (no domain),
I am in Administrators group on both servers (with the same user name &
password).

During the Connect statement processor is idle on both machines, and there
is almost no disc activity.
If I connect locally, it's almost immediately (about 0.1 s).
Everything other is very fast (e.g. ping from "client" to "server" <1ms,
Connect network drive & browse with no noticeable delay, log-in with RDC
client very fast).
Seems that the problem is related to AS2000 only.

One interesting thing: if I connect from "server" to the "client" (with MDX
Sample App), it is almost instantly.
But unfortunately, I need to connect from "client" to "server".

Thanks for any ideas.

Jiri Cerny

verify your network configuration.

maybe you have a name resolution issue.

do you connect using the netbios name or the DNS name of your server?


"Jiri Cerny" <j-cerny (AT) post (DOT) cz> wrote

Thanks for suggestion, Jéjé.
I am connectiog using IP adress.
I have tried netbios name too, with the same results.
BTW, all other software but AS runs fast with both IP adress or netbios
name.


"Jéjé" <willgart_A_ (AT) hotmail_A_ (DOT) com> wrote

I suspect a network issue.
when the time taken to authenticate is long sometimes the problem come from
a DNS configuration.
double check the DNS config of your server and stations.
the primary DNS server should be your active directory server.
and try a dns name when you connect to your server.


"Jiri Cerny" <j-cerny (AT) post (DOT) cz> wrote