Can't connect from Server A to B but B to A

I have two machines with SQL2000 on both machines.
Machine A is a member of the domain, Machine B is in a workgroup with
the same name as the domain.
Using Enterprise manager I can connect from Machine B and manage the
SQL server on machine A.
When trying to connect from Machine A to manage SQL server on Machine
B I get an error 'SQL Server does not exist or access denied'.
I have double checked username/password several times.
Client Network Utility are set to TCP/IP and Named Pipes on both
machines.
Ping works fines. I can also access shared folders from A to B and
vice versa.
What else could be the problem?
Can you connect via SQL Login.
If you're connecting via Windows Login, be sure the account has the same
name and password on both side. Also, check to see if BUILTIN\<account> is
allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
online and give it access.
-oj
"Tosch" <tosch_nospam@.swissonline.ch> wrote in message
news:9hbl51pm68gln1gmqp2ckpk5h1d7a5q7r4@.4ax.com...
>I have two machines with SQL2000 on both machines.
> Machine A is a member of the domain, Machine B is in a workgroup with
> the same name as the domain.
> Using Enterprise manager I can connect from Machine B and manage the
> SQL server on machine A.
> When trying to connect from Machine A to manage SQL server on Machine
> B I get an error 'SQL Server does not exist or access denied'.
> I have double checked username/password several times.
> Client Network Utility are set to TCP/IP and Named Pipes on both
> machines.
> Ping works fines. I can also access shared folders from A to B and
> vice versa.
> What else could be the problem?
>
|||I have tried connecting with SQL Login, no luck. I even tried sa and I
could not connect.
On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
wrote:

>Can you connect via SQL Login.
>If you're connecting via Windows Login, be sure the account has the same
>name and password on both side. Also, check to see if BUILTIN\<account> is
>allowed access on serverB. If not, take a look at 'sp_grantlogin' in book
>online and give it access.
|||Hi
What happens if you try to do a telnet to server B using the port specified
in server B's TCP/IP Clinet configuration? By doing this, you can determine
if server B listen's properly on the correct port.
Regards
Steen
Tosch wrote:[vbcol=seagreen]
> I have tried connecting with SQL Login, no luck. I even tried sa and I
> could not connect.
>
> On Mon, 11 Apr 2005 13:54:05 -0700, "oj" <nospam_ojngo@.home.com>
> wrote: