🚀 go-pugleaf

Ok, I tried what was suggested, I opened up ODBC and went into the system
DSN, configured my SQL, changed from named pipes to the IP address and
tested, the same error comes up.

Does the difference in SP level matter?


"Dan Guzman" <DGuzman@nospamplease-earthlink.net> wrote in message
news:jN0V4.2917$S31.46716@newsread2.prod.itd.earthlink.net...
> If you want to connect via IP address instead of server name, you need to
> run the client network utility to change the default protocol to TCP/IP.
> Named pipes is the default which won't allow you to connect directly to an
> IP address.
>
> Hope this helps.
>
> Silverbrain <silverbrain@nospam.hotmail.com> wrote in message
> news:39246a38$0$26042@news.execpc.com...
> > Here is the synopsis of the network.
> >
> > WinNT 4.0 Server SP5; SQL 7.0 SP1; IP 128.10.10.2 (Domain A)
> >
> > Win2K Server; SQL 7.0 SP2; IP 128.15.15.15 (Domain B)
> >   OLAP is not installed on this machine.
> >
> > Both go to a Cisco router. Both have a trust relationship between them.
> > With the router in place, both Servers can
> > A) Ping
> > B) Telnet
> > C) HTTP
> > D) FTP
> > E) Browse and attatch to shared resources.
> >
> > So we know the router is doing it's job.  Now what I  did is on SQL,
> checked
> > that all services are started on both Servers.  I do the register SQL
> > server.  No wizard, i put the IP address in the server column.  I use
SQKL
> > Server auth, with the login name sa and no password.  I click OK, and an
> > error comes back at me....
> >
> > SQL Server registration failed because of the connection failure
displayed
> > below. Do you wish to Register anyway?
> > Client unable to establish connection
> > ConnectionOpen (CreateFile())
> >
> > Also, there is a third box, WinNT 4.0 SP 4 SQL 7 SP1, on the 128.10.10.x
> ip
> > scheme, but in another domain.  The first box was able to register this
> box
> > just fine.
> >
> >
> >
> >
> > What am i not doing here, and what can i try?  Thanks in advance, Jason
> >
> >
>
>