I have a server with sbs2003 and isa, where is my sql
database.
I need to connect some clients to my database over the
internet.
What sould I do.
Thanks
Hi,
See the old posts:-
http://groups.google.co.in/groups?q=...+internet&hl=e
n&lr=&ie=UTF-8&selm=%23lFK03dOEHA.3924%40TK2MSFTNGP09.phx.gbl&r num=4
As well as see the below links
Q185638 How to Set Up Server Proxy with SQL Server
http://support.microsoft.com/support.../q185/6/38.asp
Q177153 Additional Proxy Server 2.0 Configurations
http://support.microsoft.com/support.../q177/1/53.asp
Q287932 INF: TCP Ports for Communication to SQL Server Through Firewall
http://support.microsoft.com/support.../q287/9/32.asp
Thanks
Hari
MCDBA
"Luis" <info@.luislei.com.pt> wrote in message
news:2381401c45e8c$d2c1b8c0$a401280a@.phx.gbl...
> I have a server with sbs2003 and isa, where is my sql
> database.
> I need to connect some clients to my database over the
> internet.
> What sould I do.
> Thanks
Showing posts with label clients. Show all posts
Showing posts with label clients. Show all posts
Sunday, March 25, 2012
connecting to sql over the internet
I have a server with sbs2003 and isa, where is my sql
database.
I need to connect some clients to my database over the
internet.
What sould I do.
ThanksHi,
See the old posts:-
http://groups.google.co.in/groups?q...r+internet&hl=e
n&lr=&ie=UTF-8&selm=%23lFK03dOEHA.3924%40TK2MSFTNGP09.phx.gbl&rnum=4
As well as see the below links
Q185638 How to Set Up Server Proxy with SQL Server
http://support.microsoft.com/suppor...s/q185/6/38.asp
Q177153 Additional Proxy Server 2.0 Configurations
http://support.microsoft.com/suppor...s/q177/1/53.asp
Q287932 INF: TCP Ports for Communication to SQL Server Through Firewall
http://support.microsoft.com/suppor...s/q287/9/32.asp
Thanks
Hari
MCDBA
"Luis" <info@.luislei.com.pt> wrote in message
news:2381401c45e8c$d2c1b8c0$a401280a@.phx
.gbl...
> I have a server with sbs2003 and isa, where is my sql
> database.
> I need to connect some clients to my database over the
> internet.
> What sould I do.
> Thanks
database.
I need to connect some clients to my database over the
internet.
What sould I do.
ThanksHi,
See the old posts:-
http://groups.google.co.in/groups?q...r+internet&hl=e
n&lr=&ie=UTF-8&selm=%23lFK03dOEHA.3924%40TK2MSFTNGP09.phx.gbl&rnum=4
As well as see the below links
Q185638 How to Set Up Server Proxy with SQL Server
http://support.microsoft.com/suppor...s/q185/6/38.asp
Q177153 Additional Proxy Server 2.0 Configurations
http://support.microsoft.com/suppor...s/q177/1/53.asp
Q287932 INF: TCP Ports for Communication to SQL Server Through Firewall
http://support.microsoft.com/suppor...s/q287/9/32.asp
Thanks
Hari
MCDBA
"Luis" <info@.luislei.com.pt> wrote in message
news:2381401c45e8c$d2c1b8c0$a401280a@.phx
.gbl...
> I have a server with sbs2003 and isa, where is my sql
> database.
> I need to connect some clients to my database over the
> internet.
> What sould I do.
> Thanks
Monday, March 19, 2012
Connecting to MSDE via client
Hope someone can explain why this happened.
I installed MSDE on a Winxp workstation.
I then setup clients to access MSDE via TCP/IP using the (Static) IP Address
address of the workstation.
Connection successful
I then removed MSDE2000 and installed MSDE2000 sp3a
Went I to connect to MSDE via TCP/IP and could not connect using the IP
When I changed to The machine name I could connect to MSDE2000
Anyone with any idea.
Server was winXP and workstations Win98 and Win08se.
Regards
Jeff
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003Jeff Williams wrote:
> Hope someone can explain why this happened.
> I installed MSDE on a Winxp workstation.
> I then setup clients to access MSDE via TCP/IP using the (Static) IP
> Address address of the workstation.
> Connection successful
> I then removed MSDE2000 and installed MSDE2000 sp3a
> Went I to connect to MSDE via TCP/IP and could not connect using the
> IP When I changed to The machine name I could connect to MSDE2000
> Anyone with any idea.
> Server was winXP and workstations Win98 and Win08se.
> Regards
> Jeff
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003
Check that the Server (via sql server network utility) is configured to
use TCP/IP. Also check your client is configured like this too (client
network utility).
Br,
Mark Broadbent
mcdba , mcse+i
=============
I installed MSDE on a Winxp workstation.
I then setup clients to access MSDE via TCP/IP using the (Static) IP Address
address of the workstation.
Connection successful
I then removed MSDE2000 and installed MSDE2000 sp3a
Went I to connect to MSDE via TCP/IP and could not connect using the IP
When I changed to The machine name I could connect to MSDE2000
Anyone with any idea.
Server was winXP and workstations Win98 and Win08se.
Regards
Jeff
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003Jeff Williams wrote:
> Hope someone can explain why this happened.
> I installed MSDE on a Winxp workstation.
> I then setup clients to access MSDE via TCP/IP using the (Static) IP
> Address address of the workstation.
> Connection successful
> I then removed MSDE2000 and installed MSDE2000 sp3a
> Went I to connect to MSDE via TCP/IP and could not connect using the
> IP When I changed to The machine name I could connect to MSDE2000
> Anyone with any idea.
> Server was winXP and workstations Win98 and Win08se.
> Regards
> Jeff
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003
Check that the Server (via sql server network utility) is configured to
use TCP/IP. Also check your client is configured like this too (client
network utility).
Br,
Mark Broadbent
mcdba , mcse+i
=============
Connecting to MSDE from client
We are using MSDE as a cheap datastore in our client/server app. MSDE is installed only on the server and both the server and the clients connect to it from their machines.
When we deploy on Windows XP, we see that our code running on the server can access MSDE, but our code running on a client machine cannot connect to MSDE.
The clients are able to connect on Windows 2000 ... can anyone help me understand this ?
Thanks in advance,
ethan
MSDE only allow local access.Wednesday, March 7, 2012
Connecting to a Clients SQL server
I am not sure if its possible, hopefully it is. I would like to create a custom page for one of my clients to log into and access information from their SQL server. If I have all the connection information, i.e user id and password etc. Can this be done. I know how to connect to an SQL server locally. If anyone can give me a point in the right direction, it would be greatly appreciative.
If this is possible, I am looking at adding a button on this page to allow the client to transfer records that meet specific criteria in a column in their database into a designated database on my server.
Thanks for any help.If your server can access their SQL Server, sure. Ask them for the TCP/IP connection information, and if you can see their server, you should be able to pull it off.
The difference from what you may be doing locally, is that instead of server=(local), you'll likely have the IP address of their server, and you may be using Windows Authentication locally, but you'll use SQL security to connect to their machine.
Regards,
Xander
Sunday, February 19, 2012
Connecting Clients
What are the prerequisites for Win2K and WinXP Clients to
connect to a MSDE server?
I have installed MDAC2.8, is there anything else they need?
Hi
Nothing else. XP has MDAC 2.8 already in it. All low level connectivity is
there once MDAC is installed.
Regards
Mike
"Kon" wrote:
> What are the prerequisites for Win2K and WinXP Clients to
> connect to a MSDE server?
> I have installed MDAC2.8, is there anything else they need?
>
connect to a MSDE server?
I have installed MDAC2.8, is there anything else they need?
Hi
Nothing else. XP has MDAC 2.8 already in it. All low level connectivity is
there once MDAC is installed.
Regards
Mike
"Kon" wrote:
> What are the prerequisites for Win2K and WinXP Clients to
> connect to a MSDE server?
> I have installed MDAC2.8, is there anything else they need?
>
Friday, February 17, 2012
Connecting a webpage to SQL
I would like to know how to go about doing this.
I have a table ClientInfo in SQL 2k. I want the customer
service dept to be able to add new clients and search for
ones to edit. I want other groups to be able to only view
client info read-only.
1. I assume creating a webpage is probably better than
an .adp file?
2. If I do a webpage, how do I deal with the
permissions? Should I create a login table and add all
the users/pwd in there and set the level of security that
way? Or is there a way to base it off of Windows active
directory groups?
Thanks.
You can set the security with in SQL Server based on the NT users. You can
create a view that has the data that you wan the users to view and then
only give select permissions to the to those users.
In other words use teh security mechnism within SQL Server to set the
security.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks!
I use the dsnless connection string for trusted_connection
to base ithe permissions on the user.
However, the windows login box does pop up for them to
enter in username/pwd/domain.
Is there a way that sql grabs the user info automatically
and set the perms that way?
If I have a default page and links to an edit page, is
there a way to use the user info to disallow certain
people from entering that page?
Ngan
>--Original Message--
>You can set the security with in SQL Server based on the
NT users. You can
>create a view that has the data that you wan the users to
view and then
>only give select permissions to the to those users.
>In other words use teh security mechnism within SQL
Server to set the
>security.
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>
I have a table ClientInfo in SQL 2k. I want the customer
service dept to be able to add new clients and search for
ones to edit. I want other groups to be able to only view
client info read-only.
1. I assume creating a webpage is probably better than
an .adp file?
2. If I do a webpage, how do I deal with the
permissions? Should I create a login table and add all
the users/pwd in there and set the level of security that
way? Or is there a way to base it off of Windows active
directory groups?
Thanks.
You can set the security with in SQL Server based on the NT users. You can
create a view that has the data that you wan the users to view and then
only give select permissions to the to those users.
In other words use teh security mechnism within SQL Server to set the
security.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thanks!
I use the dsnless connection string for trusted_connection
to base ithe permissions on the user.
However, the windows login box does pop up for them to
enter in username/pwd/domain.
Is there a way that sql grabs the user info automatically
and set the perms that way?
If I have a default page and links to an edit page, is
there a way to use the user info to disallow certain
people from entering that page?
Ngan
>--Original Message--
>You can set the security with in SQL Server based on the
NT users. You can
>create a view that has the data that you wan the users to
view and then
>only give select permissions to the to those users.
>In other words use teh security mechnism within SQL
Server to set the
>security.
>Rand
>This posting is provided "as is" with no warranties and
confers no rights.
>.
>
Tuesday, February 14, 2012
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.
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.
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.
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.
connect via QA with windows auth without joining domain
Hi, I'm using my laptop to connect to a client's internal network. I'd
like to connect to their SqlServer database using Query Analyzer,
Enterprise Manager, osql, etc... They only have Windows Authentication
enabled (they won't change this setting).
When I try to connect in QA I get the authentication failed for user
(null) error.
They've given me a domain login to use when connecting to their
database, but I'm not sure how to use it without logging on to windows
as that user.
I'd prefer not to make my laptop part of their domain. I'd rather use
my regular (local machine) login so I can access my installed programs
and files.
Any thoughts on how I should connect?
Thanks!
Try mapping a drive to a share on a machine in that domain
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<dinosaur8000@.yahoo.com> wrote in message
news:1133316094.691249.88290@.z14g2000cwz.googlegro ups.com...
> Hi, I'm using my laptop to connect to a client's internal network. I'd
> like to connect to their SqlServer database using Query Analyzer,
> Enterprise Manager, osql, etc... They only have Windows Authentication
> enabled (they won't change this setting).
> When I try to connect in QA I get the authentication failed for user
> (null) error.
> They've given me a domain login to use when connecting to their
> database, but I'm not sure how to use it without logging on to windows
> as that user.
> I'd prefer not to make my laptop part of their domain. I'd rather use
> my regular (local machine) login so I can access my installed programs
> and files.
> Any thoughts on how I should connect?
> Thanks!
>
|||I've done that. I mapped a drive to the machine hosting the SqlServer,
actually. I supply the domain login and I'm able to connect to the
share just fine. However, when I try to connect to the DB through QA or
Enterprise Manager, it doesn't work. Am I missing a step?
Tibor Karaszi wrote:[vbcol=seagreen]
> Try mapping a drive to a share on a machine in that domain
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> <dinosaur8000@.yahoo.com> wrote in message
> news:1133316094.691249.88290@.z14g2000cwz.googlegro ups.com...
like to connect to their SqlServer database using Query Analyzer,
Enterprise Manager, osql, etc... They only have Windows Authentication
enabled (they won't change this setting).
When I try to connect in QA I get the authentication failed for user
(null) error.
They've given me a domain login to use when connecting to their
database, but I'm not sure how to use it without logging on to windows
as that user.
I'd prefer not to make my laptop part of their domain. I'd rather use
my regular (local machine) login so I can access my installed programs
and files.
Any thoughts on how I should connect?
Thanks!
Try mapping a drive to a share on a machine in that domain
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
<dinosaur8000@.yahoo.com> wrote in message
news:1133316094.691249.88290@.z14g2000cwz.googlegro ups.com...
> Hi, I'm using my laptop to connect to a client's internal network. I'd
> like to connect to their SqlServer database using Query Analyzer,
> Enterprise Manager, osql, etc... They only have Windows Authentication
> enabled (they won't change this setting).
> When I try to connect in QA I get the authentication failed for user
> (null) error.
> They've given me a domain login to use when connecting to their
> database, but I'm not sure how to use it without logging on to windows
> as that user.
> I'd prefer not to make my laptop part of their domain. I'd rather use
> my regular (local machine) login so I can access my installed programs
> and files.
> Any thoughts on how I should connect?
> Thanks!
>
|||I've done that. I mapped a drive to the machine hosting the SqlServer,
actually. I supply the domain login and I'm able to connect to the
share just fine. However, when I try to connect to the DB through QA or
Enterprise Manager, it doesn't work. Am I missing a step?
Tibor Karaszi wrote:[vbcol=seagreen]
> Try mapping a drive to a share on a machine in that domain
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> <dinosaur8000@.yahoo.com> wrote in message
> news:1133316094.691249.88290@.z14g2000cwz.googlegro ups.com...
Sunday, February 12, 2012
Connect to SQL Server through an cable modem client
Hi, I'm connecting some clients via Internet to a named instance of SQLServer
(port 1433). All the clients conected to internet via DSL works just great,
but all the clients connected to internet via an cable ISP, just can't find
the server.
I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
the cable users connect to my sql server using a different port, and the dsl
users still using the 1433? ... or what collateral damage could happen if I
just change the current port on the remote server?
If you change the port on which the SQL instance is listening, just make sure
that you also change the port to which the clients are configured to connect.
I'm assuming that you are specifying the port number in your connection
string.
Linchi
"Ruben" wrote:
> Hi, I'm connecting some clients via Internet to a named instance of SQLServer
> (port 1433). All the clients conected to internet via DSL works just great,
> but all the clients connected to internet via an cable ISP, just can't find
> the server.
> I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
> the cable users connect to my sql server using a different port, and the dsl
> users still using the 1433? ... or what collateral damage could happen if I
> just change the current port on the remote server?
|||Hi Linchi, I'm not specifying the port in the connection string, I'm setting
a Server Alias (with the client network utility) and the port is set to
determine it dinamically ... and reading your post I assume there isn't any
problem if I change the port at the main server, right?
"Linchi Shea" wrote:
[vbcol=seagreen]
> If you change the port on which the SQL instance is listening, just make sure
> that you also change the port to which the clients are configured to connect.
> I'm assuming that you are specifying the port number in your connection
> string.
> Linchi
> "Ruben" wrote:
|||You can change the port that the SQL instance is listening on, or you can
specify the port after the server name (or the IP address) after a comma. You
can also specify the port number when you specify your alias. If the UDP port
1434 is blocked, you may not have a choice but to specify the port number on
the connection string. Note that when the SQL instance is the deafult
instance, the default port of 1433 will be tried evne if you don't specify a
port number.
Linchi
"Ruben" wrote:
[vbcol=seagreen]
> Hi Linchi, I'm not specifying the port in the connection string, I'm setting
> a Server Alias (with the client network utility) and the port is set to
> determine it dinamically ... and reading your post I assume there isn't any
> problem if I change the port at the main server, right?
> "Linchi Shea" wrote:
(port 1433). All the clients conected to internet via DSL works just great,
but all the clients connected to internet via an cable ISP, just can't find
the server.
I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
the cable users connect to my sql server using a different port, and the dsl
users still using the 1433? ... or what collateral damage could happen if I
just change the current port on the remote server?
If you change the port on which the SQL instance is listening, just make sure
that you also change the port to which the clients are configured to connect.
I'm assuming that you are specifying the port number in your connection
string.
Linchi
"Ruben" wrote:
> Hi, I'm connecting some clients via Internet to a named instance of SQLServer
> (port 1433). All the clients conected to internet via DSL works just great,
> but all the clients connected to internet via an cable ISP, just can't find
> the server.
> I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
> the cable users connect to my sql server using a different port, and the dsl
> users still using the 1433? ... or what collateral damage could happen if I
> just change the current port on the remote server?
|||Hi Linchi, I'm not specifying the port in the connection string, I'm setting
a Server Alias (with the client network utility) and the port is set to
determine it dinamically ... and reading your post I assume there isn't any
problem if I change the port at the main server, right?
"Linchi Shea" wrote:
[vbcol=seagreen]
> If you change the port on which the SQL instance is listening, just make sure
> that you also change the port to which the clients are configured to connect.
> I'm assuming that you are specifying the port number in your connection
> string.
> Linchi
> "Ruben" wrote:
|||You can change the port that the SQL instance is listening on, or you can
specify the port after the server name (or the IP address) after a comma. You
can also specify the port number when you specify your alias. If the UDP port
1434 is blocked, you may not have a choice but to specify the port number on
the connection string. Note that when the SQL instance is the deafult
instance, the default port of 1433 will be tried evne if you don't specify a
port number.
Linchi
"Ruben" wrote:
[vbcol=seagreen]
> Hi Linchi, I'm not specifying the port in the connection string, I'm setting
> a Server Alias (with the client network utility) and the port is set to
> determine it dinamically ... and reading your post I assume there isn't any
> problem if I change the port at the main server, right?
> "Linchi Shea" wrote:
Connect to SQL Server through an cable modem client
Hi, I'm connecting some clients via Internet to a named instance of SQLServe
r
(port 1433). All the clients conected to internet via DSL works just great,
but all the clients connected to internet via an cable ISP, just can't find
the server.
I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
the cable users connect to my sql server using a different port, and the dsl
users still using the 1433? ... or what collateral damage could happen if I
just change the current port on the remote server?If you change the port on which the SQL instance is listening, just make sur
e
that you also change the port to which the clients are configured to connect
.
I'm assuming that you are specifying the port number in your connection
string.
Linchi
"Ruben" wrote:
> Hi, I'm connecting some clients via Internet to a named instance of SQLSer
ver
> (port 1433). All the clients conected to internet via DSL works just great
,
> but all the clients connected to internet via an cable ISP, just can't fi
nd
> the server.
> I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
> the cable users connect to my sql server using a different port, and the d
sl
> users still using the 1433? ... or what collateral damage could happen if
I
> just change the current port on the remote server?|||Hi Linchi, I'm not specifying the port in the connection string, I'm setting
a Server Alias (with the client network utility) and the port is set to
determine it dinamically ... and reading your post I assume there isn't any
problem if I change the port at the main server, right?
"Linchi Shea" wrote:
[vbcol=seagreen]
> If you change the port on which the SQL instance is listening, just make s
ure
> that you also change the port to which the clients are configured to conne
ct.
> I'm assuming that you are specifying the port number in your connection
> string.
> Linchi
> "Ruben" wrote:
>|||You can change the port that the SQL instance is listening on, or you can
specify the port after the server name (or the IP address) after a comma. Yo
u
can also specify the port number when you specify your alias. If the UDP por
t
1434 is blocked, you may not have a choice but to specify the port number on
the connection string. Note that when the SQL instance is the deafult
instance, the default port of 1433 will be tried evne if you don't specify a
port number.
Linchi
"Ruben" wrote:
[vbcol=seagreen]
> Hi Linchi, I'm not specifying the port in the connection string, I'm setti
ng
> a Server Alias (with the client network utility) and the port is set to
> determine it dinamically ... and reading your post I assume there isn't an
y
> problem if I change the port at the main server, right?
> "Linchi Shea" wrote:
>
r
(port 1433). All the clients conected to internet via DSL works just great,
but all the clients connected to internet via an cable ISP, just can't find
the server.
I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
the cable users connect to my sql server using a different port, and the dsl
users still using the 1433? ... or what collateral damage could happen if I
just change the current port on the remote server?If you change the port on which the SQL instance is listening, just make sur
e
that you also change the port to which the clients are configured to connect
.
I'm assuming that you are specifying the port number in your connection
string.
Linchi
"Ruben" wrote:
> Hi, I'm connecting some clients via Internet to a named instance of SQLSer
ver
> (port 1433). All the clients conected to internet via DSL works just great
,
> but all the clients connected to internet via an cable ISP, just can't fi
nd
> the server.
> I saw some of the cable ISPs block the 1433 and 1434 ports...it's possible
> the cable users connect to my sql server using a different port, and the d
sl
> users still using the 1433? ... or what collateral damage could happen if
I
> just change the current port on the remote server?|||Hi Linchi, I'm not specifying the port in the connection string, I'm setting
a Server Alias (with the client network utility) and the port is set to
determine it dinamically ... and reading your post I assume there isn't any
problem if I change the port at the main server, right?
"Linchi Shea" wrote:
[vbcol=seagreen]
> If you change the port on which the SQL instance is listening, just make s
ure
> that you also change the port to which the clients are configured to conne
ct.
> I'm assuming that you are specifying the port number in your connection
> string.
> Linchi
> "Ruben" wrote:
>|||You can change the port that the SQL instance is listening on, or you can
specify the port after the server name (or the IP address) after a comma. Yo
u
can also specify the port number when you specify your alias. If the UDP por
t
1434 is blocked, you may not have a choice but to specify the port number on
the connection string. Note that when the SQL instance is the deafult
instance, the default port of 1433 will be tried evne if you don't specify a
port number.
Linchi
"Ruben" wrote:
[vbcol=seagreen]
> Hi Linchi, I'm not specifying the port in the connection string, I'm setti
ng
> a Server Alias (with the client network utility) and the port is set to
> determine it dinamically ... and reading your post I assume there isn't an
y
> problem if I change the port at the main server, right?
> "Linchi Shea" wrote:
>
Subscribe to:
Posts (Atom)