- CHANGE IP ADDRESS NOVELL NETWARE 6.5 SERVER INSTALL
- CHANGE IP ADDRESS NOVELL NETWARE 6.5 SERVER WINDOWS
There again, DNS can solve your woes, if you register the name of the server (Say it is SQLSERV1) with the default DNS name (say ) tacked onto the end of it, so that the IP Name resolves to the IP Number you want it to point at. If you want to connect to the MS SQL server box to put a file on it, then that is somewhat unrelated to the SQL aspect of the issue. If they need to use the IP address of the SQL server to connect to it via a SQL client, then you have a DNS problem. (There you go! Now a search will show at least ONE reference to Banyan Vines!! Every good technology site needs at least one, and probably not more than one!)Īs others have noted, what are you trying to do?
But, it would register the machine in Netware's Well if you are using SQL Authentication, then you are using a SQL Client of some kind to connect to it, and the fact you have Novell in the picture is as unrelated as if you had Banyan Vines.
CHANGE IP ADDRESS NOVELL NETWARE 6.5 SERVER INSTALL
You could install the netware client on the SQL machine but that would make most DBA's cringe. Simply add the microsoft sql server's network name to your local DNS services and it won't appear like it's a second class citizen. If your Netware network is running just fine, then I wouldn't change it. But, this would conflict with your directory services (if used) on your netware server.
CHANGE IP ADDRESS NOVELL NETWARE 6.5 SERVER WINDOWS
If you want your Microsoft SQL Server to be a integral part of your network, then you need Microsoft Active Directory installed with integrated windows authentication and DNS services running on a Domain Controller. Netware has it's own form of directory services that is independant of Microsoft. (I imagine you are using SQL Authentication instead of AD based.) If you have to connect via IP rather than name, then your Windows boxes aren't participating in an Active Directory authentication + DNS setup like is the case in most "windows" networks verus the "netware" network that you are running into. It sounds like your Windows SQL Server is in fact a second class citizen on your networks.
0 kommentar(er)
