RE: Connect via ServerName but not by IP or FQDN
- From: v-mingqc@xxxxxxxxxxxxxxxxxxxx (Michael Cheng [MSFT])
- Date: Tue, 18 Oct 2005 03:47:14 GMT
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.
.
- Follow-Ups:
- Re: Connect via ServerName but not by IP or FQDN
- From: Brett Wickard
- Re: Connect via ServerName but not by IP or FQDN
- References:
- Connect via ServerName but not by IP or FQDN
- From: Brett Wickard
- Connect via ServerName but not by IP or FQDN
- Prev by Date: Re: Sept CTP 2005 Mange. Studio can't connect to MSOLAP "actively
- Next by Date: Re: Can't connect to SQL server after hibernating
- Previous by thread: Connect via ServerName but not by IP or FQDN
- Next by thread: Re: Connect via ServerName but not by IP or FQDN
- Index(es):
Relevant Pages
|