Ias Log Viewer Android Systems It

At import, it supports LOG and CSV files, while at export you can use extensions such as DBF, XML and CSV.

For example, it is possible to list the records from the uploaded LOG file, along with details such as date, time and username, as well as connects along with information including start and stop date and time, duration, user IP, input octets and connect request.

Filed under View windows log Interpret log file Windows log analyzer Windows log Interpreter IAS service Viewer.

Softpedia and the Softpedia logo are registered trademarks of SoftNews NET SRL Contact.

This is fairly easy to accomplish if youre dealing with domain joined machines.

Thus far after following the official tutorials from the vendor.

Ias Log Viewer Android Systems It

On the android systems it says Incorrect password, so after some troubleshooting and diagnostics on the fortigate firewall i have the following debug file attached - Android Debug.

On windows all i get is the following error: Not sure where to turn from here hoping this community can provide some light on the issue, Thanks in advance regards, Friendly IT Guy.

The clients are either the APs or the Fortigate itself depending on what is sending the traffic (I believe in your scenario its the Fortigate itself that does the RADIUS communication on behalf of the APs).

A way to find out for sure is run this Fortigate debug command instead which shows more useful info for this particular issue.

It means itll show you source interface, IP port and destination interface, IP port Trigger a wireless client to connect and observe which IP is talking to your RADIUS server.

Then check to make sure you have a RADIUS client in NPS defined with that IP address.

Windows server by default does not configure its own built-in firewall to actually allow the RADIUS traffic.

Thats often an indication you need to create an Inbound rule to pass RADIUS: allow both TCP and UDP port 1812.

The rest is then based on Policies in NPS how you allow the clients to connects - ie by specifying domain credentials, only allowing domain joined machines and no need for user passwords, etc.

I cleaned it up a bit in Notepad and if I did the breaks correctly it seems the Fortigate isnt at fault here at fault here.

RADIUS traffic is leaving your mgmt interfaceVLAN and a reply is received.

Make sure Windows NPS has a RADIUS client with IP 192.168.91.58 defined so itll allow it to talk to it.

Is it correct that you have two subnets on the same interfaceVLAN With the right routes in place thats not an issue obviously.

I do believe that part is all fine because your first debug log did show a Radius Reject message which came from the NPS server itself.

From the VLAN that the Fortigate lives you should be able to ping and have port 1812 and 1813 open as well as DNS 53, etc.

Yeah the right routes are in place on the fortigate on intermediary firewalls, not sure what you mean by a discrepancy between the subnets can you explain that a little.

I added 53 no luck.

For troubleshooting i opened up the connection to all ports between 91.58 (Fortigate) and 3.244(Radius).

Still no luck. Any other ideas that may be hampering the authentication Also i can ping both ways so im ruling out routing issue as well as trace routes are accurate.

After looking at the logs (using NPS log monitor) i do notice something coming up now see the attachment: The last field says: The client could not be authenticated because the EAP type cannot be processed by the server.

I am going to venture a guess here and think its certificate related.

You need a certificate authority to issue the NPS server certificates that the clients also need to trust.