Re: Win2K3 Client / Win2K3 & 2K SQL Server DBNETLIB Problem!

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Teddy Smith (teddy_at_smith.com)
Date: 09/14/04 

Date: Tue, 14 Sep 2004 09:42:53 +0930

Hi Howard,

> This would often indicate a DNS issue, but you say that targetting with
the
> IP address fails too. DBNETLIB implies it's using the TCP/IP library, so
not
> sure I know the answer to this part from what you've said. However, if the
> response is immediate, you can be fairly sure it's an authentication
issue.
> If it takes a while to respond it's likely to be a connectivity/name
> resolution issue. If you run a NetMon on the client and/or server machine
to
> trap the traffic this will help indicate if you have an authentication or
> connectivity issue.

Yes I have tried this and it does not seem to be a problem. When the script
runs on the client it seems to connect to the database and start pulling the
records out.. It gets to about 1500 records, pauses for a few seconds and
then throws the error. This is random however as sometimes it might get 1600
or 1700 records and then error, but I have found if it needs to get over
about 1500 it will almost always give this error.

I am also wondering if it has something to do with TCP port allocation. When
I run "netstat -an" from the commaned prompt while the query is running I
can see all the client ports being opened to 1433 on the SQL server and this
is working. Once the client gets to port 5000 it seems to stop and then
start using ports from 1025 again (re-using them I suppose), this is about
the time the error is thrown. These ports stay open in the netstat table for
about 1 or 2 minutes after the query had run and then disappear. I have
found if I get the error above and then try and run another query straight
away I will get the timeout error below, so this makes me think Windows 2003
is not releasing the ports in the same way windows 2000 does, and when I try
and connect the second time I get a timeout because there is no available
ports left to connect with. If I wait a minute of so the ports have timed
out and cleared, and the query can run again.

If this was the case however I would expect a massive amount of information
on it as the querys we are running are quite basic in comparison to the
industry, so other people must have seen this problem on a bigger scale if
that was correct.

>
> > Run-time Error '-2147467259 (80004005)':
> > [Microsoft][ODBC SQL Server Driver] Timeout expired
> If you get this on the Win2K3 server but not the Win2K server, I wonder if
> the query is timing out on the Win2K3 server. Have you tried executing the
> same query on the same dataset from the Win2K and Win2K3 server from Query
> Analyser and comparing the timings and query plans?

I will try this now.

Thanks so much for all your help.

Best Regards.

Relevant Pages

  • RE: serial ports?
    ... including the client file system, smart cards, audio, serial ... ports, printers, and the clipboard. ... terminal services only can redirect the serial ports to the Terminal ... redirected to the Terminal Server. ...
    (microsoft.public.windows.terminal_services)
  • Re: Exchange ports through firewall?
    ... I take there are too many ports to open if we use the full client method? ... in this case if you want to provide clients RPC/MAPI access across a firewall, you can restrict clients and server to a narrower range of ports, or alternatively open a lot more ports on the firewall. ...
    (microsoft.public.exchange.admin)
  • Re: Microsoft FTP and Linksys BEFSR41 (okay, Kerio 2.1.5 also)
    ... configure PASV on your server, and ask people to use PASV ... If the client has a router which isnt well implemented for FTP ... it will drop incoming connections on high ports ...
    (comp.security.firewalls)
  • Blocking Morpheus
    ... the server here is linux. ... With Morpheus and it client side. ... to be using random ports to connect in. ...
    (comp.security.firewalls)
  • Re: How to setup Manual printer redirection
    ... The client must be ... > connected to the terminal server during manual redirection. ... Ports for all clients currently connected ...
    (microsoft.public.windows.terminal_services)