Hey, kids:
We have a couple of development workstations that use ODBC to access a SQL
Server on a third machine. Access works fine from the dusty old machine we
keep around as a spare, but just stopped working from the shiny Lenovo T590
the other coder uses and has worked fine for years. Using any one of the
three 32-bit drivers installed on the machine, we can use an old or create
a new System DSN, specify the server machine (SERVERNAME\SQLEXPRESS) and
use SQL Server Authentication to access the machine. Clicking on the dialog
to specify a default database hangs for a long time and then returns an
error, as does the "Test" option on the last page of the ODBC setup.
One the dusty old machine, using identical login credentials, it works fine.
Have dropped firewalls on both the server and workstations, no change.
No recent software installs, other than the Windows Updates ("that won't
break anything, will it?" is Laura's funniest joke, first told in... 1997?)
Something's changed, clearly, and it's likely one of us flailing at the
Network settings that threw it off, but I don't see it. Any ideas on what
to try next?
Local LAN is just a bunch of machines, no domain, Active Directory,
workgroup or HomeGroup set up.
All boxes can ping each other, so basic name resolution is working fine.
Any and all ideas welcomed!
Far more information than you need, included below:
Same machines on same LAN, no changes.
1. Old machine: 64-bit Windows 10 Pro, version 1902, Build 18362.1016,
Intel Core 2 1.86GHz, 8 Gb RAM Dell Optiplex
2. New Machine: 64-bit Windows 10 Pro, same version and build, Lenovo
T590, Intel i7-8665U 1.90/2.11 GHz, 16Gb RAM
3. Server is an HP Pro 3005 running 32-bit Windows 10 Pro, version 1909,
Build 18363.1082, an AMD Athlon II X2 245 2.90 GHz with 8Gb RAM, (3.25
usable due to 32-bit OS)
>From the ThinkPad:
Microsoft SQL Server Native Client Version 11.00.2100
Data Source Name: XXXXXX
Data Source Description: XXXXXX
Server: SERVERNAME\SQLEXPRESS
Use Integrated Security: No
Database: XX_XXX
Language: (Default)
Data Encryption: No
Trust Server Certificate: No
Multiple Active Result Sets(MARS): No
Mirror Server:
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Regional Settings: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes
Microsoft SQL Server Native Client Version 11.00.2100
Running connectivity tests...
Attempting connection
[Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces:
Error Locating Server/Instance Specified [xFFFFFFFF].
[Microsoft][SQL Server Native Client 11.0]Login timeout expired
[Microsoft][SQL Server Native Client 11.0]A network-related or
instance-specific error has occurred while establishing a connection to SQL
Server. Server is not found or not accessible. Check if instance name is
correct and if SQL Server is configured to allow remote connections. For
more information see SQL Server Books Online.
TESTS FAILED!
With the 10.0 driver, I get a timeout message, SQL State '08001' and SQL
error 10060, "A connection attempt failed because the connected party did
not properly respond after a period of time, or established connection
failed because the connected host has failed to respond." (Typos mine,
retyping from screenshot)
Halp.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/cacw6n4t6wcf5xz_hdclj-vugdurfyo5ztz6mhuxz9pbx6mt...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
