Cant add ASPNET login to SQL Server

Here's the situation:

SQL Server is on one machine.
ASP.net is running on a different machine named THALES, which has the ASPNET account on it.
Both machines are on the same domain.

I am trying to add the THALES\ASPNET as a SQL Server login so that I can connect using Windows Authentication. When I try to add THALES\ASPNET, I get this message:
Error 15401: Windows NT user or group 'THALES\ASPNET' not found. Check the name again.

Any suggestions?You need to create an ASPNET user on the SQL Server machine, and give it the same password as the ASPNET user on the Web Server. By default, the password for the ASPNET user is autogenerated. You will need to change this in the Machin.Config so that it is a known password that you can then use for the ASPNET user on the SQL Server machine.|||Thank you, Douglas, that helped.

Cant access Northwind database

I'm using XP Pro and I have the Developer's version of SQL Server installed. I downloaded SQLXML 3.0 and created a virtual directory named nwind.

I then entered the following on my IE browser:

http://<IIServer>/nwind?sql=SELECT FirstName, LastName FROM Employees FOR XML AUTO&root=root

the result is:
"The page cannot be displayed..."

I'd appreciate any help.

Thanks,
Pathttp://<IIServer>/nwind?sql=SELECT FirstName, LastName FROM Employees FOR XML AUTO&root=root

Is that a typo, or are you trying to pass a variable to a directory? when you say /nwind?sql='foo' then you should get page cannot be displayed, right? Don't you have to say /nwind/default.asp?sql='foo' ??

or will the virtual directory/IIS understand what you mean?sql

Can't Access Named Instanced With Network Protocol Disabled

Hi there,
I have a little question here.
I've installed a named instance of MSDE SP4 called mydb, with network
protocols disabled.
Then I noticed that I can't connect to it using OSQL
I tried
'osl -S (local)\mydb -E'
'osl -S localhost\mydb -E'
and both of them can't connect to the database, however.
'osql -S mypcname\mydb -E'
works perfectly... I don't want to manually fill in the machine name for
each connection string can someone tell me why (local) doesn't seem to
connect to the local machine? Does it have anything to do with network
protocols disabled?
Thanks.
Hi
(local) and localhost rely on the network stack to resolve. If you network
is disabled, there is nothing there to resolve the name. localhost resolves
to 127.0.0.1 by TCP/IP.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Marauderz" <marauderz@.nospam.com> wrote in message
news:u1dlfrAqFHA.3720@.TK2MSFTNGP14.phx.gbl...
> Hi there,
> I have a little question here.
> I've installed a named instance of MSDE SP4 called mydb, with network
> protocols disabled.
> Then I noticed that I can't connect to it using OSQL
> I tried
> 'osl -S (local)\mydb -E'
> 'osl -S localhost\mydb -E'
> and both of them can't connect to the database, however.
> 'osql -S mypcname\mydb -E'
> works perfectly... I don't want to manually fill in the machine name for
> each connection string can someone tell me why (local) doesn't seem to
> connect to the local machine? Does it have anything to do with network
> protocols disabled?
> Thanks.
>

can't access named instance by it's name

Hi,

I have sql2005 sp1 active-active installation.

I've fixed the named instance port.

I can't reach it from clients with i'ts name (servername\instancename) .

I manage to rech it only by using servername, ip-port.

The sql browser has the following error:

"The configuration of the AdminConnection\TCP protocol in the SQL instance GILBOACL is not valid."

your help is appreciated!

Shahar

1. Is UPD port 1434 open?
2. Does the browser service account have access to the registry key? See the following article for more info.
http://support.microsoft.com/kb/905618

Cannot view reports but able to see ReportManager from different

My RS was installed on server which is accessed from 2 domains (lets
named Domain1 and Domain2).
Server belongs to Domain1 and RS service has admin privileges on
Domain1 as well. Viewing reports on Domain1 cause no problem. But I
have users in Domain2. They have got RUSER server role to access to RS
with Windows Auth.
When I open reports on Domain2 I could see Report Manager home page,
but when I click report I get "Internet Explorer cannot display the
webpage".
Is it possible to have access from 2 different domains to RS?
Any help appreciate.
Regards,
BartekAre the domains trusted? Does Domain1 trust Domain2?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bartolo" <andrew.osa@.gmail.com> wrote in message
news:44bafaf7-1f58-4387-9014-2bec3a3caaa5@.8g2000hsu.googlegroups.com...
> My RS was installed on server which is accessed from 2 domains (lets
> named Domain1 and Domain2).
> Server belongs to Domain1 and RS service has admin privileges on
> Domain1 as well. Viewing reports on Domain1 cause no problem. But I
> have users in Domain2. They have got RUSER server role to access to RS
> with Windows Auth.
> When I open reports on Domain2 I could see Report Manager home page,
> but when I click report I get "Internet Explorer cannot display the
> webpage".
> Is it possible to have access from 2 different domains to RS?
> Any help appreciate.
> Regards,
> Bartek|||Yes, both domains are trusted.
Bartek
On 4 Kwi, 17:50, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> Are the domains trusted? Does Domain1 trust Domain2?
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Bartolo" <andrew...@.gmail.com> wrote in message
> news:44bafaf7-1f58-4387-9014-2bec3a3caaa5@.8g2000hsu.googlegroups.com...
> > My RS was installed on server which is accessed from 2 domains (lets
> > named Domain1 and Domain2).
> > Server belongs to Domain1 and RS service has admin privileges on
> > Domain1 as well. Viewing reports on Domain1 cause no problem. But I
> > have users in Domain2. They have got RUSER server role to access to RS
> > with Windows Auth.
> > When I open reports on Domain2 I could see Report Manager home page,
> > but when I click report I get "Internet Explorer cannot display the
> > webpage".
> > Is it possible to have access from 2 different domains to RS?
> > Any help appreciate.
> > Regards,
> > Bartek

Cannot start SQL Server Browser

Hello,

I use SQL Server 2005 for multi-user access. In the Surface Area Configuration, I changed the protocol from TCP/IP to Named Pipes and restarted the service. Then I went to SQL Server Browser, stopped it and clicked on Start to restart. I am getting a message "An error occurred while performing this operation". I am not able to get the Browser started.

Any help would be greatly appreciated.

Check the Windows event log and report back with the errors listed by SQL Browser service this will help with diagnosis.|||

I checked the error log and found a few messages for SQL Browser. Here they are:

1. SQL Browser Service was unable to establish SQL instance and connectivity discovery
2. The SQL Browser service port was unavailable for listening, invalid
3. The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.
4. The SQL Browser is enabling SQL instance and connectivity discovery support
5. The SQL Browser service has started
6. The SQL Browser service has shut down

|||

The key one is "The SQLBrowser service port is unavailable for listening, or invalid.".

So what happens is SQL Browser starts up and enumerates all network interfaces and attempts to bind to UDP port 1434 on each one found. If it cannot bind to any of the network interfaces, you will get the above error.

So run this from a command prompt first to locate the process id bound to UDP 1434 ->

netstat -aon -p UDP

Look for things bound to 1434, like for example PID 4736 below:

Proto Local Address Foreign Address State PID
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 1156
UDP 0.0.0.0:1025 *:* 1792
UDP 0.0.0.0:1026 *:* 1792
UDP 0.0.0.0:1027 *:* 1792
UDP 0.0.0.0:1434 *:* 4736
...

Next look up the PID in Task Manager to see what process this is. If it's a SQL Server process try shutting down all SQL Server instances and then restart SQL Browser. If it is some other process let me know what it is.

It is also possible that SQLBrowser did not find any network interfaces to bind to, for example if the computer has no NICs. Let me know if this is a NIC-less PC.

|||

check whether firewall is enabled on this machine.. check UDP port 1434 is excempted.... Refer http://msdn2.microsoft.com/en-us/library/ms165724.aspx

Madhu

|||Thank you Matt for your help. I tried the "netstat -aon -p UDP" command. The Windows 2000 Server does not seem to support the -o switch which shows the Process ID. I could only do "netstat -an -p UDP", without the "o". I can see that 1434 was listed, but do not know the process ID. How may I proceed?|||

Most likely it is another SQL Server service, do you see sqlservr.exe in the Task Manager? So go to control panel Services and stop all SQL Server services you see, then start SQL Browser. Once SQL Browser loads up it will automatically disable the other SQL Server services from binding to UDP 1434. Then you can restart the other SQL Server services. Look in Services for things like MSSQL$<Something> these are SQL Server instances.

Try running this from command prompt to find the running SQL Services (I think it might work on Windows 2000):

sc query | findstr /I "MSSQL"

Look for things like:

SERVICE_NAME: MSSQLSERVER

or

SERVICE_NAME: MSSQL$INSTANCE1

Then stop these services, start SQL Browser, then restart the SQL Services.

|||

I followed your suggestion and stopped the SQL Server services (MS SQL Server and SQL Server (SQLExpress). Then I was able to start the SQL Server Browser. Then I restarted the Database Engine Service from Surface Area Configuration. It is working fine and the client can connect.

Thank you very much. It was a great help.

|||Thank you Madhu for the information. Though it did not solve my problem, I find the information helpful.|||

Hi,

I am having a problem with starting the browser, I have checked the UDP port and it is certainly available.

I get this error repeated every 1 minute in the event log "The SQLBrowser is enabling SQL instance and connectivity discovery support." with a "SQLDmpr###.mdmp" dumped to C:\Program Files (x86)\Microsoft SQL Server\90\Shared\ErrorDumps in a beautiful harmony with the events.

Does anyone have a clue as to what is happening here, this is the only server I have this problem with (SQL server 64bit Enterprise edition)

Many thanks

Mike

|||

Does not sound good. I'll check Watson to see if your dumps are showing up.

Check the event log to and post back with the messages from SQLBrowser service.

|||

Hey Matt, thanks for the response,

The browser service keeps repeating this error:

The SQLBrowser is enabling SQL instance and connectivity discovery support.

and this error

The SQL Server Browser service terminated unexpectedly. It has done this 45 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

If I run "sqlbrowser.exe -c" then I end up with an output like this:

C:\Program Files (x86)\Microsoft SQL Server\90\Shared>sqlbrowser -c
SQLBrowser: starting up in console mode
SQLBrowser: starting up SSRP redirection service
SQLBrowser is successfully listening on 0.0.0.0[1434]
[3608]: Waiting for next request...
[3600]: Waiting for next request...
[3616]: Waiting for next request...
[3612]: Waiting for next request...
[3608]: Received request...
[3600]: Received request...
[3608]: Waiting for next request...
SQLBrowser: starting up OLAP redirection service
[3600]: Waiting for next request...

then it crashes and leaves the dmp file.

Getting hard to see this one... there not that much that could get in the way right!? I have disabled windows firewall. Single instance is easily accessible. I had heard that KB910437 caused a conflict with the exe; have you heard of that before, so I tried removing that. no joy.

Cheers

Mike

|||

Looks like a problem with OLAP redirection dll. We host this in sqlbrowser. The dll is named msmdredir.dll and it's located in the C:\Program Files\Microsoft SQL Server\90\Shared folder. You could try as a temporary fix renaming this dll to msmdredir.dll_ but in general this looks like an invalid setup type issue.

|||

Matt,

That worked. I am amazed that it did... but it did.

How would an invalid setup have affected this? I have just run a fresh install and service packed to SP2, but this problem persisted.

I'm going to need that DLL though, this server is supposed to run analysis services and OLAP. Whatamigonnado?

Do you know what the setup validity error is?

Thanks for your help so far bud,

Great.

mike

|||

Most likely some runtime dependancy on the olap redirector dll did not get properly installed.

If you could send me one of these .mdmp files I can get this over to OLAP folks for diagnosis.

My email is mattn (at microsoft.com).

Cannot start SQL Server Browser

Hello,

I use SQL Server 2005 for multi-user access. In the Surface Area Configuration, I changed the protocol from TCP/IP to Named Pipes and restarted the service. Then I went to SQL Server Browser, stopped it and clicked on Start to restart. I am getting a message "An error occurred while performing this operation". I am not able to get the Browser started.

Any help would be greatly appreciated.

Check the Windows event log and report back with the errors listed by SQL Browser service this will help with diagnosis.|||

I checked the error log and found a few messages for SQL Browser. Here they are:

1. SQL Browser Service was unable to establish SQL instance and connectivity discovery
2. The SQL Browser service port was unavailable for listening, invalid
3. The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid.
4. The SQL Browser is enabling SQL instance and connectivity discovery support
5. The SQL Browser service has started
6. The SQL Browser service has shut down

|||

The key one is "The SQLBrowser service port is unavailable for listening, or invalid.".

So what happens is SQL Browser starts up and enumerates all network interfaces and attempts to bind to UDP port 1434 on each one found. If it cannot bind to any of the network interfaces, you will get the above error.

So run this from a command prompt first to locate the process id bound to UDP 1434 ->

netstat -aon -p UDP

Look for things bound to 1434, like for example PID 4736 below:

Proto Local Address Foreign Address State PID
UDP 0.0.0.0:445 *:* 4
UDP 0.0.0.0:500 *:* 1156
UDP 0.0.0.0:1025 *:* 1792
UDP 0.0.0.0:1026 *:* 1792
UDP 0.0.0.0:1027 *:* 1792
UDP 0.0.0.0:1434 *:* 4736
...

Next look up the PID in Task Manager to see what process this is. If it's a SQL Server process try shutting down all SQL Server instances and then restart SQL Browser. If it is some other process let me know what it is.

It is also possible that SQLBrowser did not find any network interfaces to bind to, for example if the computer has no NICs. Let me know if this is a NIC-less PC.

|||

check whether firewall is enabled on this machine.. check UDP port 1434 is excempted.... Refer http://msdn2.microsoft.com/en-us/library/ms165724.aspx

Madhu

|||Thank you Matt for your help. I tried the "netstat -aon -p UDP" command. The Windows 2000 Server does not seem to support the -o switch which shows the Process ID. I could only do "netstat -an -p UDP", without the "o". I can see that 1434 was listed, but do not know the process ID. How may I proceed?|||

Most likely it is another SQL Server service, do you see sqlservr.exe in the Task Manager? So go to control panel Services and stop all SQL Server services you see, then start SQL Browser. Once SQL Browser loads up it will automatically disable the other SQL Server services from binding to UDP 1434. Then you can restart the other SQL Server services. Look in Services for things like MSSQL$<Something> these are SQL Server instances.

Try running this from command prompt to find the running SQL Services (I think it might work on Windows 2000):

sc query | findstr /I "MSSQL"

Look for things like:

SERVICE_NAME: MSSQLSERVER

or

SERVICE_NAME: MSSQL$INSTANCE1

Then stop these services, start SQL Browser, then restart the SQL Services.

|||

I followed your suggestion and stopped the SQL Server services (MS SQL Server and SQL Server (SQLExpress). Then I was able to start the SQL Server Browser. Then I restarted the Database Engine Service from Surface Area Configuration. It is working fine and the client can connect.

Thank you very much. It was a great help.

|||Thank you Madhu for the information. Though it did not solve my problem, I find the information helpful.|||

Hi,

I am having a problem with starting the browser, I have checked the UDP port and it is certainly available.

I get this error repeated every 1 minute in the event log "The SQLBrowser is enabling SQL instance and connectivity discovery support." with a "SQLDmpr###.mdmp" dumped to C:\Program Files (x86)\Microsoft SQL Server\90\Shared\ErrorDumps in a beautiful harmony with the events.

Does anyone have a clue as to what is happening here, this is the only server I have this problem with (SQL server 64bit Enterprise edition)

Many thanks

Mike

|||

Does not sound good. I'll check Watson to see if your dumps are showing up.

Check the event log to and post back with the messages from SQLBrowser service.

|||

Hey Matt, thanks for the response,

The browser service keeps repeating this error:

The SQLBrowser is enabling SQL instance and connectivity discovery support.

and this error

The SQL Server Browser service terminated unexpectedly. It has done this 45 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

If I run "sqlbrowser.exe -c" then I end up with an output like this:

C:\Program Files (x86)\Microsoft SQL Server\90\Shared>sqlbrowser -c
SQLBrowser: starting up in console mode
SQLBrowser: starting up SSRP redirection service
SQLBrowser is successfully listening on 0.0.0.0[1434]
[3608]: Waiting for next request...
[3600]: Waiting for next request...
[3616]: Waiting for next request...
[3612]: Waiting for next request...
[3608]: Received request...
[3600]: Received request...
[3608]: Waiting for next request...
SQLBrowser: starting up OLAP redirection service
[3600]: Waiting for next request...

then it crashes and leaves the dmp file.

Getting hard to see this one... there not that much that could get in the way right!? I have disabled windows firewall. Single instance is easily accessible. I had heard that KB910437 caused a conflict with the exe; have you heard of that before, so I tried removing that. no joy.

Cheers

Mike

|||

Looks like a problem with OLAP redirection dll. We host this in sqlbrowser. The dll is named msmdredir.dll and it's located in the C:\Program Files\Microsoft SQL Server\90\Shared folder. You could try as a temporary fix renaming this dll to msmdredir.dll_ but in general this looks like an invalid setup type issue.

|||

Matt,

That worked. I am amazed that it did... but it did.

How would an invalid setup have affected this? I have just run a fresh install and service packed to SP2, but this problem persisted.

I'm going to need that DLL though, this server is supposed to run analysis services and OLAP. Whatamigonnado?

Do you know what the setup validity error is?

Thanks for your help so far bud,

Great.

mike

|||

Most likely some runtime dependancy on the olap redirector dll did not get properly installed.

If you could send me one of these .mdmp files I can get this over to OLAP folks for diagnosis.

My email is mattn (at microsoft.com).

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.
>
>

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.
>> >
>> >
>> >
>>

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.
>
>