We decided to change our physical Domino Server with a new one. In order to prevent current server from being un-accessible while we configure the new one, we plan to up the new Domino server which has the same domino server name with the existing one, only the IP will be different.
For example:
Existing domino server
Name : Notes Server/_Org
IP : 10.8.8.50
New domino server
Name : Notes Server/_Org
IP : 10.8.8.51
When the new server is up and run smoothly, we will shut down the current server and change the new server IP address to 10.8.8.50
Is it possible ?
And if its possible , is it a good practice or there is a better way to do this ?
Thanks a lot
Related
I installed SQL Server 2012 on Windows server 2012, I can connect to the server only if I write . in the server name field.
But I can't connect using the server name MSSQLSERVER.
I am trying to connect using SQL Server Management Studio from the same machine.
I checked that TCP/IP is enabled, IP2 is enabled, port 1433 is configured for all IPs, added an inbound rule for port 1433.
Also tried restarting both the SQL Server service and SQL Server browser service multiple times, but no luck.
Any ideas on what could be causing this problem?
Wow, this is an old post. Still I'm going try to answer this just in case someone else is wondering.
The Short Answer
MSSQLSERVER is typically not used as the name of a Server hosting the SQL Server Object (often referred to as SQL Server). Since you are using SSMS, you need simply define the name of the SQL Host--the actual NetBIOS name, or FQDN, or IP address of the host.
If no instance was created during installation
Server Name: ServerHostName
If an instance was created during installation
Server Name: ServerHostName\InstanceName
or IP address
Server Name: ###.###.###.###\InstanceName
If a port was defined other than the default port of 1433
Server Name: ServerHostName,####\InstanceName
The Long Answer
First a question. Is the MSSQLSERVER the actual NetBIOS name of your server? When talking about a SQL Server, it can be a little confusing at times as the name SQL Server is used to describe the host as well as the SQL Server Object (which is what most people are referring to in this context).
When using a tool like SSMS to connect to the SQL Server, you are first connecting to the host server, and once connected, you will connect to the SQL Object itself. The "." is not an object, or is not a valid SQL server name, unless you named your SQL server ".".
Regarding the instance, this is usually defined during the installation of the SQL Server (the object). Post installation, if you forget or simply do not know the name of the instance, the fastest way to determine what the instance name of your SQL server object is, is by checking system Services.
services.msc
Take a look at the SQL Services that are running. If you created a SQL instance during the installation of the SQL server object, then the instance name will be in (): i.e. (SQLInstance). On the same token, if you create multiple instances on the same server, then you will see multiple service names like,
Default Instance
SQL Server
With Instances
SQL Server (SQLInstance1)
SQL Server (SQLInstance2)
That should answer an issue where you can connect to one instance, but not another if one instance is running but the other is not.
If you did not create a SQL instance during installation, then the default SQL instance will always be MSSQLSERVER, and you will not need to define this in the Server Name spot of the SSMS.
I hope this helps.
It's a typical problem.
Just use cliconfg.exe to create alias with tcp/ip protocol.
If unsure do the same alias for 32 and 64 bit.
The 64 bit version is found in:
C:\Windows\System32
The 32 bit version is in:
C:\Windows\SysWOW64
In General tab enable TCP/IP.
In Alias, create a new alias, insert the name you prefer (with named istance) and select TCP/IP as network libraries.
As server name put the ip and 1433 as port. Don't leave "dynamicaly determine port" selected.
Source for cliconfg locations: http://sqlblog.com/blogs/tibor_karaszi/archive/2009/09/08/sql-client-config-32-and-64-bit.aspx
Try to enable the SQL Browser service.
The port number in SQL named instance is dynamic
SQL Brower uses UDP port 1434 to send the correct TCP port to the client.
If your SQL server instance is a default instance, you can login with the following as the Server name:
. (period)
LAPTOP-JDRDGF9T (the name of your PC)
localhost
127.0.0.1
If it on the other hand is a named instance, you login with localhost\<INSTANCE_NAME>, instance name normally being SQLEXPRESS.
You can Go to SQL Server Configuration manager >> SQL Server Network Configuration >> Protocol for MSSQLSERVER
OR
SQL Native Client configuration >> Client Protocols
In the right pane split page you will have to enable and disable the followings:
>> Shared Memory Enable this
>> Named Pipes Enable this
>> TCP/IP Enable this
>> VIA Disable this
Also, Check whether you have checked the Mixed mode authentication or not.
I want to install an additional Domino as I did several times before. This one now resides on an external V-host. The "first" server I specified is in my internal network but can be reached from outside via :1352. But the remote setup tool says that it is unreachable.
Q1: are there other ports I have to open for remote setup to access my internal server?
Q2: can I setup the server w/o the first server by only providing the system databases via filecopy? Which dbs are needed and how can I tell the remote setup tool to use them instead of trying to connect to the first server via TCPIP?
Edit:
To be clear: I can run the remote setup tool and connect to the new server but it fails when the new one wants to pull stuff from the first server.
Remote server setup uses port 8585. Try opening that port and restart remote server setup.
Solution in the thread above works.
Open port 8585 (Per Henrik Lausten contribution)
Add the Fully Qualified Internet Host Name from the server document to the hosts file (Umeli contribution)
Run server configuration with new settings
I have a project to inventory an SQL Server. Part of this project includes discovering every IP that makes a connection to this SQL Server. It is an internal SQL Server with several other programs running on other servers that access this SQL server. Because this server's IP address is going to be changed, all of those other programs will have to updated with the new address. Plus the boss just wants a diagram of everything running on this server and everything connecting to it.
My initial inclination would be to setup logon triggers to capture the client IP address and port and write it to table. I am unfamiliar with logon triggers and have read that they present dangers to the server.
What is the best way that I can discover who all is connecting to and using this server?
Running the stored procedure sp_who will tell you about the machines connected to a SQL server instance.
I want to connect my db on SQL Server 2008 over local area network I want to put it on one computer on the LAN so any computer on the network can access it what should I do please give me correct steps
In a Client-Server scenario, you will have the SQL Server installed on your server machine.
Clients will be the computers accessing that SQL Server using a client software (can be SQL Server Management Studio, web/forms application, Excel worksheet, etc).
Each of the client will provide you a way of making a connection to the SQL Server Instance running on the server. From server you will need IP Address or Servername along with SQL Server Instance name. They both combined form host name.
Data Source = ServerName\InstanceName
Note: Instance name not required for default instance.
User name: You need to add user from domain or a sql server authenticated user under security tab (SSMS) on the SQL Server.
Password: Corresponding password.
Note: Once you add a user to SQL Server Instance, do not forget to attach the user to databases you want the user to access and provide appropriate role(s).
Install SQL Server 2008 on one machine on your LAN (let's call it SQLServer)
Connect that machine to the LAN (network cable)
You're done.
Now, all other computers can connect to that SQL Server machine by its name in the connection string - in .NET, that would look like:
server=SQLServer;database=YourDatabase;User ID=YourUser;Pwd=top$Secret
I am having a hell of a time trying to connect to the SQL SERVER 2005 database. I am using Windows 7.
Here is the screenshot of the error thrown:
(source: highoncoding.com)
I have been battling this issue for the past week and still no progress.
I have tried the following in the server name:
(local)
localhost
computername
none of them worked!
I just checked in the services section and SQLSERVER EXPRESS is not even there. I am using the following post as a reference:
https://serverfault.com/questions/11745/i-cannot-connect-to-my-local-sql-server-2008
This instance of SQL Server is running on the same PC you're connecting from? That's the implication of 'local'.
Possibilities :
1) Try (local) instead of local for the server name
2) Try 'MSSQLSERVER' as the name
3) Check the SQL Server Configuration Manager shows the same configuration options you're attempting to connect with, eg the same instance name, Named Pipes enabled, services running ok, etc.
EDIT :
Ok, what are you using to connect with? SQL Server Management Studio Express? Are you sure you installed an instance? The lack of SQLExpress in the services list would seem to indicate otherwise.
When you connect to a SQL Server you specify the name in the form {computername}\{instancename}. The {instancename} is the name of the SQL instance which was chosen during the SQL Server installation. For {computername} you can substitute the special names . or local when connecting to the localhost machine. If the SQL Server was installed as the Default instance then the instance name part must be omitted, so the connection Server name becomes just the computer name.
SQL Server Express installs by default an instance named SQLEXPRESS. The corresponding NT service name is MSSQL$SQLEXPRESS. The Server name in the connection dialog is .\SQLEXPRESS, local\SQLEXPRESS, localhost\SQLEXPRESS or {computername}\SQLEXPRESS (they're all the same).
If the SQL Server was installed as the Default instance name then the corresponding NT service name is MSSQLSERVER. The Server name in the connection dialog is ., local, localhost or {computername} (they're all the same).
If the SQL Server was installed as a named instance then the corresponding NT service name is MSSQL${INSTANCENAME}. The Server name in the connection dialog is .\{INSTANCENAME}, local\{INSTANCENAME}, localhost\{INSTANCENAME} or {computername}\{INSTANCENAME} (they're all the same).
When connecting from a remote computer to a SQL Server instance the SQL has to be configured to allow remote connection How to configure SQL Server 2005 to allow remote connections.
Check your SQL server configuration, make sure the TCP connections are enabled. You can also check that the SQL Browser service is started. Make sure you do not have a firewall that gets on the way. Make sure the SQL Server service is also started.
Did you install SQL Server on the default instance, or have you used named instances? If you've used named instances then the server will be server\instancename. If you don't know, then have a look in the Services administrative tool; you'll be able to determine the instance name, if any, from there).
You could also try connecting with the server name as a single period (i.e. simply ".") [caveat... I've not got access to SQL Server at the moment, but I think I've used this before now].