NexusDB slow connection on win7 64bit

Hi

My app compiled with D7 and and run under win xp sp2 works great.

The very same app with the same data +/- a few new records takes *21.8*
seconds to connect to the db!

After the connection is made the speed of data access seems more or less
"normal".

I did have a similar problem with a different app that takes 12 seconds to
connect.

I tested this with the firewall turned OFF and av programs inactive. No
difference.

I have also experienced a (win7 32 bit) situation where the EM cannot
connect to the server and returns a network error, but the instant the
error message appears, so does the db in the EM. From then on the db
access is normal. After shutting down the EM and then starting again the
same condition applies, the error message appears when the db appears in
the EM list.

I believe this is something to do with Win7 network access/security/UAC?

Has anyone else had a similar experience and could possibly offer
corrective suggestions?


--
Kind Regards

Peter

> The very same app with the same data +/- a few new records takes *21.8*
> seconds to connect to the db!
>
> After the connection is made the speed of data access seems more or less
> "normal".
>
> I did have a similar problem with a different app that takes 12 seconds to
> connect.
> ...
> Has anyone else had a similar experience and could possibly offer
> corrective suggestions?

Windows 7 has a lot of possibilities to tweak teh network. Obviously with this
also come a lot of options for failure. The main clue here is the fact that
the speed goes back to normal once the connection is completely established.
This clearly points to some issue with connection negotiation. If you're using
a machine name (as opposed to an IP) the first place to look is name and
machine resolution. Flush the DNS (ipconfig /?) and arp (arp /?) caches and
try again. The next thing is to make sure you're not having an IP collision
(two or more machines with the same IP) which can quite easily happen if one
machine has a fixed set IP in the range IPs of a DHCP server. Most often
though this seems to happen when people use VMWare or similar and forget to
change IPs when copying Vms. If that's ruled out, take a look at switching off
the network auto tuning
(http://www.sysprobs.com/network-is-v...-windows-vista), which can a
major impact on DNS lookup and machine resolution. If you're using some
network card with a broadcomm chip, disabling Remote Differential Compression
(RDC) *could* have an impact as well. Next idea is an issue in your network
routing table on either of the two machines or a problem with a router (NAT?)
in between. Try both machines on the same router on the same subnet. And if
you can try them on a different router as well. Last but not least it could
simply be that the network card(s) have problems on negation of link speeds,
so settings these manually (or if they are manul back to automatic) could do
the trick.

These are just the top 5 or so issues occuring on network configurations, not
only on Win7, but also Vista and Win2k8. There are plenty of other
possibilities of what's going wrong, but I guess that should get you started.


--

Hannes Danzl / NexusDB

Issue Tracker - http://www.nexusdb.com/mantis/view_all_bug_page.php
Newsgroup Web Gateway - http://www.nexusdb.com/forums/
Newsgroup Search - http://www.nexusdb.com/forums/search.php

Please check if you try to uncheck “Automatically detect settings” in
Internet Options of Internet Explorer helps?

Refer here: http://tinyurl.com/2dw7rzf

Peter Sanders;100149 Wrote:
> Hi
>
> My app compiled with D7 and and run under win xp sp2 works great.
>
> The very same app with the same data +/- a few new records takes *21.8*
> seconds to connect to the db!
>
> After the connection is made the speed of data access seems more or
> less
> "normal".
>
> I did have a similar problem with a different app that takes 12 seconds
> to
> connect.
>
> I tested this with the firewall turned OFF and av programs inactive. No
> difference.
>
> I have also experienced a (win7 32 bit) situation where the EM cannot
> connect to the server and returns a network error, but the instant the
> error message appears, so does the db in the EM. From then on the db
> access is normal. After shutting down the EM and then starting again
> the
> same condition applies, the error message appears when the db appears
> in
> the EM list.
>
> I believe this is something to do with Win7 network
> access/security/UAC?
>
> Has anyone else had a similar experience and could possibly offer
> corrective suggestions?
>
>
> --
> Kind Regards
>
> Peter


--
ccy

ccy wrote:

>
> Please check if you try to uncheck Automatically detect settings in
> Internet Options of Internet Explorer helps?
>
> Refer here: http://tinyurl.com/2dw7rzf

Oh, yes, forgot about this. This should be the first thing to check!


--

Hannes Danzl / NexusDB

Issue Tracker - http://www.nexusdb.com/mantis/view_all_bug_page.php
Newsgroup Web Gateway - http://www.nexusdb.com/forums/
Newsgroup Search - http://www.nexusdb.com/forums/search.php

Hi Hannes

On Tue, 27 Jul 2010 10:31:13 +0800, Hannes Danzl[NDD]
<hannes@nexusdb.dbnexus.com> wrote:

> Windows 7 has a lot of possibilities to tweak teh network. Obviously
> with this
> also come a lot of options for failure. The main clue here is the fact
> that
> the speed goes back to normal once the connection is completely
> established.
> This clearly points to some issue with connection negotiation. If you're
> using
> a machine name (as opposed to an IP) the first place to look is name and
> machine resolution.

I used to use the ip address and changed to the pc name after an answer to
a previous question (of mine) in this forum

> Flush the DNS (ipconfig /?) and arp (arp /?) caches and try again.

I will do this.

> The next thing is to make sure you're not having an IP collision

I know this is not the problem.

> take a look at switching off the network auto tuning

I will do this.


> (http://www.sysprobs.com/network-is-v...-windows-vista), which
> can a
> major impact on DNS lookup and machine resolution. If you're using some
> network card with a broadcomm chip, disabling Remote Differential
> Compression
> (RDC) *could* have an impact as well. Next idea is an issue in your
> network
> routing table on either of the two machines or a problem with a router
> (NAT?)
> in between. Try both machines on the same router on the same subnet. And
> if
> you can try them on a different router as well. Last but not least it
> could
> simply be that the network card(s) have problems on negation of link
> speeds,
> so settings these manually (or if they are manul back to automatic)
> could do
> the trick.
>
> These are just the top 5 or so issues occuring on network
> configurations, not
> only on Win7, but also Vista and Win2k8. There are plenty of other
> possibilities of what's going wrong, but I guess that should get you
> started.

Thanks for the suggestions

--
Kind Regards

Peter

"Hannes Danzl[NDD]" <hannes@nexusdb.dbnexus.com> wrote in message
news:xn0gx4wo3fusc5300w@news.nexusdb.com...
> ccy wrote:
>
>>
>> Please check if you try to uncheck Automatically detect settings in
>> Internet Options of Internet Explorer helps?
>>
>> Refer here: http://tinyurl.com/2dw7rzf
>
> Oh, yes, forgot about this. This should be the first thing to check!

You learn something every day. Has anyone got reason why we need to do this?
--
Regards
Will Owyong [NDX]
Newcastle, NSW, AUSTRALIA
GMT+10

Hi

On Wed, 28 Jul 2010 09:24:57 +0800, Will Owyong [NDX]
<stuvik@nospam.gee.mail.com> wrote:

> "Hannes Danzl[NDD]" <hannes@nexusdb.dbnexus.com> wrote in message
> news:xn0gx4wo3fusc5300w@news.nexusdb.com...
>> ccy wrote:
>>
>>>
>>> Please check if you try to uncheck %13Automatically detect settings%14
>>> in
>>> Internet Options of Internet Explorer helps?
>>>
>>> Refer here: http://tinyurl.com/2dw7rzf
>>
>> Oh, yes, forgot about this. This should be the first thing to check!
>
> You learn something every day. Has anyone got reason why we need to do
> this?

I don't know why it seems we need to do this, but I discovered this option
due to a different problem.

When I set up two new pcs (for a client) in my office, the internet
connection was "automatic" i.e. Windows itself made the connection and
everything worked as expected. When I delivered the pcs to the client I
could not get the pcs to connect to the net. I tried setting and resetting
everything I could think of, checked passwords router settings etc, etc. I
could not get a connection!

I unchecked this box and the internet appeared instantly!

It seems to me that if this is set, it works once and that's it. The
detected settings are committed to memory and do not change. The
"automatically detect settings" does not work again unless you uncheck and
check this box.

--
Kind Regards

Peter