Re: Remote ODBC connection to SQL Server 2005 Exp.
- From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
- Date: Mon, 27 Nov 2006 18:47:31 -0500
Try scanning your Win2K server from the Internet to see if the port 1433 is
visible:
http://www.pcflank.com/scanner1.htm
You can also make some tests from home using the ping or tracert command or
using a port scanning software like the following:
http://insecure.org/nmap/man/man-port-scanning-basics.html
Please take note that ping or tracert don't scan for a particular port and
will only test if a machine is globabally accessible from the internet by
the TCP/IP protocol. These two services can also be blocked by your *little
glitch*; so a failure reported by Ping or Tracert doesn't necessarily mean a
bad installation in your case. Probably that scanning the ports will give
you a better idea of your problem but Tracert can help you to define its
extent.
Other tests are available on the Internet.
--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Bruce Maston" <homebrew@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:46DCB577-131D-4C08-8D2B-01752DE9B15E@xxxxxxxxxxxxxxxx
I am unable to connect to a SQL Server 2005 Exp. server on a three computer
network at my office from my home computer.
1. I am using Access 2000 as the front end with SQL 2005 Exp. as the back
end. The office network consists of 2 XP pro machines with Access and a
third W2K machine acting as the SQL Exp. server. The home machine is XP
Home
Ed.
2. There is a Netgear RP 114 router for the office network. This router
has port forwarding set to forward any request via port 1433 to the SQL
server machine. I have also listed the SQL server machine as a "trusted
device" on the router meaning that it "has full access to the internet
without blocking of any resource."
3. I have completely uninstalled firewall software from the SQL server
machine. As far as I can figure, there is no additional firewall on the
router.
2. I am able to connect to the SQL from the two machines "inside" the
router on the office network, and my only problem is establishing the ODBC
connection from the home computer.
3. In SQL Server Configuration Manager, TCP/IP is enabled and running. In
SQL Server Surface Area Config., Local and Remote Connections with TCP/IP
is
enabled.
4. My TCP/IP protocol is set up with a fixed IP address.
You need to establish the connection through Start/Settings/Administrative
Tools/Data Sources (ODBC) and you are guided through 4 screens to
establish
the connection. I get to the screen where I have indicated to log on with
SQL authentication. I enter the WAN IP address for the router along with
the
userID and password. When I click "next," I get an error message:
Connection Failed ... Error: 10060 ... Error: 17 ... SQL server doesn't
exist or access denied.
You would expect this to be a firewall problem or router problem. The
router is old, but it has been working satisfactorily with an ODBC
connection
to an off-site SQL server prior to my attempt to use SQL Exp. on a machine
in
my office.
There is one other glitch. The fixed IP address for my router is "behind"
another router. A large company in my building has a T1 line, and they
have
set me up with my own IP address "behind" the router that is the IP
address
for the company. The IT person tells me this should make no difference,
as
my IP is different from theirs and stuff simply passes through. But I'm
not
so sure.
Does anyone have any additional thoughts on any of this? Thank you.
.
- Prev by Date: RE: 255 Character Limit for Linked Excel data
- Next by Date: Re: Use Paramater Input with an Table Import MACRO?
- Previous by thread: RE: 255 Character Limit for Linked Excel data
- Index(es):
Relevant Pages
|
