Connect via ServerName but not by IP or FQDN

How can I make it so that our intranet clients can connect to the SQLServer
via our FQDN? Our extranet clients work fine via that way, but once they go
behind the VPN, the FQDN doesn't work. Also for onsite intranet clients we
can connect fine via server name, but not via IP address or FQDN.
(connecting via the ODBC SQL Server Driver in the Data Source Administrator)Hi Brett,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you would like to connect to your SQL
Server with FQDN name via VPN. If I have misunderstood your concern, please
feel free to point it out.
Based on my knowledge, if you connect via VPN, your client will be on the
intranet and please make sure your intranet DNS server could resolve that
FQDN. What do your intranet clients used to connect the SQL Server? server
name, ip address or FQDN name?
Please connect via VPN and perform the test below
1. PING with FQDN name and IP address (make sure you are using it's
intranet IP address)
2. telnet <FQDN name or IP address> <Port number, usually 1433>
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||I'd like my intranet clients (and extranet clients) to be able to connect
using the FQDN -- but you're correct they cannot resolve that name right
now on the intranet (or if behind the VPN). Why would that be? They can
ping the www.mydomain.com, but if I use www.mydomain.com as the server name,
it isn't resolved. How can I get it to resolve the FQDN for a SQL Server
ODBC connection?
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:7H$Voa50FHA.3328@.TK2MSFTNGXA01.phx.gbl...
> Hi Brett,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood you would like to connect to your SQL
> Server with FQDN name via VPN. If I have misunderstood your concern,
> please
> feel free to point it out.
> Based on my knowledge, if you connect via VPN, your client will be on the
> intranet and please make sure your intranet DNS server could resolve that
> FQDN. What do your intranet clients used to connect the SQL Server? server
> name, ip address or FQDN name?
> Please connect via VPN and perform the test below
> 1. PING with FQDN name and IP address (make sure you are using it's
> intranet IP address)
> 2. telnet <FQDN name or IP address> <Port number, usually 1433>
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Brett,
It seems none of your intranet clients (no matter it conncet directly in
the intranet or connnect via VPN) will be able to connet the SQL Server by
FQDN name. If I have misunderstood your concern, please feel free to point
it out.
Please perform the steps below and let me know the results
1. check whether there are any Firewall settings in your intranet to see
whether it blocks the connection.
2. perform the command below and let me know the result
TELNET <FQDN name or IP address> <Port number, usually 1433>
3. What's the IP address return back from ping www.mydomain.com. Does it
match the IP address of your SQL Server?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.