Easysoft ODBC-SQL Server Driver

Why do I get error "Client unable to establish connection: 'Failed to get datagram from socket'"?

The Easysoft ODBC-SQL Server Driver uses the SQL Server Browser or the SQL Server 2000 listener service to find out what TCP port SQL Server is listening on. If the SQL Server Browser or listener service is not running and active, the Easysoft ODBC-SQL Server Driver will be unable to open a connection for this purpose and the "Failed to get datagram from socket" error displays.

On the SQL Server machine, "SQL Server Browser" will be listed in the output of the net start command, if the SQL Server Browser is running. If net start shows that the SQL Server Browser service is running, the service may not be active. In the SQL Server Configuration Manager, the Active option must be set to "Yes" in the Advanced SQL Server Browser property tab. (The SQL Server Browser service must be restarted before any change to this setting takes effect.)

If you are connecting to SQL Server through a firewall, the firewall needs to allow connections through:

• The SQL Browser UDP port, 1434.
• The TCP port that the SQL Server instance is listening on.

If UDP port 1434 is not open, the firewall will block the connection when the Easysoft ODBC-SQL Server Driver attempts to discover the SQL Server port and the 'Failed to get datagram from socket' will display.

Because the SQL Server Browser or listener accepts unauthenticated UDP requests, it may have been turned off as a security measure, and your database administrator will have configured each SQL Server instance to listen on a specific TCP port. You need to specify this port number with the Port setting. For example, if SQL Server is listening on port 1500, add this line to the data source in odbc.ini:

Port = 1500

The "Failed to get datagram from socket" error also displays if you try to connect to a hidden SQL Server instance. You need to specify the port that the hidden instance is listening even though the SQL Server Browser or listener may be running.

Applies To

• Products
  • Easysoft ODBC-SQL Server Driver

Knowledge Base Feedback

* Did this content help you?

Yes No Maybe

* Please select one option based on your first choice:

I'm very satisfied I think it will help, but I haven't tried it yet It is helpful, but I need more information It is helpful, but hard to understand Seemed relevant in search results, but didn't help me The information is incorrect The page contains one or more broken links

Suggest new content or let us know how we can improve this content:

(* Required Fields)

• About Easysoft

• Contact Us
• About Us
• Clients
• Upgrade Offer
• Blog
• Careers

• Products

• ODBC Drivers
• JDBC Drivers
• Bridges and Gateways
• In Development

• Services

• Consultancy
• Training
• Custom Development

• Licensing

• Product Licenses
• Prices

• Support

• Support Home
• Solution Wizard
• Getting Started Guides
• User Guides
• Knowledge Base

• Search

• Easysoft.com
• Documentation
• Knowledge Base

• Popular Resources

• Developer Area
• Client Applications

• Legal

• Privacy Statement

© 1993 - 2024 Easysoft Limited. All rights reserved. Oracle® is a registered trademark of Oracle® Corporation and/or its affiliates. Other trademarks and registered trademarks appearing on easysoft.com are the property of their respective owners.

• 
• 
• 
•