Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error connecting to SQL Server

2 views
Skip to first unread message

Taylor Huckstep

unread,
Nov 7, 2002, 6:56:57 PM11/7/02
to
Can somebody please help me here? I have MS Project
Server installed and SQL Server Installed, on the same
machine, as it happens I have only one Server available.
And I can connect successfully to the MS Project Server
and open our project LOCALLY. Only from within our
network does it work. Attempting to connect from
outside, through the internet, I get the following error
after entering authentication information:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.

Here's a bit more information that might help in solving
this. I am trying to connect by entering the IP address
of the server, so no DNS problems should be occuring.
From within our Network we connect with
http://office/ProjectServer, but outside we're attempting
to connect with http://xxx.xxx.31.83/ProjectServer.

I am desperate for some help here, my searches on the web
have so far failed. Thanks very very much for any help
or suggestions.

--Taylor Huckstep

Gary Chefetz [MVP]

unread,
Nov 8, 2002, 1:00:04 PM11/8/02
to
Taylor:

Project Professional and Project Server weren't designed for this type of
connectivity. Using Terminal Services or a VPN solution are better options.

--
Gary Chefetz [MVP]

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.


"Taylor Huckstep" <tay...@sisna.com> wrote in message
news:a35401c286b9$5b444df0$2ae2...@phx.gbl...

Taylor Huckstep

unread,
Nov 11, 2002, 9:32:41 PM11/11/02
to
If it's not designed to allow collaboration with a
client/server environment through the internet, then what
was server designed to for? And what is Microsoft
Project Web Access for? Are you saying that it's not
designed to go through a firewall, but to be used
internally only? And you're suggesting a VPN solution so
they come on board virtually? Just trying to clarify
what you mean by it's not designed to do what I'm trying
to do. Thank you.

--Taylor

>-----Original Message-----
>Message unavailable

Gary Chefetz [MVP]

unread,
Nov 19, 2002, 8:08:32 AM11/19/02
to
Taylor:

The Project Professional client needs domain credentials to talk to Project
Server across the Internet to Project Web Access. You get these by providing
VPN. On a single-box installation this can be accomplished by using FQDNs
for your installation and local machine accounts but performance may not be
what you want it to be. Terminal Services is THE answer.

--
Gary Chefetz [MVP]

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.


"Taylor Huckstep" <tay...@sisna.com> wrote in message

news:4a6501c289f3$c666cf80$3aef2ecf@TKMSFTNGXA09...

0 new messages