New Server Cannot 'See Out'

Hi All,

Not sure where to put this post, hope this is the right place. Relatively new to SQL, not sure what info you need, so here we go: We have a Windows 2000 Server running SQL 2000 ("Server1) in location 1. This server is outside of the firewall.

We have a network setup in location 2 where we are doing development and also have a server in that location (everything at location 2 is behind the same firewall). There is a new server in location 2 running Windows 2003 Server and SQL Server 2005.

The problem is that Server2 cannot see Server1, and Server1 cannot see Server2.

If, using Object Explorer, I click Connect > Database Engine, and put in the details for Server2, I get an error that the database does not reply.

Also, if trying to connect from Server2 to Server1 (registering a db), I get an access denied or does not exist error.

Any of the development machines at location 2 can see and connect to Server1, but Server2 cannot. Also, any of the Dev machines can see and connect to Server2 as well, but Server1 cannot.

1433 is not blocked in the firewall of location2, since all Dev machines can access SQL on Server1.

I'm really at a loss, and any ideas would be most helpful.

Thanks,

Michael
.

Relevant Pages

  • Re: transaction log shipping wizard uses wrong computer name?
    ... I'm still hoping someone can point me to a solution here...It looks like the "jobserver" name is an alias to the machine name that SQL Agent is running on...I presume that the SQL agent picked this up when I first installed SQL2005 on the server before it was joined to the domain. ... I'm configuring log shipping on server1 and backingup/restoring to server2. ...
    (microsoft.public.sqlserver.tools)
  • Security Question - Totally Stumped
    ... SERVER2 has joined to the SBS domain (verified by looking at the AD on ... When I log into SERVER2 using the Admin credentials of the domain ... To add to this SERVER2 also has SQL 2005 with Reporting Services. ...
    (microsoft.public.windows.server.sbs)
  • Re: Security Question - Totally Stumped
    ... SERVER2 has joined to the SBS domain (verified by looking at the AD on ... When I log into SERVER2 using the Admin credentials of the domain ... To add to this SERVER2 also has SQL 2005 with Reporting Services. ...
    (microsoft.public.windows.server.sbs)
  • Error 18456, State 28000
    ... Running SQL Server 2000... ... On server2, i have the exact same group set up... ... users in this group doesn't get recognized by my new sql installation. ... get the error above (SQL Error 18456, ...
    (microsoft.public.sqlserver.security)
  • transaction log shipping wizard uses wrong computer name?
    ... I'm trying to configure transaction log shipping using SMS on sql 2005. ... Both servers are 2008 DCs in a domain, with SQL and SQL Agent running under a domain account. ... I'm configuring log shipping on server1 and backingup/restoring to server2. ...
    (microsoft.public.sqlserver.tools)