Are both running the sql browser? And if so, on what ports? And are those ports
open?
Regards,
Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com
From: Sean Martin [mailto:seanmarti...@gmail.com]
Sent: Tuesday, May 25, 2010 7:27 PM
To: NT System Admin Issues
Subject: S
I'm connecting to the same SQL server and instance. Yes it is running the
sql browser and it is listening on 1434/udp.
- Sean
On Tue, May 25, 2010 at 3:29 PM, Michael B. Smith wrote:
> Are both running the sql browser? And if so, on what ports? And are those
> ports open?
>
>
>
> Regards,
>
>
>
o: NT System Admin Issues
Subject: Re: SQL Connectivity from DMZ
I'm connecting to the same SQL server and instance. Yes it is running the sql
browser and it is listening on 1434/udp.
- Sean
On Tue, May 25, 2010 at 3:29 PM, Michael B. Smith
mailto:mich...@smithcons.com>> wrote:
Are both
If you can connect using IP Address\Instance then SQL browser is working fine
(and the FW port for the instance as well). Instead, it seems you have a name
resolution (DNS) problem. Either check that name resolution is working
properly, or check that you didn't configure an SQL Alias at site A t
Verify that the clients are using the same/correct network library
(TCP/IP, Named Pipes) in ODBC>Client connectivity. I have experienced
issues connecting to a DMZ when the connection wasn't set to TCP/IP.
You can also check those settings on the server side and make sure the
matching protocols ar
Thanks for the tips guys. I have verified we're dealing with TCP/IP and not
named pipes. I'm not sure where DNS would play a role because I'm attempting
connection via IP address. Since the web servers reside in our DMZ, they
have no means of resolving the names of machines on our trusted network.
