Remote Connecting a PC to a Mac Server

The Mac Server we've purchased for our company has been working great. Our employees can easily access files by remote connecting from home using their Macs.
But we have employees that also use PCs from home and I have been unable to figure out how to get them connected remotely. I've searched the internet and have read the entire Mac OSX Server training book I bought without any luck.
I'd like the share points to show up as network drives, just as they do when connecting locally.
Please help!!
Thanks in advance for looking this over.

I've been struggling with this for weeks. My provider blocks port 139 which is reserved for SMB. VPN won't help because my PC users are outside the server local network...which uses port 139 that is blocked by my provider.
The way I see it, there are two ways for windows users to get access to a Mac OS X Server
1) move all your files to the folder that serves WebDAV (/Library/WebServer/Documents) and let your Windows users connect via WebDAV. This means all of your files have to be in this folder. I find this very cumbersome but probably necessary.
2) remap your port to provide SMB on another port besides 139. Apple Enterprise Support says this is pretty involved and they won't support it unless I go with a higher-priced service plan.
I'm trying to find a third solution such as using another protocol (NTP, AFP for Windows??) that will allow Windows users outside my local network to connect to my server.

Similar Messages

Remote Connection from SAP to MS-SQL server

Hello Experts,
We have been following 2 options so far and we have come across some issues
The first Option is to call a stored procedure (this is our preferred method) which does the data transfer for us
We have been able to test this scenario successfully from SQL Server side
However, while calling the stored proc via native SQL from ABAP we have come across an issue which is due to SQL 2005 changes (Schema implementation and difference in the security context)
While calling the stored procedure from the ABAP Code we have an error
The program short dumps with runtime error DBIF_DSQL2_SQL_ERROR, exception CX_SY_NATIVE_SQL_ERROR. The database error code is 15274, and the error text is
"Access to the remote server is denied because the current security context is not trusted."
This issue is new after the SQL Server 2005.
We are trying to resolve that.
Secondly we have been trying the DBCON option as well as per OSS Note 323151
We have a few things thatu2019s impacting our scenario:
The remote servers are in a different domain
The remote servers are located in DIZ
Remote server is a named instance
Remote server has been configured with a different port than standard (1565) u2013 All Connection strings will need port in there
The Database name starts with a numeric value
Due a combination of factors as mentioned above the standard approach does not work
Have any of you used this approach while connecting from SAP to MS-SQL server? Do you know of any successful methods to connect to SQL using ABAP (or not) from SAP.
Thanks in advance,

Yes,
DBConnect & UDConnect.
Works like a charm.
We write data into a MS-SQL database via DBConnect & an ABAP program (using open sql).

Remote Connection using Back to my Mac for Time Capsule?

How do I connect to my Time Capsule and connected usb drive/printer now that Back to my Mac for Mobile Me is disabled and iCloud is running Back to my Mac?
More information:
I used to use the Mobile Me's version of Back to my Mac to enable connecting with my time Capsule, but how is this done now that iCloud has taken over Back to my Mac and I have upgraded to Lion.
I have a Feb2011 MBP and a 2010 minimac the macmini is always connected to the time capsule, but I would like to be able to connect directly to the time capsule without having to go through the macmini.
Thank you for your help

It is possible but I am not sure it is worth the hassle..
Your key issue here is public IP for your network.. if you have a static ip you are fine.. but very few people have this. It also depends on how the TC is setup.. is it the main router for the network or plugged into a modem router which has the role of main router, even if you use the TC as a secondary router.
Without more info..
1. This is easy if you have a static public IP and the TC is the main router and gets the public IP on the wan port.. just go to disk sharing in the airport utility manual setup and check for wan (internet access).
2. If you have a dynamic IP, then you will have to sort out how you are going to find that IP.. the normal method to use dyndns account is not directly applicable because the TC has no client. It is possible to set up dyn dns but you will need to purchase your own domain name.
3. You may find it easier to use standard router and bridge the TC. A standard router can be setup to port forward 548 AFP files service to the TC ip address. You may or maynot be able to access the printer. Certainly would be easier if the printer has IPP services. And is a true network printer.
4. Use vpn.. get a vpn router so you can setup proper vpn endpoints.. then you use VPN service to access your local network.. this is far more secure and will work with dyndns just fine.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The
server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26- Error:Locating Server\instance Specified)
How Can i solve this?

1. Make sure SQL Server Service is running
2. If a named instance, make sure SQL Server browser service is running
3. Make sure SQL Server is configured to allow remote connections
4. Examine the SQL Server error log for messages confirming that SQL is listening on the expected network interfaces and ports
5. Test server connectivity with PING from the client machine
6. Test port connectivity using TELNET or PowerShell to the server and port (from step 4) from the client machine. For example
a. TELNET <server-name> 1433
b. PowerShell: 1433 | % { echo ((new-object Net.Sockets.TcpClient).Connect("YourServerName",$_)) "server listening on TCP port $_" }
7. Check firewall settings if step 5 or 6 connectivity test fails
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Oracle 11g Remote Connection issue

When I try to connect to Oracle database remotely using SQLPlus or SQLDeveloper I get the following error.
ORA-01017: INVALID USERNAME/PASSWORD; logon denied.
Server details:
Oracle 11g on Enterprise Linux 4
I can connect using SQLPlus on the server.
SHOW SQLCASE is MIXED
Client details:
Windows Server 2003 enterprise Edition
Oracle 11g Client.
From remote computer my TNSPING to that server works perfectly.
For the same connection string I can’t connect from client. I am sure I am not typing bad password.
Any thought on this will be helpful.
Thank you,
Smith

Did the following steps and still not able to connect.
1. Cross checked that the REMOTE_LOGIN_PASSWORDFILE is set to EXCLUSIVE.
2. Created the PASSWORD file at the server using the tool ORAPWD
3. Restarted the server and started the Oracle listener and database.
4. Connected to the database using PLSQL in server to make sure it works fine there.
5. Checking at the client box to connect to the database. It fails and I am looking for help again at forum.
Now it is connecting using remote connection(sqlplus and sqlDeveloper) to the server. Interestingly the password are not the same when I connect remotely and from the server.
I am sure it is connecting to the same database both the occasion. I shut down the server and try to connect or v$version results indicates that I connecting to the same database.
Any jestification on this? I am getting lost here.
Thank you,
Smith
Edited by: user517525 on Feb 16, 2010 1:44 PM
Edited by: user517525 on Feb 16, 2010 2:22 PM

Sharing DSL between Mac Server and PC client

Hello,
I'm running a small Mac server network of 3 Mac clients and 1 PC. They are all connected via ethernet to a switch. There is a DSL modem also connected to the switch. The modem software was installed on the Mac server.
The Mac clients can access the Mac server as well as access the DSL modem to get on-line. The PC is running XP Pro. I can either set up his LAN network connection to see the Mac server or manipulate the settings in that same LAN network connection to see the DSL modem and get on-line. I can't seem to do both.
On the Macs, I set up separate network configurations with the appropriate tcp/ip settings required for the 2 tasks in question.
It seems like there should be a way to set up another separate LAN connection on the problem PC, much like I did on the Macs, to allow both server and DSL access.
1. Does anyone know if this is possible?
2. Does anyone know of another way to get the pc to see the server and the dsl simultaneously, using the same ethernet connection?
Thank you in advance for any help.
Allan
p.s. The macs are running 10.39 and the server is running 10.1.2.

Hi Allan!
I suggest you replace your switch for a router. The purpose of a router is to connect two networks. In your case it would connect your local computer network (Macs, server and PC) to the Internet. Having your DSL on a switch with the rest of your machines means that only one at a time should be able to connect to the Internet.
Hope this helps! bill
1 GHz Powerbook G4 Mac OS X (10.4.8)

Remote Connectivity Analyzer opens port 443 successfully but fails.."Net. conn. not available"

Trying to set up a client with external access. I just got their Edge off the domain and in the DMZ, and supposedly the appropriate firewall ports are opened. They have a RP running IIS ARR.
Microsoft Remote Connectivity Analyzer (testconnectivity.Microsoft.com) does the following for three tests:
1. When I do Lync Server Remote Connectivity Test and choose Autodiscover, it is able to open port 443 and it validates the cert. But it says "Operation failed because the network connection was not available".
2. When I do the same Lync Server Remote Connectivity Test and manually enter the Access Edge service FQDN and choose port 5061, it is able to resolve the name in DNS but it then fails testing TCP port 5061 with "The specified port is either blocked,
not listening, or not producing the expected response".
3. When I do the Lync Autodiscover Web Service Remote Connectivity Test, it fails when trying to open port 443 on the Lyncdiscover URL.
So, that seems to indicate to me that port 443 might be open on the Edge but not the Reverse Proxy, since that's where the autodiscover URL points. And it seems 5061 is not open but 443 is on the Edge. What else could I check on the Edge to get
443 working?
Thanks for the help and sorry for any vague information. Any help is appreciated!
Brandon

Okay, I can now telnet to lyncdiscover.mydomain.dom on port 443 successfully, and I can telnet to sip.mydomain.com on 5061 successfully.
Now when I do the remote connectivity test:
Using Autodiscover to detect server settings, I get "Operation failed because the network connection was not available". It opens port 443 fine it looks like.
Manually choosing lync.mydomain.com as the FQDN and port 5061, I get "The endpoint was unable to register. See the ErrorCode for specific reason". Response code is 504 and response message is Server Time-out
Doing the Lync Autodiscover Web Service Remote Connectivity Test I get "HTTP 403 error was received because ISA server denied the specified URL".
Looks to me like a rule might not be set right on the firewall if ISA is denying the connection, right?(they are using TMG on a server running Server 2008 as the firewall). I can't ping the reverse proxy from the firewall (but I can ping the Edge).
What else can I check?
Thanks for all the help so far, I really appreciate it.
Brandon

Remote Connecting to a PC from my Mac

Hi, I am wondering how I can essentially "screen share" with my friend using a pc. By this I mean they share their screen. I've been looking on the internet for answers and I have found multiple hits for connecting from PC to Mac but not the other way around. In addition, from what I have read, nothing was vert step-by-step. I heard about TightVNC so I told my friend to download it and that I would be able to remote connect to them using what I have in Leopard. However, it's at this point that I am completely clueless on how to actually establish that connection.
I would like to know what the PC user needs to do and secondly what I would need to know/type in in order to connect to their pc and control their screen.
Thanks

When it says "computer:________" Connect. I put in the PC's ip address (I'm pretty sure it's the right one, I will ask again if not).
Do they have a home router between their ISP connection and their PC? If so, their router needs to forward port 3389 from the Internet to their PC. And the IP address you need is the IP address assigned to the router by the ISP. They could access a web site such as <http://whatismyip.com> to find out their public IP address.
1. Who's user name and Password? The PC User's or My account name and my password? If theirs, they don't have a name or password, they turn on the computer and the desktop is there, without having to log in. Do they need to have one (an account or w/e).
The PC's Username and Password. And yes they do have a username and password. They may not remember what they setup, since they have it set to auto login. I do NOT know how to find out this information, as I am a Mac and/or Unix kind of guy
2. Domain. This is optional is it not? Can the IP go in here?
This is the Windows account domain, and nothing to do with IP addresses nor DNS. Mostly they have WORKGROUP or MSHOME as their domain. If it is optional, then ignore it.
Here are some alternative approaches. Sign-up for a free LogMeIn.com account <http://logmein.com>. Have them install the LogMeIn.com server and associate it with the LogMeIn.com account you created. Now you can use your web browser (Safari) to login to the LogMeIn.com account, and from there connect to their PC's LogMeIn.com server.
The current version of Skype allows screen sharing, however, I think it is a view ONLY connection. That is to say, you can watch their screen, but you can not control their keyboard, nor their mouse. <http://skype.com>
Another choice might be a purchased copy of GoToMyPC (there are both Mac and PC versions).
There is also TimBukTu from <http://www.netopia.com> which is also cross platform.
VNC has also been mentioned. Again, VNC needs router port forwarding, only VNC needs port 5900 forwarded. TightVNC, UltraVNC, RealVNC are possible Window's VNC servers. JollysFastVNC (highly recommended), Chicken of the VNC, or Mac OS X built-in Screen Sharing (Finder -> Go -> Connect to Server -> vnc://ip.addr.of.pc). I only recommend the built-in Mac OS X Screen Shring if the other system is on the same high speed network, or if connecting to another Mac OS X system.

Need to Remote Connect to Mac at the Office... HELP!

Alright, I've seen topics similar to this one on the Leopard thread but I really, REALLY, need someone to help me. I know about Apple Remote Desktop but I don't have $300. I have downloaded Vine Viewer/ Vine Server VNC and Chicken of the VNC. When I'm at the office and connected to the office network I have no problems being connected and controlling my other Mac. The default port for forwarding is 5900 but is being used by another coworker, so I tried to configure port 6900. I'm not sure what I'm doing wrong so if someone could help me step by step that would be awesome. Thanks.

Please check out this thread. You don't need Vine server on the work machine. Set up the office computer like how I told Bruce to set up his Quicksilver. Your home computer is like his iBook. You won't need to deal with forwarding ssh port 22 on your home router, your work IT guy will have to ensure that that port will allow inbound traffic to pass to your work computer. Also, this will give you remote keyboard/screen, but you won't be able to drag&drop files across locations. To get that, tunnel afp as I discussed in a later post in that thread. Then you'll have both encrypted drag & drop and encrypted remote keyboard/screen.

Remote connection, mac to mac

I have had a look and can't seem to find anything convincing - we have a few macs at work, and we each have a mac at home - all we want to be able connect from home, to our mac at work and do work....
does the official apple remote software cover this, as it seems more networking focused
or has anyone any other experiences with software they would like to share?
many thanks in advance

The key will be how work interfaces to the internet.
If you have a corporate firewall, and no control over that firewall, then it gets complicated.
If you have a small office and router similar to a home router, then you can configure that router to allow specific ports from the internet to be be routed to specific Macs at work.
But before going down that path, here are the easy to the more complex ways to connect to your Macs at work.
If your work router allows it, you could use Apple MobileMe subscriptions and its Back-to-My-Mac feature. This depends on the router supporting Universal Plug and Play features, but if it does, then Back-to-My-Mac will give screen sharing, and file sharing between home and your Macs.
LogMeIn.com and TeamViewer.com can generally work, even across corportate firewalls. They both provide screen sharing. TeamViewer.com includes file copy, and LogMeIn.com (paid version) also includes file transfer. There is also GoToMyPC.com.
If you can configure your work router to Port Forward internet ports to specific ports on your work Macs, then you can roll your own. This would consist of forwarding a unique internet port for each work Mac to each Mac's port 5900 (the VNC port), and a separate set of unique internet ports to each Mac's port 548 (the AFP file sharing port). For examle:
Internet port 5911 to Mac 1's 5900
Interent port 5912 to Mac 2's 5900
Internet port 5913 to Mac 3's 5900
Internet port 11548 to Mac 1's 548
Internet port 12548 to Mac 2's 548
Internet port 13548 to Mac 3's 548
Of course Screen Sharing and File Sharing would need to be enabled on the work Mac's.
Now when you want screen share with work Mac 1, at home you would use Finder -> Go -> Connect to Server -> vnc://work.router.address:5911
And when you wanted to do file sharing with work Mac 2, at home you would use Finder -> Go -> Connect to Server -> afp://work.router.address:12548
If your work.router.address does not have its own domain name, then you can get a free No-IP.com or DynDNS.org dynamic DNS name, which will allow you to have a fixed name you connect to, and one of the Macs at work run the dynamic DNS updater that keeps the name up to date when your work ISP changing the IP address.
The next level of complexity, is to have a VPN into work. If work already has a VPN that you can use, this would actually simplify things a little, as the VPN software already gets you into the work network, and you can just ignore my router configuration suggestions. Then you just use the Finder -> Go -> Connect to Server -> vnc://address.of.mac.inside.VPN and afp://address.of.mac.inside.VPN
If you do not have a VPN, then setting one up is beyond my knowledge, and I'm sure a bit more complex. It might also requires some dedicated hardware or Mac to do the VPN server duties.
Another more complex approach which gives the security of a VPN, with a different set of complexities would be using ssh tunnels. This is alternative to opening separate ports for VNC and AFP. Instead you would open unique ports for ssh (System Preferences -> Sharing -> Remote Login).
Internet port 21022 to Mac 1's port 22
Internet port 22022 to Mac 2's port 22
Interent port 23022 to Mac 3's port 22
Now from a terminal, or an ssh GUI interface, establish tunnels for screen sharing and file sharing. The following would be the terminal command issued from the Home Mac.:
ssh -p 23022
-L 5913:localhost:5900
-L 13548:localhost:548
username@ work.router.address
Now from the home Mac use Finder -> Go -> Connect to Server -> vnc://localhost:5913 and afp://localhost:13548

Remote control a Mac server from Windows machines

I'm running a Mavericks Server that I'd like to get off my desk and put in the data center. However, my primary laptop is a Windows 8.1 laptop that I use to support other things. I'd still like the ability to remote into the Mac Server from my Windows laptop. I know that I can VNC into the server, but it's my understanding that if I have Remote Management turned on, I can't have Screen Sharing (and thus, VNC) turned on. So it seems like my options are to run another VNC server on a different port or use LogMeIn Ignition. But I'm not sure what other people are using so I'd like your help. Thoughts? Suggestions?
TIA

As you have found via the answer provided by Morgan R, it is possible to configure Remote Management to allow standard VNC clients to connect just like it is possible with Screen Sharing.
Note: Remote Management does everything Screen Sharing does plug other things. So anything you can do via Screen Sharing you can do via Remote Management.
However there is a client available for Windows that does support the extended login information used by Remote Management/Screen Sharing, this is 'Remotix' by Nulana.
See http://www.nulana.com/remotix-windows/
I have tried it and it does work. I did however find one serious bug which I have reported to them but I don't know if they have fixed it yet.
Over the years I have found many in fact nearly all software that involves linking Mac and Windows where one controls the other in either direction has suffered an inexcusable bug whereby if you are not using US keyboards at both ends then several keys will not be mapped properly and you can even end up with some keys not usable at all. The most infamous combination is the @ and " keys being swapped.
All these programs appear to have been written by Americans who are members of the 'flat earth' society and obviously believe that if you leave the shores of the USA you will fall of the edge of the world. I presume they also are avid fans of the Discworld series of books.
Offenders include Virtual PC, Microsoft Remote Desktop Client 1.0 (for Mac), Timbkutu Pro, Remotix and I am sure many others.
Note: Microsoft did at least fix theirs several years later with Remote Desktop Client 2.0 (for Mac).
The one noteable exception is VNC. VNC was originally developed at AT&T Laboratories in Cambridge, England. (Not New England.)
See http://www.cl.cam.ac.uk/research/dtg/attarchive/vnc/ I am sure if it had been developed in Cambridge, Massachusetts it would have suffered the same problem. Since Screen Sharing on Macs is based on VNC it has never suffered this problem even when controlling a PC via VNC. I am therefore even more shocked that Nulana managed to make this mistake.
To our dear American friends in the colonies, you might want to read http://uk.ask.com/question/who-discovered-that-the-earth-was-round

Connecting Remotely from a PC to a Mac

Can you tell me how to connect remotely from my home PC to my office's Mac server? I need to do it using the internet.

We need a lot more information to support you here.
What are you looking at accesing? What technology are you hoping to use?
Also since this is from MAC it may be limited support in these forums.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
Blog: http://www.windows-support.co.uk
Twitter: LinkedIn:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (p

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that
the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)(Microsoft SQL Server, Error: 2)
The system cannot find the file specified
Cannot connect to COWBOYS.
Here are the technical details===================================
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=2&LinkId=20476
Error Number: 2
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer
timeout)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance,
SqlConnectionString userConnectionOptions, SessionData reconnectSessionData)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
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()
===================================
The system cannot find the file specified
I have tried from so many forms. This is so frustrating. Thank for everyone/anyone who wants to help. So this is what happened: I had to uninstall my previous sqlserver 2012(which worked great) for some reason, and I uninstalled everything from that download.
Then I installed the trial edition of sql server 2012 (64 Bit) and It wouldn't connect to the database. (Error mentioned above.) My local DB is COWBOYS. (COWBOYS is also my computer name.) After this, I have tried downloading sqlexpress and sqlserver 64bit
many times and cannot connect to my local DB.
How do I connect to my Local DB?
Also, I think this might help: (When I run sqlserve.exe, which I was able to find in C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn, I get an error: Your SQL server installation is either corrupt or has been tampered with(Error getting
instance ID from name). Please uninstall then re-run setup to correct this problem.
I would happily re install it, if it wasn't my 20th time.
I don't have any remote connections, I don't use username/password, only window authentication. I work mostly on visual studio, but without able to store /retrieve data, I don't know how to survive.
May be the solution is very simple, but I am too frustrated.
Some of the things I have tried:
From a command prompt, enter one of the following commands:
net start "SQL Server Agent (MSSQLSERVER)" OR
net start "SQL Server Agent(instancename)"(for instance)
on my sql configuration, I cannot start anything because there is nothing there to start. I can post more details, if that would help. Also, some more details about the error:
Details
Product:
SQL Server
ID:
2
Source:
MSSQLServer
Version:
10.0
Component:
SQLEngine
Message:
An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error:
40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Explanation
SQL Server did not respond to the client request because the server is probably not started.
User Action
Make sure that the server is started.
Version:
9.0
Component:
SQLEngine
Message:
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: Named Pipes Provider, error:
40 - Could not open a connection to SQL Server) (.Net SqlClient Data Provider)
Explanation
SQL Server did not respond to the client request because the server is probably not started.
User Action
Make sure that the server is started.
Any one that can help me, I will be greatful. Thank you so much. p.s. please ask me anything if you have any questions.

It sounds like there are a couple things going on here. First check if you have a successful install of SQL Server, then we'll figure out the connection issues.
Can you launch SQL Server Configuration Manager and check for SQL Server (MSSQLSERVER) if default instance or SQL Server (other name) if you've configured your instance as a named instance. Once you find this, make sure the service is started.
If not started, try to start it and see if it throws an error. If you get an error, post the error message your hitting. If the service starts, you can then launch SSMS and try to connect. If you have a default instance, you can use the machine
name in the connection dialog. Ex: "COWBOYS" where Cowboys is the machine name. However, if you named the SQL Server instance during install, you'll need to connect using the machine\instance format. Ex: COWBOYS\Romo (where Romo
is the instance name you set during install).
You can also look at the summary.txt file in the SQL Server setup error logs to see what happened on the most recent install. Past install history is archived in the log folder if you need to dig those up to help troubleshoot, but the most
recent one may help get to the bottom of it if there is an issue with setup detecting a prior instance that needs to be repaired.
Thanks,
Sam Lester (MSFT)
http://blogs.msdn.com/b/samlester
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and
"Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

How to Configure Remote Connections To SQL Server 2008 R2 Express

Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name 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)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!

My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
            // netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo

Can I connect Windows 7 to a mac network account server

Hi All,
I have a Mac Mini Server allong with a pile of Macs and a few PCs. What I want is being able to login to an ACCOUNT from ANY of my macs OR PCs. So when the computer turns on it asks you to put in a username and password. I know this is possible if all computers are running the same opperating system but i am not sure how to do it with different opperating systems.
Thanks,

I was struggling with this for a few days as well! Finally got it working though ! YAY !
Here are the steps:
1. Add this to your registry:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\PolicyAgent]
"AssumeUDPEncapsulationContextOnSendRule"=dword:00000002
2. Open secpol.msc (click start > search for secpol.msc)
- Local Policies > Security Options
- Network Security : LAN Manager Auth Level…
- Set to: Send LM & NTLMv2 - UseNTLMv2…
And
- Network Security : Minimum session security… clients
- uncheck "Require 128-bit encryption"
3. Restart PC
4. Create VPN Connection on Windows 7
- Host Name: (server IP or yourhost.name.com)
- PPP Settings : Enable LCP (only)
- Type: L2TP/IPSec
- Pre-shared key : yoursharedsecret
- Data encryption : Optional encryption
- Allow CHAO and CHAPv2
5. Router on server-side must allow VPN Passthrough and forward ports: 50, 51, 500, 548, 1701, 1723, 4500 to the server box. Also, do not filter anonymous internet requests, multicast or NAT Redirection but enable SPI Firewall.
...now you should be good to go

Remote Connecting a PC to a Mac Server

Similar Messages

Maybe you are looking for