Connect to MSDE Instance via Internet.

I am trying to connect to a MSDE instance across the internet.
I installed it at my house and can connect from work no problem.
Installed it at a customers and I can not connect to it.
I can access their Linksys router and have the correct ports forwarded (I
tried setting the DMZ on, it made no difference) 1434 UPD and 3605 TCP
(although I have them set to BOTH at this time)
Netstat -an shows that both 3605 and 1434 are listening.
TELNET 72.XXX.XXX.50 3605
(I also tried TELNET 72.XXX.XXX.50\InstanceName 3605) didn't know if I
needed the instance name.
Does nothing. But if I telnet my computer at home it clears the screen like
it should.
I have turned off their windows firewall and disabled their McAfee firewall
but no change.
I also open port 79 (we do some communication before we open SQL Server) and
it communicates fine. So I think I have the router set up OK.
Does anyone have any ideas?
Thanks in advance,
Rob
PS. It was installed as follows:
setup SAPWD=XXXX DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=RRRob,
Always difficult ones.
I found that TCP and UDP 1433-1434 open on both inbound and outbound solved
my problems. Also, I had problems if there were 2 NICS involved. Always
configure connections for the lowest IP in the range.
The other issues I've had with MSDE was that MSDE did not enable the TCp/IP
protocol by default. Use Enterprise manager, r-click the server, properties,
network config and check that tcp/ip and named pipes are enabled protocols.
Jamie.
"Rob" wrote:

> I am trying to connect to a MSDE instance across the internet.
> I installed it at my house and can connect from work no problem.
> Installed it at a customers and I can not connect to it.
> I can access their Linksys router and have the correct ports forwarded (I
> tried setting the DMZ on, it made no difference) 1434 UPD and 3605 TCP
> (although I have them set to BOTH at this time)
> Netstat -an shows that both 3605 and 1434 are listening.
> TELNET 72.XXX.XXX.50 3605
> (I also tried TELNET 72.XXX.XXX.50\InstanceName 3605) didn't know if I
> needed the instance name.
> Does nothing. But if I telnet my computer at home it clears the screen li
ke
> it should.
> I have turned off their windows firewall and disabled their McAfee firewal
l
> but no change.
> I also open port 79 (we do some communication before we open SQL Server) a
nd
> it communicates fine. So I think I have the router set up OK.
> Does anyone have any ideas?
> Thanks in advance,
> Rob
> PS. It was installed as follows:
> setup SAPWD=XXXX DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL INSTANCENAME=R
R
>
>

Connect through NAT router

I need to connect to SQL Server 2000 across the Internet. SQL Server is
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill Todd
Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com
|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh

Connect through NAT router

I need to connect to SQL Server 2000 across the Internet. SQL Server is
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill Todd
Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com
|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh

Connect through NAT router

I need to connect to SQL Server 2000 across the Internet. SQL Server is
behind a NAT router. What port(s) do I need to forward to be able to
connect with Enterprise Manager and ADO?
Bill ToddBill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server
> is behind a NAT router. What port(s) do I need to forward to be able
> to connect with Enterprise Manager and ADO?
Try forwarding 1033.
David Gugick
Imceda Software
www.imceda.com|||Bill Todd wrote:
> I need to connect to SQL Server 2000 across the Internet. SQL Server is
> behind a NAT router. What port(s) do I need to forward to be able to
> connect with Enterprise Manager and ADO?
>
I've personally found 1433 to be the port that's needed. This is,
however, configurable from within Enterprise Manager.
Right-click on your server, select the "General" tab, click on "Network
Configuration", and select TCP/IP from among the named protocols on the
right. Click "Properties" and this should tell you what port SQL Server
is using.
Josh

Connect across Internet through NAT router

I am attempting to use Enterprise Manager to connect to SS 2000 across the
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill ToddI found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd

Connect across Internet through NAT router

I am attempting to use Enterprise Manager to connect to SS 2000 across the
Internet. The machine running SQL Server is behind a NAT router.
Enterprise manager shows that the TCP/IP port that SQL Server is using is
1061. I have forwared port 1061 on the router to the machine running SQL
Server. When I attempt to register the server in Enterprise Manager I use
the WAN IP address of the router as the server name. However, registration
fails with the message "SQL Server does not exist or access denied."
What am I doing wrong?
Bill Todd
I found an article in BOL saying that UDP port 1434 must also be
forwarded, however, doing so did not help.
Bill Todd

Confusion about dialog security steps.

Hi There

I have done the following.

2 Servers across the net work Server A and Server B.

I have created private keys at each and copied to public keys across.

I create an endpoint at each with validation by the certificates. I then create appropriate users and logins at each and import the public certificates with authorization to the users who have send permission on the endpoints.

That is transport security sorted and it works.

Now from what i have learnt from examples, to setup dialog security i do the following.

create a private key in each DB :

create certificate Store001DialogPri

with subject = 'Store001DialogPri',

start_date = '07/20/2006'

active for begin_dialog = on;

go

I then copy the public key to each server, create a user only in each DB and import the public keys with authorization on the user. And grant send to the appropriate servcies to the user.

I then create appropriate remote service bindings with this user.

Now this works for me. Everythign seems A OK.

However i am going thorugh the Service Broker "bible", and there are a ton of steps i am not doing but my setup works ?

Steps i am not doing for example is when i create the private keys in the DB i should authorize them to a user i create who is then gratnted CONTROL permission on the SERVICES.

Now i do not do this but everything seems to be working. I thought i finally understood dialogs security but now i am totally confused ?

Is what i am doing correct ? If so why are these all these additinal steps mentioned ? WHat am i missing ?

Thanx

The AUTHORIZATION and CONTROL steps in the samples are needed if you are performing these steps for somebody else. You test probably ended up with all the services being owned by [dbo], (you are sysadmin on the test machine, aren't you?), and the certificates with private keys also being owned by [dbo], so it just worked. But in real life, you might have to do this setup steps for a service owned by a different database user, so in that case is important to associate the private key with the service owner.

HTH,
~ Remus

|||

Hi Remus

Yes everything should be owned by dbo, however i do not see any otehr users coming into the SB application, so therefore i shouldnot have to do these steps?

Thanx for the feedback

Confusing CONTAINS behavior

I'm experimenting with the CONTAINS operation and I've come across some
confusing or inconsistent results. The following results are exactly the
same if the search terms are enclosed in double quotes so that they are
treated as a phrase.
I'm searching a Books table for books whose Author column contains "cs".
The following CONTAINS statements in the WHERE clause result in books by
"Lewis, C.S." being returned:
CONTAINS( Author, 'cs' )
CONTAINS( Author, 'CS' )
CONTAINS( Author, 'C.S.' )
The fact that "cs" matches an author containing "C.S." indicates that both
case and punctuation are ignored. However, the following CONTAINS statement
does not return any results for "Lewis, C.S.":
CONTAINS( Author, 'c.s.' )
This puzzles me. It seems as though either punctuation is ignored or case
is ignored, but not both. What kind of behavior is that? Is this by design
?Greg Smalter wrote:
> I'm experimenting with the CONTAINS operation and I've come across
> some confusing or inconsistent results. The following results are
> exactly the same if the search terms are enclosed in double quotes so
> that they are treated as a phrase.
> I'm searching a Books table for books whose Author column contains
> "cs".
> The following CONTAINS statements in the WHERE clause result in books
> by "Lewis, C.S." being returned:
> CONTAINS( Author, 'cs' )
> CONTAINS( Author, 'CS' )
> CONTAINS( Author, 'C.S.' )
> The fact that "cs" matches an author containing "C.S." indicates that
> both case and punctuation are ignored. However, the following
> CONTAINS statement does not return any results for "Lewis, C.S.":
> CONTAINS( Author, 'c.s.' )
> This puzzles me. It seems as though either punctuation is ignored or
> case is ignored, but not both. What kind of behavior is that? Is
> this by design?
According to BOL, a word is one or more characters without spaces or
punctuation. Punctuation marks such as the period, colon, semicolon,
comma, and hyphen are ignored during a search.
I do not believe the full-text engine is indexing the punctuation marks
which is why the second query fails.
David Gugick
Quest Software
www.quest.com|||I agree about the specification of the word and how it shouldn't contain
punctuation. That is why I also tested it with phrases surrounded by double
quotes, where the specification doesn't mention that puncutation is not
allowed.
I imagine you are right about the indexing, but that doesn't explain why
CONTAINS( Author, 'C.S.' ) works while CONTAINS( Author, 'c.s.' ) does not
work, because they both have the exact same punctuation. The only differenc
e
is case.
"David Gugick" wrote:

> Greg Smalter wrote:
> According to BOL, a word is one or more characters without spaces or
> punctuation. Punctuation marks such as the period, colon, semicolon,
> comma, and hyphen are ignored during a search.
> I do not believe the full-text engine is indexing the punctuation marks
> which is why the second query fails.
>
> --
> David Gugick
> Quest Software
> www.quest.com
>|||Greg Smalter wrote:
> I agree about the specification of the word and how it shouldn't
> contain punctuation. That is why I also tested it with phrases
> surrounded by double quotes, where the specification doesn't mention
> that puncutation is not allowed.
> I imagine you are right about the indexing, but that doesn't explain
> why CONTAINS( Author, 'C.S.' ) works while CONTAINS( Author, 'c.s.'
> ) does not work, because they both have the exact same punctuation.
> The only difference is case.
That part is confusing...
David Gugick
Quest Software
www.quest.com