Showing posts with label locally. Show all posts
Showing posts with label locally. Show all posts

Wednesday, March 21, 2012

Remote SSIS Access

Hello,
We have discovered that unless a user is an administrator on the MS SQL 2005
server, they cannot connect to SSIS server locally or remotely.
The SQL Junkies site has the solution. They recommend that you first add the
user to the Distributed COM Users group. Then you should run
%windir%\system32\Com\comexp.msc to launch Component Services to launch
component server. On the properties of MsDtsServer you can choose security
and from there you can set the Remote Activation permissions to allow the
user to connect the SSIS server remotely. The SSIS service should then be
restarted.
I tried it and it works. However, what are the security implications with
this solution?The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:

>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>|||The implications are basically just what you set - you allow
that user to connect remotely to the process for
MsDtsServer. Not much outside of that really - you're only
changing this for SSIS and that particular user.
-Sue
On Thu, 8 Jun 2006 14:04:04 -0600, "Loren Zubis"
<Loren.Zubis@.gov.ab.ca> wrote:

>Hello,
>We have discovered that unless a user is an administrator on the MS SQL 200
5
>server, they cannot connect to SSIS server locally or remotely.
>The SQL Junkies site has the solution. They recommend that you first add th
e
>user to the Distributed COM Users group. Then you should run
>%windir%\system32\Com\comexp.msc to launch Component Services to launch
>component server. On the properties of MsDtsServer you can choose security
>and from there you can set the Remote Activation permissions to allow the
>user to connect the SSIS server remotely. The SSIS service should then be
>restarted.
>I tried it and it works. However, what are the security implications with
>this solution?
>

Remote SQL Server 2000 Perfmon Not Working

I have a SQL Server 2000 cluster running on x64 OS. I found the threads in the forum to run perfmon locally by using the x86 version of perfmon (mmc /32 perfmon). However, I cannot run a perfmon remotely from another machine and see the SQL Server perfmon data on any of the nodes in the cluster. The remote perfmon picks up all of the other perfmon variables but no SQL.

I found another thread where somebody asked this question but it wasn't answered. Thanks in advance.

Mark

there is no x64 counter.|||Absolutely correct. There is no x64 SQL 2000 counter which is why one must run the 32-bit version of perfmon. I can run the 32-bit perfmon locally on my cluster nodes and see the 32-bit SQL performance counters but I am unable to run perfmon from a remote machine, connect to one of my cluster nodes and see the SQL counters.|||

What do you mean by "remote computer"? Are you trying to do this across the Internet or VPN or what?

Perfmon depends on the "named pipes" protocol and will never work across the Internet because NetBios is blocked by most ISPs.

|||

We are in the process of setting up Operations Manager to collect perf data. Until then we are stuck with a management server that has perfmon running on it centrally collecting data from various servers. I can see other performance counters, just not the ones for SQL Server.

The management server and the SQL cluster are on the same LAN/subnet without any type of firewall between them. I have a test cluster that is doing the exact same thing. Sad

Monday, February 20, 2012

Remote connection problems

I have a Windows 2003 server running SQL Server 2005. I can connect locally via TCP/IP and I've followed all the recommended steps to enable TCP/IP and remote connections.

However, I cannot connect remotely from my desktop machine (different LAN) using the SQL Management Studio, not will the same connection string work on a webserver that's on a different machine.

My connection string is:

Dim objConn, objRS, strConn, strSQL, Email_Number, Template
strConn = "Driver={SQL Server};Server=88.208.229.121;Database=test;Uid=XXX;Pwd=YYY;"
Set objConn = Server.CreateObject("ADODB.Connection")
objConn.Open strConn

The error that I'm getting on the client with management studio is that the remote database is not available and most probably because TCP/IP was not enabled!

The error that I'm getting through classic ASP on the remote web is:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

Keep in mind I can use the exact same connection string and ASP and connect on the local machine, no problems.

Any help in this matter will be greatly appreciated.

Thanks
Riaan
London

Is there a firewall (esp. Windows firewall) between your computer and the server?

Have you enabled remote connections (using the Surface Configuration tool)?

Have you enabled TCP/IP?

Check these resources:

Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277

Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

|||Hi

There is no firewall on the server, and from this location I connect through a broadband router that has the standard type of protection.

Yes, remote connections and TCP/IP are enabled.

I actually followed the steps from the first article.

Riaan|||I've done every step in the mentioned articles as above and neither of my two web servers at my ISP are running Windows Firewall. They are both at the same ISP and as I said, with the connection string I use I can browse the DB from classic ASP on the server that runs SQL, but not from another server that just runs IIS.

Is there anywhere else I should look?

Riaan
London|||

I noticed that your server bridges two networks.

It is possible that the problem lies there due to the added complexity involved in dealing with two networks simultaneously.

It will have two ip addresses, one for network 1 and another for network 2. You cannot connect to the network 1 ip from network 2. From your local machine you can "see" both networks and both network cards, so it will be able to connect to either ip address. Only remotely does it matter which identifier you use for your server (assuming that the configuration of your server is absolutely perfect) because again the server bridges two networks. So have you tried the other ip address to make sure you aren't using network 1's ip address to try to access the server from network 2?

Additionally, you will have to make sure that you have enabled it for both network interfaces -- this requirement is there to allow differentiation between trusted and untrusted networks but of course adds to the complexity of configuring the system to service two different networks.

I hope this helps,

John Gordon (MSFT)

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

Remote connection error - but everything installed locally?

I have a visual basic 2005 application where I am storing some data in a Sequel Server Database. It's my first attempt using SQL Server. It was developed on my machine and the database is on my local hard drive.

It was put onto an industrial PC and shipped last December (the vb app is an HMI).

Our service guy is installing the machine and asked for some changes to the VB screens. I ran my app (on my computer) and it crashed when I selected the screen where I use the db.

So I decided to look at the database using Visual Basic and I get the following error:

Microsoft Visual Basic 2005 Express Edition

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I then tried to create a new database via Visual Basic and get the same error. My boss has it installed on his machine. Same error there. These are both machines that had no problem back in December!

I also have a industrial PC on my desk to test my app and it STILL WORKS there. That one though is not connected to the internet and hasn't gotten any updates or changes or whatever since I last had it on in December. I don't know if it was a windows update or a network change? But as I said, I'm not connecting remotely - SQL Server and the db are on our local machines.

Interesting enough, if I go to the control panel | Administrative Tools | Services, SQL Server (SQLEXPRESS) is set to automatic and is NOT started. I attempt to start it and get an error

Services

Windows could not start the SQL Server (SQLEXPRESS) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 3417.

I am lost.

Thanks in advance for any help!

The concensus seems to be that this is related to compressed folders. Check out the posting here to check out where I got this crazy idea and the solutions that worked for others. I would also suggest checking out the log as the error recommends if you haven't already. Often the log contains more information that the error message. (Other times, it doesn't.)

Mike

|||

Thanks Mike!

There were several solutions listed at the link you provided. I tried in order:

1) compressed folder/files. I went to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data, right-clicked on each file. "Compress contents" was NOT checked. However I unchecked "ready to archive". I got a different error (instead of 26 it was 40) when I tried to create a new database.

2) I ran SQLdiag found in C:\Program Files\Microsoft SQL Server\90\Tools\Binn. It ran. There didn't seem to be a difference.

3) I right-clicked on SQLExpress in Services and changed the Log On to "Local System Account" with the box check. That did it for me.

Interesting enough, the industrial PC I have on my desk works and still has the Log On as "This Account" - but that's not connected to our server with any of our group policy stuff.

THANKS AGAIN Mike! I really appreciated your help.