Cannot seem to connect to named instance

We are trying to connect to a SQL Server across the WAN. We can manage to
ping the server and know that SQL Server is online on the other end as on
the own internal network, we can connect to it.. but across the WAN, we
cannot. We are thinking its a port issue that needs to be opened. So the
question is do I only need to open the port that named instance is listening
on or do I have to open up some other ports too. I believe for named
instances, there is something to do with UDP port too. Let me know if i have
to open up UDP port 1434 too to get this to work.> Let me know if i have to open up UDP port 1434 too to get this to work.
Yes, you'll need to open up UDP port 1434 for named instance port
enumeration as well as the named instance port TCP port. Alternatively, you
can create an alias for the named instance on the client machine and specify
the named instance port number. You won't need to open UDP 1434 in that
case.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> We are trying to connect to a SQL Server across the WAN. We can manage to
> ping the server and know that SQL Server is online on the other end as on
> the own internal network, we can connect to it.. but across the WAN, we
> cannot. We are thinking its a port issue that needs to be opened. So the
> question is do I only need to open the port that named instance is
> listening on or do I have to open up some other ports too. I believe for
> named instances, there is something to do with UDP port too. Let me know
> if i have to open up UDP port 1434 too to get this to work.
>
>|||On the below thread and similar issue, how can I hard code SQL Instance to
use the same port number?
Any suggestions?
"Dan Guzman" wrote:
> > Let me know if i have to open up UDP port 1434 too to get this to work.
> Yes, you'll need to open up UDP port 1434 for named instance port
> enumeration as well as the named instance port TCP port. Alternatively, you
> can create an alias for the named instance on the client machine and specify
> the named instance port number. You won't need to open UDP 1434 in that
> case.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> > We are trying to connect to a SQL Server across the WAN. We can manage to
> > ping the server and know that SQL Server is online on the other end as on
> > the own internal network, we can connect to it.. but across the WAN, we
> > cannot. We are thinking its a port issue that needs to be opened. So the
> > question is do I only need to open the port that named instance is
> > listening on or do I have to open up some other ports too. I believe for
> > named instances, there is something to do with UDP port too. Let me know
> > if i have to open up UDP port 1434 too to get this to work.
> >
> >
> >
>|||> On the below thread and similar issue, how can I hard code SQL Instance to
> use the same port number?
You can specify the server port number using the SQL Server Network Utility
(SQL 2000) or the SQL Server Configuration Manager (SQL 2005). See
http://support.microsoft.com/kb/823938.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:A80C2723-4EB2-4BD0-92D1-619DF2FCF527@.microsoft.com...
> On the below thread and similar issue, how can I hard code SQL Instance to
> use the same port number?
> Any suggestions?
> "Dan Guzman" wrote:
>> > Let me know if i have to open up UDP port 1434 too to get this to work.
>> Yes, you'll need to open up UDP port 1434 for named instance port
>> enumeration as well as the named instance port TCP port. Alternatively,
>> you
>> can create an alias for the named instance on the client machine and
>> specify
>> the named instance port number. You won't need to open UDP 1434 in that
>> case.
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Hassan" <hassan@.hotmail.com> wrote in message
>> news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
>> > We are trying to connect to a SQL Server across the WAN. We can manage
>> > to
>> > ping the server and know that SQL Server is online on the other end as
>> > on
>> > the own internal network, we can connect to it.. but across the WAN, we
>> > cannot. We are thinking its a port issue that needs to be opened. So
>> > the
>> > question is do I only need to open the port that named instance is
>> > listening on or do I have to open up some other ports too. I believe
>> > for
>> > named instances, there is something to do with UDP port too. Let me
>> > know
>> > if i have to open up UDP port 1434 too to get this to work.
>> >
>> >
>> >
>>