remove double value

Hy
Never use/practice SQL a lot, (vb... more, have free msde 2000) .
2 questions
A)is it simple to write a T-SQL query for having 2) at result starting
from 1) .
B)how to test dynamically sql with parmaeter ( using vb ADO)

1) before query
columA columB
d e <-same
e d <-same
e e
e d <-same

2)after query
columA columB
d e or e d
e e> A)is it simple to write a T-SQL query for having 2) at result starting
> from 1) .

SELECT DISTINCT
COALESCE(S2.a,S1.a) AS a,
COALESCE(S2.b,S1.b) AS b
FROM Sometable AS S1
LEFT JOIN Sometable AS S2
ON S1.a = S2.b AND S1.b = S2.a AND S2.a < S2.b

> B)how to test dynamically sql with parmaeter ( using vb ADO)

This may help:
http://msdn.microsoft.com/library/e...oprg02_6df7.asp
See also:
http://www.sommarskog.se/dyn-search.html

--
David Portas
----
Please reply only to the newsgroup
--|||David Portas wrote:
>>A)is it simple to write a T-SQL query for having 2) at result starting
>>from 1) .
>
> SELECT DISTINCT
> COALESCE(S2.a,S1.a) AS a,
> COALESCE(S2.b,S1.b) AS b
> FROM Sometable AS S1
> LEFT JOIN Sometable AS S2
> ON S1.a = S2.b AND S1.b = S2.a AND S2.a < S2.b
>
>>B)how to test dynamically sql with parmaeter ( using vb ADO)
>
> This may help:
> http://msdn.microsoft.com/library/e...oprg02_6df7.asp
> See also:
> http://www.sommarskog.se/dyn-search.html

hy
thank a lot for sharing your knowledge.
perhaps it was easy for you buit very hard for me
thank's for your quicky response

Remote-server registration

Does MSDE support registering a (remote) sql-server.
I am trying to replicate between two computers on the Internet (both XP).
Is this a futile attempt ... must the publisher be a "full" instance of SQL
server?
check out this link:
http://support.microsoft.com/default...;en-us;Q324992
MSDE 2000 can act as both a Publisher or Distributor, and a Subscriber, and it can replicate between MSDE versions and regular versions of SQL Server. Additionally, you cannot use it for transactional publication, but you can use it as a Publisher of snap
shot replication, and merge replication, and as a Subscriber to all three types of publications.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" wrote:

> Does MSDE support registering a (remote) sql-server.
> I am trying to replicate between two computers on the Internet (both XP).
> Is this a futile attempt ... must the publisher be a "full" instance of SQL
> server?
>
>
sql

Remotely Connect to MSDE

Hi
I just installed MSDE over my Windows 2003 box and facing an small problem.
I installed it with SQL security mode and also set a password for user "sa".
Everything looks just fine using "osql" as it uses local address.
But I can't connect to my server from another computer using VS.NET Server Explorer.
It seems as MSDE is set to reject connections from outside by default.
My question is how to enable it so I can connect using my "sa" account.
Appreciate your help in advance.OK. are you trying to connect by IP address or server name? do you have a firewall installed?|||Since I am connecting from outside of the server, I am using IP address.
And also I don't have any firewall installed.|||at a guess I'd say you have only windows authentication enabled. not 100% sure how to change that in MSDE, but I'll scout around and see.

remote saleslogix user problem using msde

Hello, I am trying to setup a remote user in saleslogix. I can login to
the remote databse but i cant login to the local msde, I attached the
remote database successfully but i believe the password of the remote
database does not match. any ideas? should i regenerate the remote
database? can anyone tell me the steps, I dont see to many 6.1
saleslogix users anymore, where did everyone go?You might try this site: http://www.slxdeveloper.com/page.aspx
<jcharth@.hotmail.com> wrote in message
news:1110138810.089034.124370@.o13g2000cwo.googlegroups.com...
> Hello, I am trying to setup a remote user in saleslogix. I can login to
> the remote databse but i cant login to the local msde, I attached the
> remote database successfully but i believe the password of the remote
> database does not match. any ideas? should i regenerate the remote
> database? can anyone tell me the steps, I dont see to many 6.1
> saleslogix users anymore, where did everyone go?
>|||thanks Michael
I found this one too
http://www.saleslogixuser.com/Forum...aspx?ForumID=4
but no luck

Remote MSDE Connection string?

For a SQL Server 2000 connection string I usualy use the following format:

server=somewhere.com;uid=sa;password=sa;database=myDB

or:

server=66.33.11.123;uid=sa;password=sa;database=myDB

However, now I am dealing with a remote MSDE database. What is the format to connect to a remote MSDE database? Is it:

server=<IPADDRESS>\<INSTANCENAME>;uid=sa;password=sa;database=myDB

Where <IPADDRESS> is the Ip address of the remote machine and <INSTANCENAME> is the MSDE instance name. Is this correct? If not, what am I doing wrong?I've used the <MACHINENAME>\<INSTANCENAME> successfully before, but I'm not sure about the <IPADDRESS>\<INSTANCENAME> combo.|||I would only think that I can use the <MACHINENAME>\<INSTANCENAME> way if the machine was on my local area network. But the machine is not, it's on a remote network on the internet. So I couldn't use <MACHINENAME>\<INSTANCENAME> because how would it find that machine unless it had an IP address?|||you need the ip address, and have that msde server accessible through their firewall.|||So,... in other words,.. I was right,... the correct way to access it is:

server=<IPADDRESS>\<INSTANCENAME
correct?

Remote management of database

trying to connect to remote MSDE database to manage it
--msde instance with DISABLENETWORKPROTOCOLS=0 is installed and working.
--local connection works to confirm username and password
--firewall ports are configured correctly and listening
--remote telnet connection works to confirm ip and port #
--ASP page can connect and return results from query
but tcp/ip does not connect
any suggestions on how to fix/make a tcp/ip connection work ?TJS wrote:
> trying to connect to remote MSDE database to manage it
> --msde instance with DISABLENETWORKPROTOCOLS=0 is installed and working.
> --local connection works to confirm username and password
> --firewall ports are configured correctly and listening
> --remote telnet connection works to confirm ip and port #
> --ASP page can connect and return results from query
> but tcp/ip does not connect
> any suggestions on how to fix/make a tcp/ip connection work ?
>
Well, MSDE (which is a free desktop editiion) normally doesn't work for outs
ide connections(they
don't want you to use the free version as a real server :)),
but i remember that some time ago on a web site i've seen a trick to make it
work. Try googling.|||I searched for a solution before coming here.
"MuZZy" <leyandrew@.yahoo.com> wrote in message
news:A7adnSWJuc_pCKbfRVn-vg@.comcast.com...
> TJS wrote:
> Well, MSDE (which is a free desktop editiion) normally doesn't work for
> outside connections(they don't want you to use the free version as a real
> server :)),
> but i remember that some time ago on a web site i've seen a trick to make
> it work. Try googling.

Remote login to MSDE 2000 (Desktop)

My question is, is it possible to connect to an SQL database using the MSDE 2000 SP3a edition over the internet? And if so, how do I set it up? Thank you in advance.::My question is, is it possible to connect to an SQL database using the MSDE 2000 SP3a
::edition over the internet?

Yes.

::And if so, how do I set it up?

You mean after making sure you can connect to the server from the internet, having a firewall in place etc.?

Not at all. There is nothing left to configure after this.

EVERY MSDE installation automatically accepts connections from the network, and guess what - the internet is just a network.

Remote Desktop

I have msde 2000 installed by one of my applications and
every time i access my pc via Remote Desktop, the msde
initializes? When I'm at my pc locally, it is not an
issue.
What is Remote Desktop doing that is causing this
behaviour and how can i get it to stop?
thanks in advance
jo
Hi Joann,
If you have installed SP3 on MSDE, the network access is
disabled by default (libraries are disabled by default) Windows XP SP2
firewall also blocks any MSSQL services from listening on the network.
It is mentioned as DISABLENETWORKPROTOCOLS switch in the readme
file. You have to enable net libraries.
See these articles:
http://support.microsoft.com/default...b;en-us;841249
http://support.microsoft.com/default...b;en-us;814130
Magy
"Joann" wrote:

> I have msde 2000 installed by one of my applications and
> every time i access my pc via Remote Desktop, the msde
> initializes? When I'm at my pc locally, it is not an
> issue.
> What is Remote Desktop doing that is causing this
> behaviour and how can i get it to stop?
> thanks in advance
> jo
>
>

Remote connection to MSDE

I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
Any ideas?
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
|||Ok, here's what i've discovered:
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?
|||Did you restart after enabling TCP/IP? Is it a default
instance or a named instance? Can you connect locally when
on the machine with MSDE?
-Sue
On 25 Jan 2006 14:21:43 -0800, "laurin1" <laurin1@.osai.com>
wrote:

>I just did an netstat -an and I don't see the server listening on 1433.
>What am I not doing?
|||Yes. It's a named instance (SHAREPOINT). I can connect locally.
|||Make sure you aren't having firewall issues.
Can you ping the MSDE box from the other box?
Check the listening port for the MSDE instance - when you
start up MSDE, it logs what protocols, ports it is listening
on in the error log.
Try to telnet to the port it's listening on.
Verify the login being used.
And if those don't get you anywhere, you can find additional
troubleshooting steps in the following article:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On 26 Jan 2006 05:41:03 -0800, "laurin1" <laurin1@.osai.com>
wrote:

>Yes. It's a named instance (SHAREPOINT). I can connect locally.
|||I just found out that this is WMSDE, not MSDE, which can only be
connected to remotely. No matter what changes I make, the server will
not listen on 1433.
|||If it is indeed WMSDE, it only supports local connections so it will never
listen on a port. WMSDE is an OS component that can only be connected to by
selected Microsoft software running locally.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"laurin1" <laurin1@.osai.com> wrote in message
news:1138379664.059706.236830@.g14g2000cwa.googlegr oups.com...
>I just found out that this is WMSDE, not MSDE, which can only be
> connected to remotely. No matter what changes I make, the server will
> not listen on 1433.
>

Remote connection to MSDE

I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpe
n
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server do
es not
exist or access denied.
Any ideas?I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?|||Ok, here's what i've discovered:
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?|||Did you restart after enabling TCP/IP? Is it a default
instance or a named instance? Can you connect locally when
on the machine with MSDE?
-Sue
On 25 Jan 2006 14:21:43 -0800, "laurin1" <laurin1@.osai.com>
wrote:

>I just did an netstat -an and I don't see the server listening on 1433.
>What am I not doing?|||Yes. It's a named instance (SHAREPOINT). I can connect locally.|||Make sure you aren't having firewall issues.
Can you ping the MSDE box from the other box?
Check the listening port for the MSDE instance - when you
start up MSDE, it logs what protocols, ports it is listening
on in the error log.
Try to telnet to the port it's listening on.
Verify the login being used.
And if those don't get you anywhere, you can find additional
troubleshooting steps in the following article:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On 26 Jan 2006 05:41:03 -0800, "laurin1" <laurin1@.osai.com>
wrote:

>Yes. It's a named instance (SHAREPOINT). I can connect locally.|||I just found out that this is WMSDE, not MSDE, which can only be
connected to remotely. No matter what changes I make, the server will
not listen on 1433.|||If it is indeed WMSDE, it only supports local connections so it will never
listen on a port. WMSDE is an OS component that can only be connected to by
selected Microsoft software running locally.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"laurin1" <laurin1@.osai.com> wrote in message
news:1138379664.059706.236830@.g14g2000cwa.googlegroups.com...
>I just found out that this is WMSDE, not MSDE, which can only be
> connected to remotely. No matter what changes I make, the server will
> not listen on 1433.
>|||somebody on this forum "sameer" gave me a clue that
1433 is not listened on due to the "slammer" virus requiring SP1 for SQL
Server 2005...I am just begiing on this so what do I know
"Roger Wolter[MSFT]" wrote:

> If it is indeed WMSDE, it only supports local connections so it will never
> listen on a port. WMSDE is an OS component that can only be connected to
by
> selected Microsoft software running locally.
> --
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "laurin1" <laurin1@.osai.com> wrote in message
> news:1138379664.059706.236830@.g14g2000cwa.googlegroups.com...
>
>

remote connection problem

Hi all,
I'm trying to connect to a MSDE database on a remote system.
I have no problems connecting locally.
I have changed the security to mixed mode, and i have made a NAT entry
that forwards port 1433 to the internal server with the MSDE database
on it.
(just for the record, the server is running five different MSDE
instances)
I wanted to verify that the instance i need access to is at port 1433,
so i tried opening SVRNETCN.exe but it just gives me the following
error message "The specified module could not be found" (The title of
the alert window is "126")
So i went to the registration database trying to confirm it there -
however the only related key i could find was:
-------
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer \Client
\SuperSocketNetLib]
"ProtocolOrder"=hex(7):74,00,63,00,70,00,00,00,6e, 00,70,00,00,00,00,00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer \Client
\SuperSocketNetLib\LastConnect]
"winfinans.mondo.dk"="-134086648:tcp:winfinans.mondo.dk,1433"
"winfinans.pitweb.dk"="-150536184:tcp:winfinans.pitweb.dk,1433"
"MYSERVER\\SHAREPOINT"="-150536184:lpc:MYSERVER\\SHAREPOINT"
"MYSERVER\\PADMINISTRATOR"="-134086648:lpc:MYSERVER\\PADMINISTRATOR"
"MYSERVER\\SBSMONITORING"="-33423352:lpc:MYSERVER\\SBSMONITORING"
"MYSERVER\\WINFINANS"="-150536184:lpc:MYSERVER\\WINFINANS"
"MYSERVER\\INSIGTH"="-150536184:lpc:MYSERVER\\INSIGTH"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer \Client
\SuperSocketNetLib\Tcp]
"DefaultPort"=dword:00000599
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer \Client
\SuperSocketNetLib\VIA]
"RecognizedVendors"="Giganet,QLogic"
-------
It is the instance "winfinans" i need access to.
I tried searching the web for an alternative method to make sure that
it is the right port - without any luck.
Thanks in advance for you're help.
Have a nice day.
Here is the output from netstat -a maybe somebody can see from that
what port i'm supposed to use.
Active Connections
Proto Local Address Foreign Address State
TCP myserver:smtp myserver.domain.dk:0 LISTENING
TCP myserver:nameserver myserver.domain.dk:0 LISTENING
TCP myserver:domain myserver.domain.dk:0 LISTENING
TCP myserver:http myserver.domain.dk:0 LISTENING
TCP myserver:kerberos myserver.domain.dk:0 LISTENING
TCP myserver:epmap myserver.domain.dk:0 LISTENING
TCP myserver:imap myserver.domain.dk:0 LISTENING
TCP myserver:ldap myserver.domain.dk:0 LISTENING
TCP myserver:https myserver.domain.dk:0 LISTENING
TCP myserver:444 myserver.domain.dk:0 LISTENING
TCP myserver:microsoft-ds myserver.domain.dk:0 LISTENING
TCP myserver:kpasswd myserver.domain.dk:0 LISTENING
TCP myserver:593 myserver.domain.dk:0 LISTENING
TCP myserver:ldaps myserver.domain.dk:0 LISTENING
TCP myserver:691 myserver.domain.dk:0 LISTENING
TCP myserver:993 myserver.domain.dk:0 LISTENING
TCP myserver:1025 myserver.domain.dk:0 LISTENING
TCP myserver:1027 myserver.domain.dk:0 LISTENING
TCP myserver:1069 myserver.domain.dk:0 LISTENING
TCP myserver:1094 myserver.domain.dk:0 LISTENING
TCP myserver:1103 myserver.domain.dk:0 LISTENING
TCP myserver:1104 myserver.domain.dk:0 LISTENING
TCP myserver:1105 myserver.domain.dk:0 LISTENING
TCP myserver:1106 myserver.domain.dk:0 LISTENING
TCP myserver:1116 myserver.domain.dk:0 LISTENING
TCP myserver:1148 myserver.domain.dk:0 LISTENING
TCP myserver:1150 myserver.domain.dk:0 LISTENING
TCP myserver:1184 myserver.domain.dk:0 LISTENING
TCP myserver:1192 myserver.domain.dk:0 LISTENING
TCP myserver:1370 myserver.domain.dk:0 LISTENING
TCP myserver:ms-sql-s myserver.domain.dk:0 LISTENING
TCP myserver:3268 myserver.domain.dk:0 LISTENING
TCP myserver:3269 myserver.domain.dk:0 LISTENING
TCP myserver:3389 myserver.domain.dk:0 LISTENING
TCP myserver:4485 myserver.domain.dk:0 LISTENING
TCP myserver:4486 myserver.domain.dk:0 LISTENING
TCP myserver:4487 myserver.domain.dk:0 LISTENING
TCP myserver:4791 myserver.domain.dk:0 LISTENING
TCP myserver:5225 myserver.domain.dk:0 LISTENING
TCP myserver:5226 myserver.domain.dk:0 LISTENING
TCP myserver:5989 myserver.domain.dk:0 LISTENING
TCP myserver:6001 myserver.domain.dk:0 LISTENING
TCP myserver:6002 myserver.domain.dk:0 LISTENING
TCP myserver:6004 myserver.domain.dk:0 LISTENING
TCP myserver:7560 myserver.domain.dk:0 LISTENING
TCP myserver:8008 myserver.domain.dk:0 LISTENING
TCP myserver:8081 myserver.domain.dk:0 LISTENING
TCP myserver:19226 myserver.domain.dk:0 LISTENING
TCP myserver:23164 myserver.domain.dk:0 LISTENING
TCP myserver:23165 myserver.domain.dk:0 LISTENING
TCP myserver:domain myserver.domain.dk:0 LISTENING
TCP myserver:ldap myserver.domain.dk:5918 TIME_WAIT
TCP myserver:ldap myserver.domain.dk:57373 ESTABLISHED
TCP myserver:1133 myserver.domain.dk:0 LISTENING
TCP myserver:1133 myserver.domain.dk:1134 ESTABLISHED
TCP myserver:1134 myserver.domain.dk:1133 ESTABLISHED
TCP myserver:1206 myserver.domain.dk:0 LISTENING
TCP myserver:2301 myserver.domain.dk:0 LISTENING
TCP myserver:2381 myserver.domain.dk:0 LISTENING
TCP myserver:4663 myserver.domain.dk:5225 CLOSE_WAIT
TCP myserver:4669 myserver.domain.dk:5225 CLOSE_WAIT
TCP myserver:5226 myserver.domain.dk:42330 ESTABLISHED
TCP myserver:8005 myserver.domain.dk:0 LISTENING
TCP myserver:42330 myserver.domain.dk:5226 ESTABLISHED
TCP myserver:57373 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:epmap myserver.domain.dk:5927 ESTABLISHED
TCP myserver:netbios-ssn myserver.domain.dk:0 LISTENING
TCP myserver:ldap myserver.domain.dk:1115 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:5895 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:5911 TIME_WAIT
TCP myserver:ldap myserver.domain.dk:5923 TIME_WAIT
TCP myserver:ldap myserver.domain.dk:57369 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57370 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57371 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57380 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57381 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57382 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57383 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57384 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57386 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57387 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57390 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57391 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57392 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57393 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57394 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57395 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57396 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57412 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57422 ESTABLISHED
TCP myserver:ldap myserver.domain.dk:57430 ESTABLISHED
TCP myserver:691 myserver.domain.dk:1131 ESTABLISHED
TCP myserver:691 myserver.domain.dk:1190 ESTABLISHED
TCP myserver:691 myserver.domain.dk:1197 ESTABLISHED
TCP myserver:1025 myserver.domain.dk:1098 ESTABLISHED
TCP myserver:1025 myserver.domain.dk:1222 ESTABLISHED
TCP myserver:1025 myserver.domain.dk:1245 ESTABLISHED
TCP myserver:1025 myserver.domain.dk:1503 ESTABLISHED
TCP myserver:1025 myserver.domain.dk:2158 ESTABLISHED
TCP myserver:1025 myserver.domain.dk:51771 ESTABLISHED
TCP myserver:1081 myserver.domain.dk:4791 ESTABLISHED
TCP myserver:1098 myserver.domain.dk:1025 ESTABLISHED
TCP myserver:1115 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:1131 myserver.domain.dk:691 ESTABLISHED
TCP myserver:1142 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:1148 myserver.domain.dk:5928 ESTABLISHED
TCP myserver:1173 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:1174 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:1176 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:1177 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:1178 myserver.domain.dk:3268 CLOSE_WAIT
TCP myserver:1179 myserver.domain.dk:3268 CLOSE_WAIT
TCP myserver:1190 myserver.domain.dk:691 ESTABLISHED
TCP myserver:1197 myserver.domain.dk:691 ESTABLISHED
TCP myserver:1222 myserver.domain.dk:1025 ESTABLISHED
TCP myserver:1245 myserver.domain.dk:1025 ESTABLISHED
TCP myserver:1503 myserver.domain.dk:1025 ESTABLISHED
TCP myserver:2158 myserver.domain.dk:1025 ESTABLISHED
TCP myserver:2301 myserver.domain.dk:0 LISTENING
TCP myserver:2381 myserver.domain.dk:0 LISTENING
TCP myserver:3268 myserver.domain.dk:4693 ESTABLISHED
TCP myserver:3268 myserver.domain.dk:57376 ESTABLISHED
TCP myserver:3268 myserver.domain.dk:57378 ESTABLISHED
TCP myserver:3268 myserver.domain.dk:57379 ESTABLISHED
TCP myserver:3268 myserver.domain.dk:57388 ESTABLISHED
TCP myserver:3522 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:3602 myserver.domain.dk:3268 CLOSE_WAIT
TCP myserver:3603 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:3633 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:4693 myserver.domain.dk:3268 ESTABLISHED
TCP myserver:4791 myserver.domain.dk:1081 ESTABLISHED
TCP myserver:4972 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:5286 myserver.domain.dk:3268 CLOSE_WAIT
TCP myserver:5511 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:5895 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:5907 myserver.domain.dk:epmap TIME_WAIT
TCP myserver:5908 myserver.domain.dk:epmap TIME_WAIT
TCP myserver:5909 myserver.domain.dk:epmap TIME_WAIT
TCP myserver:5910 myserver.domain.dk:1025 TIME_WAIT
TCP myserver:5911 myserver.domain.dk:ldap TIME_WAIT
TCP myserver:5912 myserver.domain.dk:ldap TIME_WAIT
TCP myserver:5919 myserver.domain.dk:ldap TIME_WAIT
TCP myserver:5920 myserver.domain.dk:3268 TIME_WAIT
TCP myserver:5921 myserver.domain.dk:domain TIME_WAIT
TCP myserver:5922 myserver.domain.dk:domain TIME_WAIT
TCP myserver:5927 myserver.domain.dk:epmap ESTABLISHED
TCP myserver:5928 myserver.domain.dk:1148 ESTABLISHED
TCP myserver:25872 myserver.domain.dk:ldap CLOSE_WAIT
TCP myserver:49366 myserver.domain.dk:3268 CLOSE_WAIT
TCP myserver:51771 myserver.domain.dk:1025 ESTABLISHED
TCP myserver:57369 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57370 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57371 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57376 myserver.domain.dk:3268 ESTABLISHED
TCP myserver:57378 myserver.domain.dk:3268 ESTABLISHED
TCP myserver:57379 myserver.domain.dk:3268 ESTABLISHED
TCP myserver:57380 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57381 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57382 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57383 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57384 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57386 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57387 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57388 myserver.domain.dk:3268 ESTABLISHED
TCP myserver:57390 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57391 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57392 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57393 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57394 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57395 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57396 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57412 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57422 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:57430 myserver.domain.dk:ldap ESTABLISHED
TCP myserver:59543 myserver.domain.dk:ldap CLOSE_WAIT
UDP myserver:nameserver *:*
UDP myserver:epmap *:*
UDP myserver:snmp *:*
UDP myserver:microsoft-ds *:*
UDP myserver:isakmp *:*
UDP myserver:1038 *:*
UDP myserver:1066 *:*
UDP myserver:1117 *:*
UDP myserver:1135 *:*
UDP myserver:1136 *:*
UDP myserver:1151 *:*
UDP myserver:1193 *:*
UDP myserver:1246 *:*
UDP myserver:ms-sql-m *:*
UDP myserver:3456 *:*
UDP myserver:3457 *:*
UDP myserver:4500 *:*
UDP myserver:4670 *:*
UDP myserver:16826 *:*
UDP myserver:16828 *:*
UDP myserver:16830 *:*
UDP myserver:16994 *:*
UDP myserver:16995 *:*
UDP myserver:16997 *:*
UDP myserver:19226 *:*
UDP myserver:27140 *:*
UDP myserver:42308 *:*
UDP myserver:domain *:*
UDP myserver:1065 *:*
UDP myserver:1067 *:*
UDP myserver:1095 *:*
UDP myserver:1118 *:*
UDP myserver:1141 *:*
UDP myserver:1147 *:*
UDP myserver:1152 *:*
UDP myserver:1185 *:*
UDP myserver:1194 *:*
UDP myserver:1201 *:*
UDP myserver:1207 *:*
UDP myserver:1216 *:*
UDP myserver:1427 *:*
UDP myserver:1599 *:*
UDP myserver:3456 *:*
UDP myserver:3457 *:*
UDP myserver:5904 *:*
UDP myserver:5982 *:*
UDP myserver:7272 *:*
UDP myserver:11974 *:*
UDP myserver:24647 *:*
UDP myserver:42247 *:*
UDP myserver:42439 *:*
UDP myserver:domain *:*
UDP myserver:bootps *:*
UDP myserver:bootpc *:*
UDP myserver:kerberos *:*
UDP myserver:netbios-ns *:*
UDP myserver:netbios-dgm *:*
UDP myserver:389 *:*
UDP myserver:427 *:*
UDP myserver:kpasswd *:*
UDP myserver:1328 *:*
UDP myserver:2535 *:*
|||Ah, by default, SQL Server 2005 named instances use dynamic port
assignments. That is, when the instance is started (each time it's started)
it asks the OS for an open port. The SQL Browser service monitors these
assignments and reports this port assignment back to any application
attempting to connect. Hard-coding a port (therefore) is problematic at
best. If you must get a static port, you have to use SQL Server
Configuration Manager to change the port config.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Tokatrash" <martin@.deamon.dk> wrote in message
news:1183020630.563134.253610@.q75g2000hsh.googlegr oups.com...
> Here is the output from netstat -a maybe somebody can see from that
> what port i'm supposed to use.
> Active Connections
> Proto Local Address Foreign Address State
> TCP myserver:smtp myserver.domain.dk:0 LISTENING
> TCP myserver:nameserver myserver.domain.dk:0 LISTENING
> TCP myserver:domain myserver.domain.dk:0 LISTENING
> TCP myserver:http myserver.domain.dk:0 LISTENING
> TCP myserver:kerberos myserver.domain.dk:0 LISTENING
> TCP myserver:epmap myserver.domain.dk:0 LISTENING
> TCP myserver:imap myserver.domain.dk:0 LISTENING
> TCP myserver:ldap myserver.domain.dk:0 LISTENING
> TCP myserver:https myserver.domain.dk:0 LISTENING
> TCP myserver:444 myserver.domain.dk:0 LISTENING
> TCP myserver:microsoft-ds myserver.domain.dk:0 LISTENING
> TCP myserver:kpasswd myserver.domain.dk:0 LISTENING
> TCP myserver:593 myserver.domain.dk:0 LISTENING
> TCP myserver:ldaps myserver.domain.dk:0 LISTENING
> TCP myserver:691 myserver.domain.dk:0 LISTENING
> TCP myserver:993 myserver.domain.dk:0 LISTENING
> TCP myserver:1025 myserver.domain.dk:0 LISTENING
> TCP myserver:1027 myserver.domain.dk:0 LISTENING
> TCP myserver:1069 myserver.domain.dk:0 LISTENING
> TCP myserver:1094 myserver.domain.dk:0 LISTENING
> TCP myserver:1103 myserver.domain.dk:0 LISTENING
> TCP myserver:1104 myserver.domain.dk:0 LISTENING
> TCP myserver:1105 myserver.domain.dk:0 LISTENING
> TCP myserver:1106 myserver.domain.dk:0 LISTENING
> TCP myserver:1116 myserver.domain.dk:0 LISTENING
> TCP myserver:1148 myserver.domain.dk:0 LISTENING
> TCP myserver:1150 myserver.domain.dk:0 LISTENING
> TCP myserver:1184 myserver.domain.dk:0 LISTENING
> TCP myserver:1192 myserver.domain.dk:0 LISTENING
> TCP myserver:1370 myserver.domain.dk:0 LISTENING
> TCP myserver:ms-sql-s myserver.domain.dk:0 LISTENING
> TCP myserver:3268 myserver.domain.dk:0 LISTENING
> TCP myserver:3269 myserver.domain.dk:0 LISTENING
> TCP myserver:3389 myserver.domain.dk:0 LISTENING
> TCP myserver:4485 myserver.domain.dk:0 LISTENING
> TCP myserver:4486 myserver.domain.dk:0 LISTENING
> TCP myserver:4487 myserver.domain.dk:0 LISTENING
> TCP myserver:4791 myserver.domain.dk:0 LISTENING
> TCP myserver:5225 myserver.domain.dk:0 LISTENING
> TCP myserver:5226 myserver.domain.dk:0 LISTENING
> TCP myserver:5989 myserver.domain.dk:0 LISTENING
> TCP myserver:6001 myserver.domain.dk:0 LISTENING
> TCP myserver:6002 myserver.domain.dk:0 LISTENING
> TCP myserver:6004 myserver.domain.dk:0 LISTENING
> TCP myserver:7560 myserver.domain.dk:0 LISTENING
> TCP myserver:8008 myserver.domain.dk:0 LISTENING
> TCP myserver:8081 myserver.domain.dk:0 LISTENING
> TCP myserver:19226 myserver.domain.dk:0 LISTENING
> TCP myserver:23164 myserver.domain.dk:0 LISTENING
> TCP myserver:23165 myserver.domain.dk:0 LISTENING
> TCP myserver:domain myserver.domain.dk:0 LISTENING
> TCP myserver:ldap myserver.domain.dk:5918 TIME_WAIT
> TCP myserver:ldap myserver.domain.dk:57373 ESTABLISHED
> TCP myserver:1133 myserver.domain.dk:0 LISTENING
> TCP myserver:1133 myserver.domain.dk:1134 ESTABLISHED
> TCP myserver:1134 myserver.domain.dk:1133 ESTABLISHED
> TCP myserver:1206 myserver.domain.dk:0 LISTENING
> TCP myserver:2301 myserver.domain.dk:0 LISTENING
> TCP myserver:2381 myserver.domain.dk:0 LISTENING
> TCP myserver:4663 myserver.domain.dk:5225 CLOSE_WAIT
> TCP myserver:4669 myserver.domain.dk:5225 CLOSE_WAIT
> TCP myserver:5226 myserver.domain.dk:42330 ESTABLISHED
> TCP myserver:8005 myserver.domain.dk:0 LISTENING
> TCP myserver:42330 myserver.domain.dk:5226 ESTABLISHED
> TCP myserver:57373 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:epmap myserver.domain.dk:5927 ESTABLISHED
> TCP myserver:netbios-ssn myserver.domain.dk:0 LISTENING
> TCP myserver:ldap myserver.domain.dk:1115 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:5895 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:5911 TIME_WAIT
> TCP myserver:ldap myserver.domain.dk:5923 TIME_WAIT
> TCP myserver:ldap myserver.domain.dk:57369 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57370 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57371 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57380 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57381 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57382 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57383 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57384 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57386 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57387 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57390 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57391 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57392 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57393 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57394 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57395 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57396 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57412 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57422 ESTABLISHED
> TCP myserver:ldap myserver.domain.dk:57430 ESTABLISHED
> TCP myserver:691 myserver.domain.dk:1131 ESTABLISHED
> TCP myserver:691 myserver.domain.dk:1190 ESTABLISHED
> TCP myserver:691 myserver.domain.dk:1197 ESTABLISHED
> TCP myserver:1025 myserver.domain.dk:1098 ESTABLISHED
> TCP myserver:1025 myserver.domain.dk:1222 ESTABLISHED
> TCP myserver:1025 myserver.domain.dk:1245 ESTABLISHED
> TCP myserver:1025 myserver.domain.dk:1503 ESTABLISHED
> TCP myserver:1025 myserver.domain.dk:2158 ESTABLISHED
> TCP myserver:1025 myserver.domain.dk:51771 ESTABLISHED
> TCP myserver:1081 myserver.domain.dk:4791 ESTABLISHED
> TCP myserver:1098 myserver.domain.dk:1025 ESTABLISHED
> TCP myserver:1115 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:1131 myserver.domain.dk:691 ESTABLISHED
> TCP myserver:1142 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:1148 myserver.domain.dk:5928 ESTABLISHED
> TCP myserver:1173 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:1174 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:1176 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:1177 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:1178 myserver.domain.dk:3268 CLOSE_WAIT
> TCP myserver:1179 myserver.domain.dk:3268 CLOSE_WAIT
> TCP myserver:1190 myserver.domain.dk:691 ESTABLISHED
> TCP myserver:1197 myserver.domain.dk:691 ESTABLISHED
> TCP myserver:1222 myserver.domain.dk:1025 ESTABLISHED
> TCP myserver:1245 myserver.domain.dk:1025 ESTABLISHED
> TCP myserver:1503 myserver.domain.dk:1025 ESTABLISHED
> TCP myserver:2158 myserver.domain.dk:1025 ESTABLISHED
> TCP myserver:2301 myserver.domain.dk:0 LISTENING
> TCP myserver:2381 myserver.domain.dk:0 LISTENING
> TCP myserver:3268 myserver.domain.dk:4693 ESTABLISHED
> TCP myserver:3268 myserver.domain.dk:57376 ESTABLISHED
> TCP myserver:3268 myserver.domain.dk:57378 ESTABLISHED
> TCP myserver:3268 myserver.domain.dk:57379 ESTABLISHED
> TCP myserver:3268 myserver.domain.dk:57388 ESTABLISHED
> TCP myserver:3522 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:3602 myserver.domain.dk:3268 CLOSE_WAIT
> TCP myserver:3603 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:3633 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:4693 myserver.domain.dk:3268 ESTABLISHED
> TCP myserver:4791 myserver.domain.dk:1081 ESTABLISHED
> TCP myserver:4972 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:5286 myserver.domain.dk:3268 CLOSE_WAIT
> TCP myserver:5511 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:5895 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:5907 myserver.domain.dk:epmap TIME_WAIT
> TCP myserver:5908 myserver.domain.dk:epmap TIME_WAIT
> TCP myserver:5909 myserver.domain.dk:epmap TIME_WAIT
> TCP myserver:5910 myserver.domain.dk:1025 TIME_WAIT
> TCP myserver:5911 myserver.domain.dk:ldap TIME_WAIT
> TCP myserver:5912 myserver.domain.dk:ldap TIME_WAIT
> TCP myserver:5919 myserver.domain.dk:ldap TIME_WAIT
> TCP myserver:5920 myserver.domain.dk:3268 TIME_WAIT
> TCP myserver:5921 myserver.domain.dk:domain TIME_WAIT
> TCP myserver:5922 myserver.domain.dk:domain TIME_WAIT
> TCP myserver:5927 myserver.domain.dk:epmap ESTABLISHED
> TCP myserver:5928 myserver.domain.dk:1148 ESTABLISHED
> TCP myserver:25872 myserver.domain.dk:ldap CLOSE_WAIT
> TCP myserver:49366 myserver.domain.dk:3268 CLOSE_WAIT
> TCP myserver:51771 myserver.domain.dk:1025 ESTABLISHED
> TCP myserver:57369 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57370 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57371 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57376 myserver.domain.dk:3268 ESTABLISHED
> TCP myserver:57378 myserver.domain.dk:3268 ESTABLISHED
> TCP myserver:57379 myserver.domain.dk:3268 ESTABLISHED
> TCP myserver:57380 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57381 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57382 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57383 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57384 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57386 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57387 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57388 myserver.domain.dk:3268 ESTABLISHED
> TCP myserver:57390 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57391 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57392 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57393 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57394 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57395 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57396 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57412 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57422 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:57430 myserver.domain.dk:ldap ESTABLISHED
> TCP myserver:59543 myserver.domain.dk:ldap CLOSE_WAIT
> UDP myserver:nameserver *:*
> UDP myserver:epmap *:*
> UDP myserver:snmp *:*
> UDP myserver:microsoft-ds *:*
> UDP myserver:isakmp *:*
> UDP myserver:1038 *:*
> UDP myserver:1066 *:*
> UDP myserver:1117 *:*
> UDP myserver:1135 *:*
> UDP myserver:1136 *:*
> UDP myserver:1151 *:*
> UDP myserver:1193 *:*
> UDP myserver:1246 *:*
> UDP myserver:ms-sql-m *:*
> UDP myserver:3456 *:*
> UDP myserver:3457 *:*
> UDP myserver:4500 *:*
> UDP myserver:4670 *:*
> UDP myserver:16826 *:*
> UDP myserver:16828 *:*
> UDP myserver:16830 *:*
> UDP myserver:16994 *:*
> UDP myserver:16995 *:*
> UDP myserver:16997 *:*
> UDP myserver:19226 *:*
> UDP myserver:27140 *:*
> UDP myserver:42308 *:*
> UDP myserver:domain *:*
> UDP myserver:1065 *:*
> UDP myserver:1067 *:*
> UDP myserver:1095 *:*
> UDP myserver:1118 *:*
> UDP myserver:1141 *:*
> UDP myserver:1147 *:*
> UDP myserver:1152 *:*
> UDP myserver:1185 *:*
> UDP myserver:1194 *:*
> UDP myserver:1201 *:*
> UDP myserver:1207 *:*
> UDP myserver:1216 *:*
> UDP myserver:1427 *:*
> UDP myserver:1599 *:*
> UDP myserver:3456 *:*
> UDP myserver:3457 *:*
> UDP myserver:5904 *:*
> UDP myserver:5982 *:*
> UDP myserver:7272 *:*
> UDP myserver:11974 *:*
> UDP myserver:24647 *:*
> UDP myserver:42247 *:*
> UDP myserver:42439 *:*
> UDP myserver:domain *:*
> UDP myserver:bootps *:*
> UDP myserver:bootpc *:*
> UDP myserver:kerberos *:*
> UDP myserver:netbios-ns *:*
> UDP myserver:netbios-dgm *:*
> UDP myserver:389 *:*
> UDP myserver:427 *:*
> UDP myserver:kpasswd *:*
> UDP myserver:1328 *:*
> UDP myserver:2535 *:*
>
|||On 28 Jun., 17:52, "William \(Bill\) Vaughn"
<billvaRemoveT...@.betav.com> wrote:
> Ah, by default, SQL Server 2005 named instances use dynamic port
> assignments. That is, when the instance is started (each time it's started)
> it asks the OS for an open port. The SQL Browser service monitors these
> assignments and reports this port assignment back to any application
> attempting to connect. Hard-coding a port (therefore) is problematic at
> best. If you must get a static port, you have to use SQL Server
> Configuration Manager to change the port config.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speakerwww.betav.com/blog/billvawww.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Tokatrash" <mar...@.deamon.dk> wrote in message
> news:1183020630.563134.253610@.q75g2000hsh.googlegr oups.com...
>
>
> ...
> ls mere
I need to get a remote connection to the server trough a firewall.
Do you know a way to make that possible besides using a static port
and NAT?
Thanks for youre help.
|||The problem is, since the server can (might) reassign the port number when
the service is started, it's impossible to open a specific port in the
firewall. Microsoft's (and my) recommendation is to use static IP
assignments.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Tokatrash" <martin@.deamon.dk> wrote in message
news:1183477208.003917.49190@.q75g2000hsh.googlegro ups.com...
On 28 Jun., 17:52, "William \(Bill\) Vaughn"
<billvaRemoveT...@.betav.com> wrote:
> Ah, by default, SQL Server 2005 named instances use dynamic port
> assignments. That is, when the instance is started (each time it's
> started)
> it asks the OS for an open port. The SQL Browser service monitors these
> assignments and reports this port assignment back to any application
> attempting to connect. Hard-coding a port (therefore) is problematic at
> best. If you must get a static port, you have to use SQL Server
> Configuration Manager to change the port config.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speakerwww.betav.com/blog/billvawww.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visitwww.hitchhikerguides.netto get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Tokatrash" <mar...@.deamon.dk> wrote in message
> news:1183020630.563134.253610@.q75g2000hsh.googlegr oups.com...
>
>
> ...
> ls mere
I need to get a remote connection to the server trough a firewall.
Do you know a way to make that possible besides using a static port
and NAT?
Thanks for youre help.
|||On 4 Jul., 22:43, "William \(Bill\) Vaughn"
<billvaRemoveT...@.betav.com> wrote:
> The problem is, since the server can (might) reassign the port number when
> the service is started, it's impossible to open a specific port in the
> firewall. Microsoft's (and my) recommendation is to use static IP
> assignments.
That's sadly just not a possebility as their security policy doesn't
allow every port to be open.
Gues i gotta find a VPN solution then.
Thanks a thousand for all you're help!!!