Accounting Software For Windows 11

1 view

Skip to first unread message

Chiquita Mcnicholas

unread,

Aug 3, 2024, 5:56:45 PM8/3/24

to remamocons

In my NPS I've setup a Radius Server Group and set : send accounting messages to , port 1813. I've changed the Connection Policy to forward accounting messages to my Radius Server Group (Sophos XG). But my Sophos XG does not receive any accounting messages. I've installed wireshark on the server which is Running NPS. There is no traffic on port 1813 udp.

But if i enable "Match known users" in my firewall rule. The Wireless Clients can't connect to the internet and i don't want them to use the captive portal because - in theory - they are already authenticated via Radius / WPA2 Enterprise.

FYI : I've successfully used both Meraki and Ruckus AP's in conjunction with the XG Radius accounting feature. As mentioned the only requirement that I'm aware of is the framed address information is sent in the accounting packet - I don't think something like a Unfi AP will provide that information so it's not a given.

Check transaction statuses, view notifications, and start timers for projects right from the status bar without interruptions to your accounting work. Additionally, the status bar also allows you to view and switch between different organizations you have created under your Zoho Books account.

I switched from QuickBooks to Zoho Books because it's incredibly user-friendly. Zoho Books has simplified our financial processes, especially with features like inventory management integrated with CRM. The platform is well-crafted and efficient, perfect for our small company. Plus, their customer service is fantastic. I trust Zoho Books.

Creating quotes, acquiring signatures, processing payments, and reporting revenue and taxes has gone from slow and arduous tasks to effortless tasks! Zoho Books does everything its counterparts do but is more customizable. Their customer service team goes above and beyond and is almost always available, all at a fraction of the cost compared to its competitors.

Internet Authentication Service (IAS) was renamed Network Policy Server (NPS) starting with Windows Server 2008. The content of this topic applies to both IAS and NPS. Throughout the text, NPS is used to refer to all versions of the service, including the versions originally referred to as IAS.

NPS fully supports the Remote Authentication Dial-In User Service (RADIUS) protocol. The RADIUS protocol is the de facto standard for remote user authentication and it is documented in RFC 2865 and RFC 2866.

The following diagram shows an authenticating client ("User") connecting to a Network Access Server (NAS) over a dial-up connection, using the Point-to-Point Protocol (PPP). In order to authenticate the User, the NAS contacts a remote server running NPS. The NAS and the NPS server communicate using the RADIUS protocol.

A NAS operates as a client of a server or servers that support the RADIUS protocol. Servers that support the RADIUS protocol are generally referred to as the RADIUS servers. The RADIUS client, that is, the NAS, passes information about the User to designated RADIUS servers, and then acts on the response that the servers return. The request sent by the NAS to the RADIUS server in order to authenticate the User is generally called an "authentication request."

If a RADIUS server authenticates the User successfully, the RADIUS server returns configuration information to the NAS so that it can provide network service to the user. This configuration information is composed of "authorizations" and contains, among others, the type of service NAS may provide to the User (for example, PPP, or telnet).

While the RADIUS server is processing the authentication request, it can perform authorization functions such as verifying the user's telephone number and checking whether the user already has a session in progress. The RADIUS server can determine whether the user already has a session in progress by contacting a state server.

The RADIUS server also collects a variety of information sent by the NAS that can be used for accounting and for reporting on network activity. The RADIUS client sends information to designated RADIUS servers when the User logs on and logs off. The RADIUS client may send additional usage information on a periodic basis while the session is in progress. The requests sent by the client to the server to record logon/logoff and usage information are generally called "accounting requests."

A RADIUS server can act as a proxy client to other RADIUS servers. In these cases, the RADIUS server contacted by the NAS passes the authentication or accounting request to another RADIUS server that actually performs the authentication or the accounting task.

Logging user authentication and accounting requests to a local file. Used primarily for connection analysis and billing purposes. Also useful as a security investigation tool because it provides you with a method of tracking the activity of a malicious user after an attack. You can configure local file logging using the Accounting Configuration wizard.

Logging user authentication and accounting requests to a Microsoft SQL Server XML-compliant database. Used to allow multiple servers running NPS to have one data source. Also provides the advantages of using a relational database. You can configure SQL Server logging by using the Accounting Configuration wizard.

In addition to these settings, both SQL Server logging and text logging allow you to specify whether NPS continues to process connection requests if logging fails. You can specify this in the Logging failure action section in local file logging properties, in SQL server logging properties, and while you are running the Accounting Configuration Wizard.

You can configure Network Policy Server (NPS) to perform Remote Authentication Dial-In User Service (RADIUS) accounting for user authentication requests, Access-Accept messages, Access-Reject messages, accounting requests and responses, and periodic status updates. You can use this procedure to configure the log files in which you want to store the accounting data.

To prevent the log files from filling the hard drive, it is strongly recommended that you keep them on a partition that is separate from the system partition. The following provides more information about configuring accounting for NPS:

To send the log file data for collection by another process, you can configure NPS to write to a named pipe. To use named pipes, set the log file folder to \.\pipe or \ComputerName\pipe. The named pipe server program creates a named pipe called \.\pipe\iaslog.log to accept the data. In the Local file properties dialog box, in Create a new log file, select Never (unlimited file size) when you use named pipes.

Switching log file formats does not cause a new log to be created. If you change log file formats, the file that is active at the time of the change will contain a mixture of the two formats (records at the start of the log will have the previous format, and records at the end of the log will have the new format).

NPS formats accounting data as an XML document that it sends to the report_event stored procedure in the SQL Server database that you designate in NPS. For SQL Server logging to function properly, you must have a stored procedure named report_event in the SQL Server database that can receive and parse the XML documents from NPS.

Some RADIUS proxy servers and network access servers periodically send authentication and accounting requests (known as ping requests) to verify that the NPS is present on the network. These ping requests include fictional user names. When NPS processes these requests, the event and accounting logs become filled with access reject records, making it more difficult to keep track of valid records.

When you configure a registry entry for ping user-name, NPS matches the registry entry value against the user name value in ping requests by other servers. A ping user-name registry entry specifies the fictional user name (or a user name pattern, with variables, that matches the fictional user name) sent by RADIUS proxy servers and network access servers. When NPS receives ping requests that match the ping user-name registry entry value, NPS rejects the authentication requests without processing the request. NPS does not record transactions involving the fictional user name in any log files, which makes the event log easier to interpret.

Only Prompt for Color, Only Prompt for Fax, or Only Prompt for Color or Fax: Select one of these options to prompt users to log in to the service. The options are available only if the printer is configured to provide the services.

If you are using an auxiliary accounting device such as a badge reader or coin box, for Auxiliary Accounting Interface, select Enabled. The Accounting window appears each time a user submits a job.

Only Prompt for Color, Only Prompt for Fax, or Only Prompt for Color or Fax: Select one of the options to prompt the user to log in to the service. The options are available only if the printer is configured to provide the services.

If you are using an auxiliary accounting device such as a badge reader or coin box, for Auxiliary Accounting Interface, select Enabled. The Accounting window appears each time a user submits a job.

If you want to specify the default User ID and Account ID, select Use Default Accounting Codes, type them in the Default User ID and Default Account ID fields, then select the default account type.

We have configured our Cisco devices to use Windows 2008 NPS for radius. However, we are unable to configure aaa accounting for priv 15 commands to use the same radius servers for logging privileged mode commands. During configuration using the following command: