Re: Slow network connection

Everett, that's a very nice idea. However, I thinks I will not be able to follow it: First, the database NT is a workstation, not a server NT. Also, our domain controller is a Win2K server. With a lot of help from Murray I found out, that the authentication at the domain takes less than a second when I run dbaccess on the db host machine to connect to the dbserver - using an account in the domain. Also, when I take the host away from the domain and connect to a local account, the delay doesn't change at all. By monitoring the network trafic I found that the basic tcp connection to the database port (turbo) is established in less than a second. Then a delay of 54 second occurs which Murray thinks is due to a timeout in windows. Any idea? "Everett Mills" <eemills@nationalbeef.com> wrote: > >Erwin- > You could set up the database NT box as a backup domain >controller, allowing it to authenticate its own requests...If it isn't >too busy otherwise. If you're running HADR, you could set the redundant >server as a domain controller and hopefully, since you can't guarantee >that your primary will follow the path you choose for authentication >(thanks, Microshaft), get almost as quick a response. > > --EEM > >> -----Original Message----- >> From: Erwin Lotter [mailto:lotter_NO_S_PAM_@zsw-bw.de] >> Sent: Wednesday, August 25, 2004 8:56 AM >> To: informix-list@iiug.org >> Subject: Re: Slow network connection >> >> I have to make a correction: >> The database does accept windows users from the domain too, >> but I don't need that. > > >sending to informix-list