The network browsing or service announcement part of Samba is also handled by the nmbd daemon. Within NBNS, there is a master server that holds the IP address and NetBIOS name of each client or server on the network and will serve these upon request. The other name resolution element of the nmbd daemon revolves around the NetBIOS Name Service (NBNS) or Windows Internet Name Service (WINS). In broadcast mode, an nmbd client will send out a request to all machines on the network, for example, asking who is running a particular service. Nmbd undertakes name resolution on a point-to-point basis or broadcast basis, using the NetBIOS protocol. Smbd handles file and printer sharing, including user access (authentication and authorization). The two daemons included with Samba are smbd and nmbd. The odds of your application having a similar bug are pretty small, but if it crashes whenever someone logs into the server as console mode then this might be the problem.
If someone remoted in as console mode, then the application crashed. There was a bug in the application that required it be run in the console session. One application that I administered would crash if anyone logged into the server in console mode. There is a small degree of risk associated with using console mode when remoting to a server. This isn’t the case when a session is opened in nonconsole mode. The advantage of opening a session in console mode is that any applications that are currently running on the server will be visible to the console-mode session. This is also referred to as “session 0.” You can connect to this session by adding the parameter / console when making the connection from RDC. A session, called the console session, always exists on the server. When using RDC to connect to a remote Windows server, you are effectively creating a new session and logging into it. Bourne, in Application Administrators Handbook, 2014 11.8.1.1 Console mode
0 kommentar(er)
