This may be simple to solve, but I'm clueless...
I have SQL Server 2012 on my laptop with Windows 8 and Virtualbox with Windows Server 2008 and SQL Server 2012, and I want to test Transactional Replication by using the host machine as the publisher/distributor and the VM as the subscriber. Thing is, I can't seem to connect the host to the guest -- I can't access the guest database from inside the host database, but I do seem to be able to connect the guest to the host. SQL Configuration Manager seems right, I tried using the VM with both NAT and bridge, and I have internet connection on the VM.
If I type the IP address of the VM on the host's SQL Server and the sa user (actually, any user), I get the message saying 'sa' login failed. I can't connect with the guest's domain name.
Also, when I start the jobs at the host, a message appears on the log saying that there are no replications available or something.
I was following this tutorial: http://technet.microsoft.com/en-us/library/aa337437.aspx
Related
Well, I'm having the following situation.
I'm trying to set up a testing environment which consist of having a SQL Server on a Windows Server VM hosted on Google Cloud Platform (GCP). So far I've installed SQL Server on the VM and configured an instance with SQL authentication. Then I installed SMSS to access using the instance name and my credentials. At this point everything works well.
The problem comes when I try to access my SQL Server via SMSS from another computer. As the instance I'm using my GCP VM IP Adress and the credentials I've created before. The error is as follows:
So far I've done the following configurations:
Enable TCP/IP via SQL Server configuration manager.
I made sure that port 1433 was properly configured in the TCP/IP properties.
Created a new inbound rule on the Firewall to allow TCP connections using port 1433.
On the SMSS, checked that allow remote connections is enabled.
Restarted SQL Services from SQL Server configuration manager and services.msc
With above configurations it should work! But I've no idea what's happening.
Anyone who could give me a hint of how this could be solved, I'd appreciate it.
Hi we're building out some test clusters in Azure, using Developer edition of SQL Server 2016. However with no firewalls between the two nodes, both nodes in same subnet, all tcp/ip settings enabled and sa permissions on both servers we're unable to connect using SSMS (management studio), what I'm trying to understand is are there any limitations with creating AlwaysOn Availabiity groups using SQL Developer 2016? Getting the following error
Mcrosoft SQL Server, Error 5 "Access is Denied"
However I can log onto the instances on both machines locally using ssms, but not across the network.
Think it might be a limitation on the sql server edition?
Thanks and sorry if this seems a bit random :)
In order to connect to SQL server on VM from a local machine. you have to not only open 1433 port for the VM on the portal, but also do you need to set up the firewall inside of the VM machine. Make sure you have the inbound 1433 port opened as below:
I have a Red HAT system on oracle virtual box that I've been trying to set a mssql server up.
-Also tried doing everything on SUSE vm but I've been probably doing the same thing wrong on that one aswell.-
I have the server up but was unable to connect the mssql server in linux from windows terminal or SSMS.
Get this as a terminal response on windows
ODBC Driver 13 for SQL Server does not support connections to SQL Server
2000 or earlier versions.
and below one on SSMS
Not associated with a trusted server connection
Not sure if I have some network configuration info wrong on vbox myb?
Might be using the wrong ip addr trying to connect aswell.
I use localhost to connect on virtual box.
Tried to connect by localhost ip, public ip and
sudo ip addr show eth0 | grep "inet"
command as well.
Any idea what could be the issue since I am quite sure both the sql server versions are up to date.
Solved upon changing network attached to on virtual box settings to bridged adapter with promiscuous mode on.
In case anyone gets stuck on this
I am not able to connect to a SQL Server 2005 hosted on a Win7 virtual machine. I am new to VM, can someone help me locate the problem?
I am able to connect another SQL server which is installed on the local machine.
When you say you can't connect - that can mean a lot of things - really you need to be much more specific.
In addition to the comments and answers already here - If you're having trouble connecting to it in Sql Server Management Studio - you should open Configuration Manager on the VM itself and make sure that Shared Memory and Named Pipes are enabled (open the SQL Server Network Configuration node in the tree).
For example, SQL Server Express instances are configured by default to reject the kind of remote connection that SSMS wants to open by default.
first of all check your connection string (for reference):
http://www.connectionstrings.com/
Second you need to add an exception in the guest machine firewall or completely disable it (port 1433 is for sql tcp/ip access).
this works fine for me:
SQLConn.ConnectionString = "Network Library=DBMSSOCN; Data Source=xxx.xxx.xxx.xxx,1433;
Initial Catalog=mySQLServerDBName; User ID=myUsername;Password=myPassword"
good luck
I have VS 2008 and SQL Server 2005 Developer edition installed on my desktop. I have a instance of XP running in Virtual PC and want to connect to the dev instance. I am logged on as a domain user on both the desktop and the Virtual instance of XP. When I try to connect I get a message saying "Server does not exist or access denied". What do I need to do to connect. I am using trusted connection and the userid has privileges on the DB.
Paul
Make sure that the VPC is not using NAT for its network connection.
Also check your configuration to be sure remote connections are allowed. Remote connection is turned off by default.
Have you tried pinging your desktop from the virtual instance? I had the same problem and figured out that the firewall was preventing any kind of communication between both machines.
I found out that you have to go into the SQL Server Surface Area Configuration tool and set "Remote Connections" to "Local and remote connections". Apparently the default is "Local connections only".
I encountered the same thing, sort of - MS Server 2003 and SQLServer 2008 Ent running on VMWare, and get the "Server does not exist or access denied" when trying to connect from host machine (on Vista x64).
SO, do you reckon changing to "Local and remote connections" via the SQL Server Surface Area Configuration tool will do the trick?
For me despite configuring the SQL server for Remote Connections also, I could not access the sql server from Win XP VM.
So when I disabled the windows firewall from host machine, it worked fine!!