Cannot connect to a named instance using SSMS from a remote machine

Hi all,
SQL Server.....: 2012 EE
OS...................: Windows Server 2008 R2
I have a desktop machine, that i am using to administrer SQL Server (via SSMS) and to develop my SSIS solutions, but i can't connect to a named instance of my SQL Server. When i try to connect using SSMS to my named instance (myhost\DWSERVER)
i get a huge error message:
A network-related or instance-specific error occurred while establisinh a connection to SQL Server. The server was not found or was not accessible. Verify that the instance is correct and that SQL Server is configured to allow remote connections.
(provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
Locally, i am able to access that named instance using SSMS, just when i try to access from another machine, the above error pops-up to me.
I am using the SQL Server Authentication mode to connect to the named instance.
What am i doing wrong?
Thanks in advance.
Fabrício Pedroso Jorge Database Administrator - Belém, Pará, Brazil

Hi,
thanks for your attention.
That's correct, i can connect to my default instance both locally and remotelly. The default instance in on port 1433. I cannot find the port used by the named instance (DWSERVER).
Actually, i found this on the errorlog from the named instance:
2015-03-22 10:10:45.80 spid13s Server is listening on [ 'any' <ipv6> 49411].
2015-03-22 10:10:45.80 spid20s Server is listening on [ 'any' <ipv6> 5023].
2015-03-22 10:10:45.81 spid20s Server is listening on [ 'any' <ipv4> 5023].
2015-03-22 10:10:45.81 spid20s The Database Mirroring endpoint is now listening for connections.
2015-03-22 10:10:46.12 spid13s Server is listening on [ 'any' <ipv4> 49411].
2015-03-22 10:10:46.25 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\DWSERVER ].
2015-03-22 10:10:46.26 spid13s Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$DWSERVER\sql\query ].
2015-03-22 10:10:46.26 Server Server is listening on [ ::1 <ipv6> 49412].
2015-03-22 10:10:46.26 Server Server is listening on [ 127.0.0.1 <ipv4> 49412].
I can ping normally to the remote server.
Fabrício Pedroso Jorge Database Administrator - Belém, Pará, Brazil

Similar Messages

Sql server 2012 express - tcp/ip connection to named instance using dynamic port not working

I have a named instance on a SQL 2012 Express server that won't connect via TCP/IP when wanting to connect off of the dynamic port. I can connect via shared memory locally on the server.   I can connect to the namespace when specifying the
dynamic port listed in the configuration manager.
This is the only named instance on the server and it is not the default.
TCP/IP is enabled
Allow Remote connections is enabled
the server browser service is running
I can connect via the dynamic port number
I am testing the connection locally on the server, so I don't believe a firewall is the issue. I get the same results if I test it from a remote computer.
When using the sqlcmd (sqlcmd -S tcp:SQLSRVR\NAMEINST -E) I get the message that "the requested protocol isn't supported [xfffffffff]".   The command (sqlcmd -S tcp:SQLSRVR\NAMEINST,59992 -E) works.
Through SSMS, I get the message "the connection was actively refused".
On other boxes, I can connect with the named instance without having to specify the port.
I have looked through the sql logs and nothing much shows up. The log does show that is listening on the port # for ipv4 and ipv6.   There is also a line in there talking about the SPN not being registered and not to worry about it if
you are not using Kerberos. I logged in through shared memory and it said I was using NTLM.
Any help would be appreciated.
thanks.

Hi clw,
I’m writing to follow up with you on this post. According to your description, I do a test, if you configure the database engine to listen on a specific TCP port (59992), and
the port is opened in the firewall. If you want to connect to the SQL Server instance, you 'd better to
use the port number.
In my opinion, by default, the default instance of the Database Engine uses port 1433, usually, if you have configured the server to listen on a non-default port number, when an instance of SQL Server uses dynamic port allocation, the connection string that
is built at the SQL Server client does not specify the destination TCP/IP port unless the user or the programmer explicitly specifies the port. Therefore, the SQL Server client library queries the server on UDP port 1434 to collect the information about the
destination instance of SQL Server.
If UDP port 1434 is disabled, the SQL Server client cannot dynamically determine the port of the named instance of SQL Server. Therefore, the SQL Server client may be unable to connect to the named instance of SQL Server. In this situation, the SQL Server
client must specify the dynamically allocated port where the named instance of SQL Server is listening.
For more information about configuring an instance of SQL Server to listen on a specific TCP port or dynamic port, you can review the following article.
https://support.transfrm.com/entries/503111-How-to-configure-an-instance-of-SQL-Server-to-listen-on-a-specific-TCP-port-or-dynamic-port
Thanks,
Sofiya Li
Sofiya Li
TechNet Community Support

SSAS 2012 (SP2) - Connecting to a Named Instance in a Failover Cluster

I posted this question some months ago and never got a resolution...still having the same problem. (http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4178ba62-87e2-4672-a4ef-acd970ac1011/ssas-2012-sp1-connecting-to-a-named-instance-in-a-failover-cluster?forum=sqlanalysisservices)
I have a 3 node failover cluster installation (active-passive-passive) configured as follows:
Node1: DB Engine 1 (named instance DB01)
Node2: DB Engine 2 (named instance DB02)
Node3: Analysis Services (named instance DBAS)
Obviously, the node indicated is merely the default active node for each service, with each service able to fail from node to node as required.
Strangely, when I attempt to connect to the SSAS node using the cluster netbios "alias" (dunno, what else it would be called, so I apologize if I am mixing terminology or somesuch), I am only able to do so by specifying the the alias _without_ the
required named instance. If I issue a connection request using an external program or even SSMS using Node3\DBAS or Node3.domain\DBAS, it appears that the SQL Server Browser is offering up a bogus TCP port for the named instance (in my case TCP/58554), when
in reality, the SSAS service is running on TCP/2383 (confirmed with netstat) -- which if I understand correctly after much, much reading on the subject is the only port that can be used in a failover cluster. In any case, I'm puzzled beyond words. As I think
through it, I believe I've seen this issue in the past, but never worried about it since it wasn't necessary to specify the named instance when I had SSAS requirements... It's only a showstopper now because I'm finalizing my implementation of SCVMM/SCOM 2012
R2, and for some strange reason the PRO configuration in VMM gets all butthurt if you don't offer up a named instance...
Thank you much for reading. I appreciate any help to get this resolved.
POSSIBLY NOT RELEVANT...?
I've properly configured the SPNs for the SSAS service (MSOLAPSvc.3) and the SQL Browser (MSOLAPDisco.3), with the former mapped to the SSAS service account and the latter to the cluster "alias" (since it runs as "NT AUTHORITY\LOCALSERVICE"
as is customary) and have permitted delegation on the service and machine accounts as required. So, I'm not getting any kerberos issues with the service...any more, that is... ;) I'm not sure that's important, but I wanted to be forthcoming with details to
help solve the issue.

When connecting to SSAS in a cluster, you do not specify an instance name. In your case, you would use the name of the SSAS IP address to connect.
See:
http://msdn.microsoft.com/en-us/library/dn141153.aspx
For servers deployed in a failover cluster, connect using the network name of the SSAS cluster. This name is specified during SQL Server setup, as
SQL Server Network Name. Note that if you installed SSAS as a named instance onto a Windows Server Failover Cluster (WSFC), you never add the instance name on the connection. This practice is unique to SSAS; in contrast, a named
instance of a clustered relational database engine does include the instance name. For example, if you installed both SSAS and the database engine as named instance (Contoso-Accounting) with a SQL Server Network Name of SQL-CLU, you would connect to SSAS using
"SQL-CLU" and to the database engine as "SQL-CLU\Contoso-Accounting". See
How to Cluster SQL Server Analysis Services for more information and examples.

How to restart base station from airport utility? I used to be able to do it remotely I currently use a Mac Pro 10.8.4 and have a time machine for wireless 6.3 (630.34). Sometimes I cannot connect to the internet and use network preferences to diagnose t

How to restart base station from airport utility? I used to be able to do it remotely
I currently use a Mac Pro 10.8.4 and have a time machine for wireless 6.3 (630.34). Sometimes I cannot connect to the internet and use network preferences to diagnose the issue. This results in being told to restart the wireless. The airport utility includes the drop down option of restarting but is not clickable so I can't choose it.
With my prior macbook and same time capsule, etc if i had problems connecting to the internet I would run network diagnostics to help out. This included clicking on the airport utility ---> base station --> restart. This worked most of the time.
Bottom line, is there something I am missing in not being able to restart the wi-fi remotely? ]
Thanks in advance

You are likely forgetting a step.
Open AirPort Utility
Click on the Time Capsule icon
Click Edit in the small window that appears
Now click the Base Station menu.....top of the screen....not the Base Station "tab" in the center of the screen
Click Restart

Need help connecting to an aws instance using a key from my macbook

i need to connect to an amazon instance using terminal and a keypair from a macbook pro. please help since its possible to connect to the aws instance easily using putty on windows 7 OS but failing to connect on my new macbook pro. step by step really appreciated.

You may need to open TCP and UDP port 3283 and TCP and UDP port 5900 in the routers on your end and your company's end. For encrypted file transfer (ARD 3.0), also open TCP port 22. You may also need to open TCP (and perhaps UDP) 5988 and 5989, though it's not clear under what circumstances this will be necessary.
If your systems at work get their IP addresses via NAT, you'll also have to forward those ports to your MBP's internal IP address.

Connecting to two database instances using the same Toplink

Hi,
We are trying to create a process using BPEL where data from one database instance needs to be passed to the other. The process is compiling properly and we could deploy it in BPEL Process Manager. But when we try to run the process, the data is not getting inserted into the second instance. There is no error /exception being thrown at most of the time, but at times we are getting a 'Unique constraint error' eventhough there is no duplication of data.
Can we connect to two different instances using the same toplink. How can we achieve this.
Thanks in advance
Pratheusha

You need to use two different sessions with two different mapping descriptors

I keep getting an error when trying to update an app- cannot connect to store. I logged out from my account and tried to log back in and got the same error. I am doing all this from my phone since I no longer own a personal computer (only work)

I keep getting an error when trying to update an app- cannot connect to store. I logged out from my account and tried to log back in and got the same error. I am doing all this from my phone since I no longer own a personal computer (only work) since I use iCloud and I tunes match

YAY!!! Saved it in my Mac's Firefox Bookmarks for easy future access!
Hope you are having a lovely afternoon today! I'm about ready to go bobo....I have an early meeting, and I don't want to oversleep! The nice part is that I work remotely, so I only have to wake up 15 minutes or so before the meeting.... I don't even use an alarm clock anymore (really, my iPhone alarm, which is much more pleasant), unless I have to get up at 6:30 or something....
TMI?
GB

Cannot connect to Analysis Services instance

Hi,
I'm new to analysis services and have been following through the tutorials here http://msdn.microsoft.com/en-us/library/ms170208(v=sql.100) for SQL Server 2008.
I've tried to deploy in visual studio 2008 and it gives an error saying it cannot connect. I've got sql server 2008 installed and I attached the 2008 Adventure Works database to my local default SQL instance. I can connect via management studio Ok. Also,
when creating the data source in visual studio I hit the "Test Connection" button which was also OK.
In management studio when I hit the connect drop down button in the Object Explorer, I get the option to connect to Analysis Services. When I do this it comes up with the server name "(local)" and uses Windows Authentication (I'm logged on to Windows as
Administrator). However, this fails with the following message "Cannot connect to (local). A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)"
I'm really stuck on this - has anybody got any ideas what might be going on?
Cheers

As Todd mentioned, check whether the SSAS Instance is running. Also check whether you have a default instance or named instance. In case of named instance you have to provide also the instance name, when connecting in the form (machineName\InstanceName)
or for local instance (locahost\InstanceName) or (.\instance name).
To determine instance name, launch SQL Server Cofinguration manager ans check SQL Server Services. The instance name is in the Parentheses listed.
If you have installed the instance and forgot to add yourselves as an administrator of the instance, and have UAC enabled, you have to Lanuch the SSMS as an administrator to rise the priviledges. Then connect to the instance and add your username explicitly
as administrator of the instance.

I cannot connect to I tunes store using I tune 11.1 I get the error 0x80092013 "secure link to I tunes store failed" does anyone know what this is?

I cannot connect to the I tunes store after recently downloading I tunes 11.1 I just get the error code 0x80092013 so not sure what to do. I have tried deleting and then reinstalling I tunes with no luck. I tried to flush my DNS but that did not work, I tried the diagnostics in I tunes and it told me my connections were fine but said the "secure link to I tunes store failed" Looking for an answer thanks!

Okay I was able to connect back to the I tunes store in I tunes 11.1 taking care of the error 0x80092013. I did this in XP going to the firewall controls, selecting the exception tab. I tunes was already in the exceptions tab but I deleted it anyway, then I added I tunes back using the Add Program button then browsing to the I tunes.exe location in the C drive then selected that as the program. I tunes showed back up in the exceptions once again. I then shut down the computer and restarted it and I then had a connection with I tunes. So the I tunes in the exceptions tab in the firewall was not working I just replaced it with a fresh one.

I cannot connect to iTunes due to a response from device

I have iphone 5s and HP61-110SA laptop using kasperksy security software. When trying to connect iphone to itune i get the error message that it cannot connect because of "invalid response from device". Can anyone help?
Aladrykes

Hi Why do you use your PC since, ios 7 almost everything be done over Wifi if you must use PC turn Security, off. And try again. Cheers Brian

"Configuration Manager cannot connect to the site" after site update from SP1 to R2

Our dev SCCM environment only has a single primary site with a remote SQL database. Initially, the dev primary site had SP1 Beta (5.00.7782.1000) installed but as everyone is aware there is no upgrade path available to SP1 or R2 from Beta; so, we uninstalled
the site and removed the database, re-installed SP1 non-Beta (5.00.7804.1000), then proceeded to update all devices with the latest client agent. Afterwards, we attempted to upgrade the site from SP1 non-Beta (5.00.7804.1000) to R2 (5.00.7958.1000).
All seemed well until we attempt to open the Configuration Manager console and we get the following error message:
Configuration Manager cannot connect to the site (Site Name)
The Configuration Manager Administrator console could not connect to the Configuration Manager site database. Verify the version of the console is compatible with the version of the site server you are connecting to and then try to connect again.
So we tried reinstalling the console directly from here...
"C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\AdminConsole.msi"
still the same error message persisted, so we tried installing it from here...
"C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\ConsoleSetup.exe"
still the same error message persisted, so then we tried installing it directly from the R2 (5.00.7958.1000) installation media, and afterwards the same error message persisted....
All along, we were checking the AdminConsole log from here:
"C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog\SmsAdminUI.log"
Here are the contents:
[4, PID:4836][04/22/2014 15:21:10] :Property: 'Features'\r\nSystem.Management.ManagementException\r\nNot found \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.PropertyData.RefreshPropertyInfo()
at System.Management.PropertyDataCollection.get_Item(String propertyName)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_Item(String name)\r\nManagementException details:
[4, PID:4836][04/22/2014 15:21:10] :ReadExtraProperties: Failed to initialize extra properties
[4, PID:4836][04/22/2014 15:21:11] :Transport error; failed to connect, message: 'The Configuration Manager Administrator console could not connect to the Configuration Manager site database. Verify the version of the console is compatible with the version
of the site server you are connecting to and then try to connect again.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.SmsConnectionWithDetailException\r\nThe Configuration Manager Administrator console could not connect to the Configuration Manager
site database. Verify the version of the console is compatible with the version of the site server you are connecting to and then try to connect again.\r\n at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.ValidateConnectionParameters(ConnectionManagerBase
connection)
at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nNo details are available for this error.\r\n
Once again, we validated we could connect to the SQL database from this box, and that the console was at the same version as the site. Any help or guidance with getting our access to the console restored after the SP1 to R2 upgrade would be greatly
appreciated.

From the Primary Site Server, I tried uninstalling the Admin Console and re-installing using:
consolesetup.exe /q TargetDir="%ProgramFiles%\Microsoft Configuration Manager" EnableSQM=0 DefaultSiteServerName=<SiteServerName>
Of course replacing <SiteServerName> with the FQDN of my Primary Site Server. Console installed successfully however the same error message persists.
Also tried installing the console on a clean Windows Server 2008 R2 installation. I tried it from the R2 (5.00.7958.1000) installation media, from the "C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\" both without any luck, the
same error message persists. I verified I could ping the FQDN of the site server also, and that the firewall between the two permits communication over the ports listed here: http://technet.microsoft.com/en-us/library/hh427328.aspx
Any help would be greatly appreciated.

Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?

i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

Not able to access database from a remote machine using SQL Server Management Studio

Hi,
I have a DB_BOX with SQL Server 2008 R2 installed. I can access the databases on the local machine using SQL Server Management Studio but it is not accessible from other machines, though the machines are in same domain.
I have remote enabled on SQL Server box, TCP enabled, firewall off. I checked with IP Address too, all SQL Server services are running.
The SQL Server log shows the message
The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.
I get the below message in SSMS from remote machine.
Details of error message are
===================================
Cannot connect to DB_BOX.
===================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476
Server Name: DB_BOX
Error Number: 64
Severity: 20
State: 0
Program Location:
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
   at System.Data.SqlClient.TdsParserStateObject.ReadByte()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Sorry, missed the message from the errorlog in the original post. You shouldn't have included that big .Net dump that hid the important facts. :-)
My first Google attempt on that message (which I have never seen before) suggests that the TCP Enpoint is stopped, so try this:
ALTER ENDPOINT [TSQL Default TCP]
STATE=STARTED;
Erland Sommarskog, SQL Server MVP, [email protected]
This solves the problem. Thanks...

Since upgrading to OSX 10.6.8, I am unable to use scp on a remote machine to copy files into my iMac.

Any suggestions?
However, I can use scp to copy files out from my iMac (10.6.8) .
I can ssh into the iMac OK.
I created a .profile in my iMac home directory with the single line "export TERM=xterm-color".
This makes a difference to how scp behaves when attempting to copy into the iMac, but it still fails.
Thanks in advance for any help. Peter R
Here is the scp debug output (on the remote machine that I'm copying a file from, to the iMac):
===
Executing: program /usr/bin/ssh host molika.ucsd.edu, user prowat, command scp -v -t Desktop/FromPelican/Outs201201.pdf
Sun_SSH_1.1.3, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to molika.ucsd.edu [137.110.243.133] port 22.
debug1: Connection established.
debug1: identity file /home/nona/.ssh/identity type -1
debug1: identity file /home/nona/.ssh/id_rsa type -1
debug1: identity file /home/nona/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version OpenSSH_5.2
debug1: match: OpenSSH_5.2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-Sun_SSH_1.1.3
debug1: use_engine is 'yes'
debug1: pkcs11 engine initialized, now setting it as default for RSA, DSA, and symmetric ciphers
debug1: pkcs11 engine initialization complete
debug1: Failed to acquire GSS-API credentials for any mechanisms (No credentials were supplied, or the credentials were unavailable or inaccessible
Unknown code 0
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: Peer sent proposed langtags, ctos:
debug1: Peer sent proposed langtags, stoc:
debug1: We proposed langtags, ctos: i-default
debug1: We proposed langtags, stoc: i-default
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: dh_gen_key: priv key bits set: 124/256
debug1: bits set: 1007/2048
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'molika.ucsd.edu' is known and matches the RSA host key.
debug1: Found key in /home/nona/.ssh/known_hosts:1
debug1: bits set: 1043/2048
debug1: ssh_rsa_verify: signature correct
debug1: newkeys: mode 1
debug1: set_newkeys: setting new keys for 'out' mode
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: newkeys: mode 0
debug1: set_newkeys: setting new keys for 'in' mode
debug1: SSH2_MSG_NEWKEYS received
debug1: done: ssh_kex2.
debug1: send SSH2_MSG_SERVICE_REQUEST
debug1: got SSH2_MSG_SERVICE_ACCEPT
debug1: Authentications that can continue: publickey,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/nona/.ssh/identity
debug1: Trying private key: /home/nona/.ssh/id_rsa
debug1: Trying private key: /home/nona/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
*** Password requested & supplied
debug1: Authentication succeeded (keyboard-interactive)
debug1: fd 5 setting O_NONBLOCK
debug1: fd 6 setting O_NONBLOCK
debug1: fd 7 setting O_NONBLOCK
debug1: channel 0: new [client-session]
debug1: send channel open 0
debug1: Entering interactive session.
debug1: ssh_session2_setup: id 0
debug1: channel request 0: env
debug1: Sending command: scp -v -t Desktop/FromPelican/Outs201201.pdf
debug1: channel request 0: exec
debug1: channel 0: open confirm rwindow 0 rmax 32768
~
debug1: channel 0: read<=0 rfd 5 len 0
debug1: channel 0: read failed
debug1: channel 0: close_read
debug1: channel 0: input open -> drain
debug1: channel 0: ibuf empty
debug1: channel 0: send eof
debug1: channel 0: input drain -> closed
debug1: channel 0: write failed
debug1: channel 0: close_write
debug1: channel 0: output open -> closed
debug1: channel 0: rcvd eof
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: channel 0: rcvd close
debug1: channel 0: almost dead
debug1: channel 0: gc: notify user
debug1: channel 0: gc: user detached
debug1: channel 0: send close
debug1: channel 0: is dead
debug1: channel 0: garbage collecting
debug1: channel_free: channel 0: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: fd 2 clearing O_NONBLOCK
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.9 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 0

On looking at the secure.log on the iMac with OSX10.6.8, I see these entries at each attempt to scp into the iMac:
Dec 29 11:06:20 molika sshd[7248]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Dec 29 11:06:26 molika sshd[7246]: Accepted keyboard-interactive/pam for prowat from 137.110.243.132 port 35571 ssh2
Dec 29 11:06:26 molika com.apple.SecurityServer[26]: Session 0x236a14 created
Dec 29 11:06:26 molika com.apple.SecurityServer[26]: Session 0x236a14 attributes 0x20
Dec 29 11:06:27 molika com.apple.SecurityServer[26]: Session 0x236a14 dead
Dec 29 11:06:27 molika com.apple.SecurityServer[26]: Killing auth hosts
Dec 29 11:06:27 molika com.apple.SecurityServer[26]: Session 0x236a14 destroyed
I don't know what to make of this.
Peter R

Way to allow students to connect to their infomation on the Xserve from a windows machine

My previous experience working with servers was a win2000 server. I have changed schools and they are running a 10.5.8 xserve to control the user accounts. I would like to know if there is a method to allow the students to use the Windows XP machines in our library, so if they log in to those machines they can access their accounts on the Xserve. We have an old Windows server, but the accounts have been limited since it is filled. The reason I ask, because our school is 1:1 in the HS, but in the Jr. High teachers can check out carts, and a lot of work gets done there, but if a student is in our Library and using one of the XP machines, they can't save back to their main profile. I did notice a Windows tab on the workgroup manager where it shows the profile and the path. Didn't know if this was where could be set up. Any help would be appreciated.

You will need to allow both GRE and TCP 1723, most probably TCP would work if you are already inspecting all TCP Traffic, however, for GRE you will need to creat a seperate class and ACL (permit gre destination>) and set action for that as pass in both driections (in out and out in) make sure that this class is the top most class in the policy map applied under each zone pair.
Here is an example you may find usefull:
http://www.cisco.com/en/US/products/ps5855/products_configuration_example09186a0080ab7073.shtml

Cannot connect to a named instance using SSMS from a remote machine

Similar Messages

Maybe you are looking for