I bought dedicated server by Windows Server 2008 R2. In options, I check "additional IP". I can create two users on my server. How I can connect to them (RDP) at the same time? (using both IP-s?)
//sorry for bad english..
Hard to answer that concisely as you haven't said what is and isn't working currently, but I'll try to cover the obvious possibilities. I'm assuming that you're talking about remote admin.
By default Windows Server 2008 R2 (and other versions) doesn't allow RDP connections, you first have to enable it and grant the relevant users permissions to connect. Select Start then right click on Computer and click Properties. In the System window, click Remote settings on the left hand side of the window. In the Remote tab, ensure that one of the two Allow connections... options has been selected, then click Select Users and add the two users you've created.
By default I believe RDP on the server is configured to listen on all connections on the server, but you can check that by running tsconfig.msc, then in the Connections section right click on RDP-Tcp and select Properties. Go into the Network Adaptor tab and check what is selected, by default this should be "All network adaptors configured with this protocol".
The fact that you've configured the server with two IP addresses (I'm assuming on the same NIC from your description) shouldn't make a difference, the two users should be able to connect via RDP using either using one or both of them.
Related
I have 2 linked SQL servers, Both are SQL Server 2012 Express Edition.
I was executing insert statement into a table of connected SQL Server and it was working perfect until now. I have changed nothing. but now it gives me the following error message.
MSDTC on server 'MSERVER1-PC\SQLEXPRESS' is unavailable.
I have "Distributed Transaction Coordinator" service enabled. have tried restarting it and tried all options but all in vein.
In Component Services under Distributed Transaction Coordinator, In Local DTC, I have enabled Network DTC Access. Allow Inbound and Allow Outbound are checked. Network DTC Access is checked.
Have tried almost everything but all in vein.
Any idea...
To enable MSDTC on the business management server that is running on Windows Server 2008 click Start, Run, type dcomcnfg and then click OK to open Component Services.
In the console tree, click to expand Component Services, click to expand
Computers, click to expand My Computer, and click to expand Distributed Transaction Coordinator.
Right click Local DTC, and click Properties to display the Local DTC Properties dialog box.
Switch to the Security tab.
In the Security Settings section, click Network DTC Access.
In the Client and Administration section, select Allow Remote Clients and Allow Remote Administration.
In the Transaction Manager Communication section, select Allow Inbound and Allow Outbound.
In the Transaction Manager Communication section, select Mutual Authentication Required (if all remote machines are running Windows Server 2003 SP1 or Windows XP SP2 or higher), select Incoming Caller Authentication Required (if running MSDTC in a cluster), or select No Authentication Required if some of the remote machines are pre-Windows Server 2003 SP1 or pre-Windows XP SP2. No Authentication Required is the recommended selection.
Select Enable XA Transactions, and then click OK.
Repeat steps 1 through 9 on the other Web servers.
Use DTCPing.exe to validate the connection between the Web server and the computer that is running SQL Server or an SQL cluster depending on your configuration. To obtain the DTCPing.exe tool, see http://go.microsoft.com/fwlink/?LinkId=72166.
For more information about how to troubleshoot
I also tried all the above settings to no avail. But the good old engineering principle works for me "If something is broken try restarting the machine".
In my case the problem was not MSDTC server either. I had to disable "Enable Promotion of Distributed Transaction" option under Linked Server properties -> Server Options.
I have a website that access a sql database in localhost and it works, but when published in an Azure website, can't reach the database. I've changed the connection string with visual studio on line pointing to a new database created in Azure, but can't reach the database.
There is a way to track the error? because the application only returns to the same webpage (this is the caondition when the connection to the database fails.
Any suggestion?
Check that the Azure firewall has a rule for the IP address of the machine hosting the website. You can do that by either of two methods:
Navigating to your Azure Portal using a browser that is on the same machine that is trying to access your database.
Go to the 'SQL Databases' section and click on the database.
In the 'Design your SQL database' section, click on 'Set up Windows Azure firewall rules for this IP address'.
If the machine already has a rule the portal will indicate that. Otherwise a new rule will be added.
The other way:
From the Management Portal, click SQL Databases. All databases and their corresponding servers are listed here.
Click Servers at the top of the page.
Click the arrow beside the server for which you want to manage firewall rules.
Click Configure at the top of the page.
To add the current computer, click Add to the Allowed IP Addresses.
To add additional IP addresses, type in the Rule Name, Start IP Address, and End IP Address.
To modify an existing rule, click any of the fields in the rule and modify.
Click Save at the bottom of the page to save the changes.
How to: Configure Firewall Settings (Azure SQL Database)
In the attached image below, I show my SQL Server as seen from SSMS on my PC (left) compared to the same as seen from the server (right) ... could someone advise why the view from my PC does not show the status indicator (running/stopped) for the server and for the SQL Server Agent items?
Also, when you right-click on either of the options, the selection for START|STOP|RESTART are all greyed out....?
For these screenshots, I am connected from my PC with a user account that should have maximum access; under the security settings for this account EVERYTHING is checked.
Access to a remote Service Control Manager (SCM) is subject to OS privileges. W/o SCM privileges you cannot know what services are running, nor can you start or stop any. The required privileges are listed at Access Rights for the Service Control Manager.
None of the above is in any way at all related to SQL Server security. Services are controlled by SCM, not SQL Server.
I have an issue with a SQL Server Express install. I have a test server set up called ASPDEMO running server03, IIS6, SSEE08R2. MgmtStudio installed.
When I access the web site from a computer on the LAN all is well, I can login to the site and hit the db with no problem.
If I try to set up an ODBC connection to ASPDEMO I can connect and link to tables from Access for example, no problem.
But I can't do both at the same time.
Any ideas?
In Management Studio, connect to the database and right-click on the instance. Choose Properties. When the Server Properties window pops up, Click Connections in the list on the left and check the maximum number of connections allowed. Maybe it is set to 1.
I am currently trying to run SQL Server Management Studio 2008 as a user who is on a different domain. I noticed in other threads that running the following command from a batch script will do this however it doesn't seem to work for me.
runas /netonly /user:DOMAIN\USER "C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\Ssms.exe"
I am asked for my password, the Login screen appears however the Windows Authentication username and password are still incorrectly the currently logged in impersonated user on the local Domain. Attempting to connect to the database on the other domain is unsuccessful regardless.
This seems to work for most people, the kicker for me is that this domain exists over a VPN connection. I am not able to view the VPN domain network computers in My Network Places, and thus I cannot Add Users in Control Panel.
My OS is Vista Business unfortunately, I cannot help this.
Any ideas would be appreciated.
Try this:
NET USE \\DBSERVER /USER:DOMAIN\USERNAME
You will be prompted for your password. This establishes a NetBIOS session with the database server. You should be able to see the shared folders and shared printers on the database server once you have done that.
If that works you should be able to connect using SSMS as yourself. You may have to specify "named pipes" as the network protocol to usem, if it doesn't work with TCP (but I think it will).
Menu->File->Connect Object Explorer...
Options->Connection Properties->Network protocol
Specify "Named pipes"
Named Pipes inherits your existing NetBIOS session, so provided you can list the shares you are probably good to go.
Update: It looks like in some configurations this does not work with TCP connections, (possibly due to some security update). In these cases you should enable Named Pipes, and set named pipes in your connection string.