Discussion Locked

Server naming conventions

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are in the process of implementing 10 new servers (a mix of NT and 2000). In the past, all of our servers have had a "-" (dash) in their name. In recent weeks I have been warned that certain applications do not function properly with hyphenationsin the Server name.

Does anyone know of ANY issues with that type of naming convention??

9 replies

by estebandelatorre

Use name as short and simple as you can.

Less Key strokes
Easy to read (specially in very long path)
Easy to write
Allows old apps to works, some of them can't work with long paths
3 letters will be enought like gns, gnc, gnf
where thelast letter means the main service of the server: e.g: GNF Firewall, GNM
Mail, GNP PrintsERVER, GNH HOME directories, GNW Web Server...
Easy to make an Local admin acc: Eg: ADGNS Local Admin Account For Server GNS, password PSWADGNS57 PaSsWord ADministrator of server GNS, 57 Is a good issue adding some (constants) numbers to a password.
Sharings: SHGNS01 SHare on server GNS number 01 Make it easy to identify where the share is localted. You can put a very long purpose on the share description.

by cviehweg

Are you sure the person who informed you was referring to the dash and not the underbar? We previously had underbars in our server names and changed them due to the (then) most recent internet naming conventions which were obsoleting the underbar.We have been using the dash after our network conversion with no problems.

by wood_jared

I have heard of some issue with apps running on servers with a "-" in the naming convention on a novell network, but I hve not personally experienced any problems with them. I am partial, though, to naming conventions beginning with a location and ending with a purpose: i.e laDHCP, nyDATA, sfEXCHG. I wouldn't use a dash if you thought there was a remote possibility of being a problem. It is going to be a pain to have to change all those names and login scripts.

by schitzoid

ocjared says dashes cause problems with older Novell clients, and I know underscores can cause trouble with older Microsoft clients, but if everyone is using Win95 or newer you shouldn't have any problems. I've personally used both naming conventions without problems, but I wasn't running any 16 bit clients. When naming your NT machine during setup, it warns you if you use an underscore (_) but not a hyphen(-).

This discussion is closed to new replies.