Re: New Server Cannot 'See Out'

It sounds like port 1433 is blocked at the firewall. The firewall is between
Server1 and Location2, nothing is going through the firewall.

You need to open a port (the default is 1433) in the firewall to allow 2-way
tcp traffic, and then set a firewall rule that restricts traffic to just the
IP addresses of Server1 and Server2.

And if you want a bit more obscurity, you could even use a different port.

--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."



"Michael" <itsjustme@xxxxxxxxxxxxx> wrote in message
news:OK6RHwkoGHA.516@xxxxxxxxxxxxxxxxxxxxxxx
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: sbs 2008 - no Internet access possible to 2nd server
    ... If you are a big enough business to use SBS then that means you have outgrown the "home office" of the SOHO acronym and, as such, should be treating your network with just as much security as you would a cash register with money in it. ... Almost all business class gateways can be configured as in a 'bridge' mode which means the firewall will handle all of the IP-level traffic, and almost all business-class firewalls can handle multiple IP's in a drop-in NAT configuration. ... Router forwards Internet traffic to server1. ...
    (microsoft.public.windows.server.sbs)
  • Ports to open in the firewall?
    ... It is a DC with multiple users setup on it. ... We would like for users on server1 to be able to do is login to WSS and use their account info from their local domain which lives on server1. ... Right now it works cause we do not have any ports closed between the DMZ and Lan sides of the firewall. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: New Server Cannot See Out
    ... Remember, we have numerous developer systems sitting behind the same firewall, each has SQL 2005 developer version installed, and they have perfect communication through the firewall with Server1. ... You need to open a port in the firewall to allow 2-way tcp traffic, and then set a firewall rule that restricts traffic to just the IP addresses of Server1 and Server2. ...
    (microsoft.public.sqlserver.connect)
  • Re: New Server Cannot See Out
    ... You may want to check if client machine in location 1 can access server1 ... configure a static port on server and open it via firewall. ... TCP Ports Needed for Communication to SQL Server Through a Firewall ... You may want to ping from server2 to server1, ...
    (microsoft.public.sqlserver.connect)
  • Re: SPN creation
    ... webserver named server1. ... accounts. ... He wants to run the test website on port ... these websites also connect to sql backend ...
    (microsoft.public.windows.server.active_directory)