WINDOWS SERVER NAME TOO LONG

Servers have several NetBIOS dependencies that may require you to use NetBIOS name resolution across different subnets for the successful operation of all Server components, depending on the network topology. The NetBIOS naming convention allows for 16 characters in a NetBIOS name. Microsoft, however, limits NetBIOS names to 15 characters and uses the 16th character as a NetBIOS suffix. Because Server components have NetBIOS dependencies, and because NetBIOS names cannot exceed 15 characters, server names exceeding 15 characters are not supported and may play havoc / unstable operational environments. Refrain from using Server names greater than 15 characters in length. Even though it will be accepted and appear ok, unexpected issues may arise. You may correct some of these issues by renaming the server with a character count less than 15 at any stage, but this will inevitably lead to other problems / issues. These may arise if dependancies have been created in other areas. This usually occurs later after a server has been in use for some time. However these can be addressed easily, ie. renaming connection details, directories, shared drives, mapped drives etc.

  • 0 משתמשים שמצאו מאמר זה מועיל
?האם התשובה שקיבלתם הייתה מועילה

Related Articles

Safe Mode / Acess Safe Mode

Getting into Windows Safe Mode Question Getting into Windows Safe Mode. Reason If you cannot...

SERVER NAME TOO LONG , EXCHANGE SERVER

Server name too long This topic has not yet been rated - Rate this topic [This topic is...