Connecting to SQL Server 2000 Via Internet

Hi guys,

I would like to know how to connect SQL Server-2000 via Internet. I have software developed by VB it is working under Intranet but I need to have it's database connected Via internet remotely.

Thanks

Quote:

Originally Posted by riyazrasheed1234

Hi guys,

I would like to know how to connect SQL Server-2000 via Internet. I have software developed by VB it is working under Intranet but I need to have it's database connected Via internet remotely.

Thanks

This should be the same process as before. Are you having an issue? What errors are you getting?|||

Quote:

Originally Posted by Motoma

This should be the same process as before. Are you having an issue? What errors are you getting?

Still I did not tried. I just trying to find code for the Connection!sqlsql

connecting to sql server (within windows domain) through linux?

Hi,

I'm planning to develop a small intranet to provide our organization
with documents online. I've decided to do this using jsp/servlets
using a tomcat server. For an operating system, I have chosen red hat
linux. However, I'd like to keep a small database on a sql server as
a datasource. However, this sql server is already part of our
organization's windows domain. I suspect I'll need to configure samba
so that other terminals on the windows domain will be able to reach
the intranet. What's the best manner in which to connect my linux
servlets to this sql server database? I suspect this may be
difficult, considering the sql server exists within a windows domain,
but as a beginner, what do I know. Perhaps someone could point me in
the right direction.Hi

You can use the JDBC driver to communicate with your SQL Server and use SQL
Server authentication to access the server. Samba is not needed at all this
may be a way to connect to an access database but SQL Server is a completely
different product.

John
"Dan" <danhicks333@.gmail.com> wrote in message
news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> Hi,
> I'm planning to develop a small intranet to provide our organization
> with documents online. I've decided to do this using jsp/servlets
> using a tomcat server. For an operating system, I have chosen red hat
> linux. However, I'd like to keep a small database on a sql server as
> a datasource. However, this sql server is already part of our
> organization's windows domain. I suspect I'll need to configure samba
> so that other terminals on the windows domain will be able to reach
> the intranet. What's the best manner in which to connect my linux
> servlets to this sql server database? I suspect this may be
> difficult, considering the sql server exists within a windows domain,
> but as a beginner, what do I know.Perhapssomeonecouldpointmein
> the right direction.|||Dan (danhicks333@.gmail.com) writes:
> I'm planning to develop a small intranet to provide our organization
> with documents online. I've decided to do this using jsp/servlets
> using a tomcat server. For an operating system, I have chosen red hat
> linux. However, I'd like to keep a small database on a sql server as
> a datasource. However, this sql server is already part of our
> organization's windows domain. I suspect I'll need to configure samba
> so that other terminals on the windows domain will be able to reach
> the intranet. What's the best manner in which to connect my linux
> servlets to this sql server database? I suspect this may be
> difficult, considering the sql server exists within a windows domain,
> but as a beginner, what do I know. Perhaps someone could point me in
> the right direction.

I have never connected to SQL Server from Unix myself, but I happen to
maintain a page which summarizes the various options. Look at:
http://www.sommarskog.se/mssqlperl/unix.html

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||The SQL server I want to connect to does not have a public IP address.
I connect to this server from my other web server (part of the
windows domain)using the server name (treadstonesql). My thinking was
that if samba is configured correctly, I could connect to it the same
way my web server does. Does this help?

"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:<414352bf$0$4664$afc38c87@.news.easynet.co.uk>...
> Hi
> You can use the JDBC driver to communicate with your SQL Server and use SQL
> Server authentication to access the server. Samba is not needed at all this
> may be a way to connect to an access database but SQL Server is a completely
> different product.
> John
> "Dan" <danhicks333@.gmail.com> wrote in message
> news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> > Hi,
> > I'm planning to develop a small intranet to provide our organization
> > with documents online. I've decided to do this using jsp/servlets
> > using a tomcat server. For an operating system, I have chosen red hat
> > linux. However, I'd like to keep a small database on a sql server as
> > a datasource. However, this sql server is already part of our
> > organization's windows domain. I suspect I'll need to configure samba
> > so that other terminals on the windows domain will be able to reach
> > the intranet. What's the best manner in which to connect my linux
> > servlets to this sql server database? I suspect this may be
> > difficult, considering the sql server exists within a windows domain,
> > but as a beginner, what do I know.Perhapssomeonecouldpointmein
> > the right direction.|||Hi

The IPaddress does not have to be a public one (in fact it would be better
if it wasn't) The IP Address can be used when connecting instead of using a
lookup, you will need to set up the firewall rules so that you can talk on
the right ports (not necessarily the default ones!) between the two
machines.

I would not expect your second web server to be part of the internal domain,
this may mean that your whole domain is compromised if the web server is
compromised.

John

"Dan" <danhicks333@.gmail.com> wrote in message
news:b03c5d2b.0409120659.618cc1ae@.posting.google.c om...
> The SQL server I want to connect to does not have a public IP address.
> I connect to this server from my other web server (part of the
> windows domain)using the server name (treadstonesql). My thinking was
> that if samba is configured correctly, I could connect to it the same
> way my web server does. Does this help?
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:<414352bf$0$4664$afc38c87@.news.easynet.co.uk>...
> > Hi
> > You can use the JDBC driver to communicate with your SQL Server and use
SQL
> > Server authentication to access the server. Samba is not needed at all
this
> > may be a way to connect to an access database but SQL Server is a
completely
> > different product.
> > John
> > "Dan" <danhicks333@.gmail.com> wrote in message
> > news:b03c5d2b.0409111105.18d75023@.posting.google.c om...
> > > Hi,
> > > > I'm planning to develop a small intranet to provide our organization
> > > with documents online. I've decided to do this using jsp/servlets
> > > using a tomcat server. For an operating system, I have chosen red hat
> > > linux. However, I'd like to keep a small database on a sql server as
> > > a datasource. However, this sql server is already part of our
> > > organization's windows domain. I suspect I'll need to configure samba
> > > so that other terminals on the windows domain will be able to reach
> > > the intranet. What's the best manner in which to connect my linux
> > > servlets to this sql server database? I suspect this may be
> > > difficult, considering the sql server exists within a windows domain,
> > > but as a beginner, what do I know.Perhapssomeonecouldpointmein
> > > the right direction.

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.

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.