Problem Registering Existing Server

I am trying to reregister an existing server that we've been able to
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
BobHi Bob
"Bob Bartel" wrote:
> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can't
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we had
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the client
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
>> I am trying to reregister an existing server that we've been able to
>> register previously.
>> I can successfully register it inside the network, i.e., from another
>> workstation on the network, but when I try to register via a gateway,
>> i.e.,
>> over the internet I can't. I can ping the server, and the router has
>> port
>> forwarding setup correctly (port 1433), I've turned off the firewall,
>> and
>> nothing else has changed that I am aware of, but it just won't respond.
>> I
>> am confident that the SA password is correct.
>> I'm stumped. I have remote users who need to access this server, but
>> can't
>> get in.
>> Can anyone give me any suggestions. I've tried everything I can imagine.
>> The one change on this system is that we had to reinstall the Server, and
>> we've installed CA Antivirus. But I've uninstalled the CA firewall
>> software, and turned off the Windows Firewall (just to get this up...we
>> had
>> it running before with SQL traffic allowed).
>> Any Ideas are welcome!!
>> Bob
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John|||Hi
"Bob Bartel" wrote:
> As I mentioned, I have already had this working before. And only shut down
> my firewall for this test. I agree a VPN is a good choice and I'll probably
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 1433
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
>> As I mentioned, I have already had this working before. And only shut
>> down
>> my firewall for this test. I agree a VPN is a good choice and I'll
>> probably
>> turn it on, but...
>> But the real problem is that even with the router correctly forwarding
>> 1433
>> and the firewall configured to allow the traffic, I can't register the
>> server remotely.
>> The only thing I can think of that may be effecting it is that I had to
>> reinstall the server. Can anyone think of anything that would keep
>> remote
>> users from registering with a new install? Is there some setting on the
>> server that I neglected to turn back on?
>> Bob
>>
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John|||Hi Bob
"Bob Bartel" wrote:
> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosing
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John