Обновлено 16.08.2017
Добрый день уважаемые читатели и гости блога, продолжаем наше с вами изучение сетевых технологий на базе операционной системы Windows Server 2012 R2, сегодня я хочу пополнить нашу с вами копилку знаний относительно всевозможных ошибок подключения к VPN серверу, и сегодня вы узнаете причины появления ошибки 691 и код события 13 в журнале NPS. Давайте смотреть как все это дело решается и диагностируется.
Что означает ошибка 691
И так есть пользователи у которых установлена на клиентской машине операционная система Windows 8.1 или 10, в момент подключения к VPN серверу у пользователя появляется вот такое сообщение:
Ошибка 691: В удаленном подключении отказано, так как не удалось распознать указанную комбинацию имени пользователя и пароля или выбранный протокол проверки подлинности не разрешен на сервере удаленного доступа
Причины ошибки
Давайте рассмотрим основные причины появления данной проблемы:
- Если мы говорим про подключение к интернет провайдеру, чтобы через это подключение, то убедитесь, что у вас нет за должности по счету
- Правильность вводимых данных
- Не правильные настройки в VPN соединении
- Блокировка со стороны антивирусного продукта или на вашем фаэрволе (роутере)
- Ошибки на стороне сервера
Давайте разберем теперь все поподробнее по каждой из причин.
Как исправить ошибку 691
- И так если подключение идет к провайдеру, то вам нужно проверить баланс, вариантов несколько, либо какой то личный кабинет (например посмотреть с мобильного), либо позвонить в техническую поддержку и уточнить
- Если блокировок нет по вашему лицевому счету, то самая распространенная ошибка это не правильные учетные данные или же выбран не тот метод подключения, тут расскажу поподробнее.
Если вы создавали vpn подключение давно, то это не значит, что вам не нужно проверять этот пункт, по одной лишь причине, что настройки на стороне сервера могли поменяться, и то что вы могли пропустить эту новость, ваша проблема. Зайдите на официальный сайт или позвоните в техническую поддержку и уточните все данные:
- Адрес сервера
- Протокол подключения
- Метод аутентификации
- Порты
Затем зайдите в свойства своего сетевого подключения, для этого нажмите Win+r и в окне выполнить напишите ncpa.cpl
В итоге у вас откроется окно «Панель управленияВсе элементы панели управленияЦентр управления сетями и общим доступом» тут вы и сможете обнаружить все ваши vpn подключения. Переходим в пункт «Изменение параметров адаптера»
В итоге тут вам необходимо найти свое VPN подключение.
Убедитесь, что вы используете правильный протокол соединения, из-за него мы уже ловили ошибку 806. Заходим в свойства подключения, через правый клик и переходим на вкладку «Общие» и проверяем правильность адреса сервера.
Очень часто я видел сбой подключения с ошибкой 691 в windows 7 именно из-за неправильного типа протокола на вкладке «Безопасность» и удостоверьтесь в правильности метода проверки подлинности.
Приводим все настройки в надлежащий вид, и в соответствии с требованиями у провайдера или поставщика сервиса. Сохраняем и пробуем подключиться.
- Теперь рассмотрим ошибки со стороны самого VPN сервера. У меня был именно этот случай. Опишу схему. Есть виртуальная машина с microtik и она работает в качестве шлюза и VPN сервера, который для проверки подлинности обращается к radius серверу у которого есть база Active Directory, по которой он видит, кто к нему пришел. И как раз в этой связке были проблемы, на сервере я видел вот такую ошибку;
RADIUS-сообщение было получено от недопустимого клиентского IP-адреса 10.152.1.100 RADIUS-клиента. С кодом события 13
По сути сервер NPS откидывал пользователя при попытке к нему подключиться и выдавал ему ошибку 691. Причин тут несколько и почти все они на стороне микротика были. Что на нем нужно проверить:
- Общий секретный ключ
- Протокол подключения
- Порты
На стороне сервера NPS и настроек у radius проверьте, что произведена регистрация NPS в Active Directory, если нет то сделайте это.
У вас выскочит окно с подтверждением вашей операции.
Так же на сервере политики сети убедитесь, что в свойствах radius подключения вы можете проверить dns имя или Ip адрес, сервера VPN
У вас не должно быть, что при проверке выдастся сообщение «Этот хост неизвестен» именно из-за этого у вас появляется ошибка «RADIUS-сообщение было получено от недопустимого клиентского IP-адреса»
- И еще удостоверьтесь, чтобы у вас не блокировались порты ,как со стороны сервера, так и со стороны клиента, примером может быть роутеры, которые режут GRE пакеты или антивирус касперского, если у вас установлен NPS, то его порты можно посмотреть в свойствах сервера. У меня это 1812, 1645 это порты проверки подлинности, 1813, 1646 это порты для учетных данных.
Надеюсь эта небольшая заметка поможет вам решить ошибку подключения 691.
Aruba Cluster generating Error 13 in NPS
This thread has been viewed 12 times
-
1.
Aruba Cluster generating Error 13 in NPSPosted Jun 08, 2022 03:44 AM
One of my Aruba wireless clusters has just (in the last 24 hours) started generating thousands of Error 13 entries in the System Log of my RADIUS server.
A RADIUS message was received from the invalid RADIUS client IP address x.x.x.x
Where x.x.x.x is the virtual IP address of the wireless cluster controller.
I have checked the RADIUS secret, etc. and this is all correct. My other two Aruba wireless clusters are set up in exactly the same way and are not generating this error.
Anyone got any ideas? -
2.
RE: Aruba Cluster generating Error 13 in NPSPosted Jun 09, 2022 04:40 AM
This is an NPS error that relates to how NPS perceives the incoming radius request.
It appears it is no longer accepting that client from IP x.x.x.x as a valid radius client. How have you configured the VC in radius clients on this NPS server? If you have specified a hostname instead of the VC virtual IP address, could you change this to the IP address as is seen in the request (x.x.x.x) and see if this resolves the issue. If a hostname is used, check the DNS entry correlating to this device to check it is resolving to the correct IP address from the NPS server.
The assumption here is that RADIUS proxy is configured on this cluster so all requests for authentication come from this VC IP.
-
3.
RE: Aruba Cluster generating Error 13 in NPSPosted Jun 09, 2022 04:57 AM
Further to this there is a Microsoft help document related to NPS Error Event ID 13 that may be helpful:
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/dd316135(v=ws.10)?redirectedfrom=MSDNChange the configuration of the RADIUS client
This condition can occur under the following circumstances:
- In the NPS Microsoft Management Console (MMC), a RADIUS client is configured by fully qualified domain name (FQDN) or NetBIOS name rather than by IP address, and NPS has not received a DNS server response to the name resolution query. Without the IP address provided by the name resolution query, NPS cannot contact the RADIUS client.
- NPS is receiving communication from a RADIUS client that is not configured in the NPS MMC.
- In the NPS MMC, a RADIUS client is configured by either IPv4 or IPv6 address, but the format of the IP address is incorrect.
-
4.
RE: Aruba Cluster generating Error 13 in NPSPosted Jun 09, 2022 05:58 AM
Thanks, but we have got it setup with the IP address and _not_ the FQDN.
-
5.
RE: Aruba Cluster generating Error 13 in NPSPosted Jun 09, 2022 07:47 AM
In your authentication server settings within the VC have you enabled ‘Status-Server Authentication’, or a better description would be authentication server status requests? I wouldn’t have thought this would generate event ID 13 but possibly something else.
Try turning this off and seeing if it goes away.
-
6.
RE: Aruba Cluster generating Error 13 in NPSPosted Jun 09, 2022 07:54 AM
Already turned off, so not that either I’m afraid.
Hi all,
I keep getting error messages from System log as:
«A RADIUS message was received from the invalid RADIUS client IP address X.X.X.100» where XXX.100 is my local host’s IP address. It generates this type of message every 15-30s.
I have set RADIUS server as well as NPS server on the same server 2012. (x.x.x.200). The RADIUS client is set with the Access Point (x.x.x.250).
Wireless authentication is still working but users get disconnected several times a day and they reconnect again.
Anyone knows how to stop the error messages ?
P.s. I tried everything from fixing DHCP, DNS, reconfigure NPS but still getting the same message. This is very annoying, indeed.
Step 1 – Solve Nps Error Codes
Is Nps Error Codes appearing? Would you like to safely and quickly eliminate nps reason code which additionally can lead to a blue screen of death?
When you manually edit your Windows Registry trying to take away the invalid nps error 4402 keys you’re taking a authentic chance. Unless you’ve got been adequately trained and experienced you’re in danger of disabling your computer system from working at all. You could bring about irreversible injury to your whole operating system. As very little as just 1 misplaced comma can preserve your Pc from even booting every one of the way by!
Troubleshooting nps error 13 Windows XP, Vista, 7, 8 & 10
Simply because this chance is so higher, we hugely suggest that you make use of a trusted registry cleaner plan like CCleaner (Microsoft Gold Partner Licensed). This system will scan and then fix any Nps Error Codes complications.
Registry cleaners automate the entire procedure of finding invalid registry entries and missing file references (including the Codes error) likewise as any broken hyperlinks inside of your registry.
Issue with nps error 22
Backups are made immediately prior to each and every scan providing you with the choice of undoing any changes with just one click. This protects you against doable damaging your pc. Another advantage to these registry cleaners is that repaired registry errors will strengthen the speed and performance of one’s procedure drastically.
- https://technet.microsoft.com/en-us/library/dd197521(v=ws.10).aspx
- https://documentation.meraki.com/MR/Encryption_and_Authentication/Common_Wireless_RADIUS_Configuration_Issues
- https://technet.microsoft.com/en-us/library/dd197582(v=ws.10).aspx
- https://technet.microsoft.com/en-us/library/dd197570(v=ws.10).aspx
Cautionary Note: Yet again, for those who are not an state-of-the-art consumer it’s very encouraged that you simply refrain from editing your Windows Registry manually. If you make even the smallest error within the Registry Editor it can result in you some serious issues that may even call for a brand new set up of Windows. Not all difficulties attributable to incorrect Registry Editor use are solvable.
Fixed: nps code south africa
Symptoms of Nps Error Codes
“Nps Error Codes” appears and crashes the energetic method window.
Your Personal computer routinely crashes with Nps Error Codes when running the exact same system.
“Nps Error Codes” is shown.
Windows operates sluggishly and responds little by little to mouse or keyboard input.
Your computer periodically “freezes” for the number of seconds in a time.
Will cause of Nps Error Codes
Corrupt obtain or incomplete set up of Windows Operating System software program.
Corruption in Windows registry from a new Windows Operating System-related application adjust (install or uninstall).
Virus or malware infection which has corrupted Windows method documents or Windows Operating System-related application data files.
Another method maliciously or mistakenly deleted Windows Operating System-related files.
Mistakes this sort of as “Nps Error Codes” can be brought about by several different elements, so it really is important that you troubleshoot every of the achievable brings about to forestall it from recurring.
Simply click the beginning button.
Variety “command” inside the lookup box… Will not hit ENTER nonetheless!
Although keeping CTRL-Shift in your keyboard, hit ENTER.
You’re going to be prompted that has a authorization dialog box.
Click on Of course.
A black box will open having a blinking cursor.
Variety “regedit” and hit ENTER.
Within the Registry Editor, choose the nps error 4402 connected key (eg. Windows Operating System) you wish to back again up.
Within the File menu, choose Export.
Inside the Preserve In list, pick out the folder in which you wish to save the Windows Operating System backup key.
Inside the File Title box, sort a reputation for the backup file, these types of as “Windows Operating System Backup”.
From the Export Vary box, ensure that “Selected branch” is selected.
Click on Help you save.
The file is then saved by using a .reg file extension.
You now use a backup within your nps error 13 related registry entry.
Solution to your nps code bank problem
There are actually some manual registry editing measures that can not be talked about in this article due to the high chance involved for your laptop or computer method. If you want to understand more then check out the links below.
Additional Measures:
One. Conduct a Thorough Malware Scan
There’s a probability the Error Nps Codes error is relevant to some variety of walware infection. These infections are malicious and ready to corrupt or damage and possibly even delete your ActiveX Control Error files. Also, it’s attainable that your Nps Error Codes is actually connected to some element of that malicious plan itself.
2. Clean nps packet type Disk Cleanup
The a lot more you employ your computer the extra it accumulates junk files. This comes from surfing, downloading packages, and any sort of usual computer system use. When you don’t clean the junk out occasionally and keep your program clean, it could turn into clogged and respond slowly. That is when you can encounter an Codes error because of possible conflicts or from overloading your hard drive.
Once you clean up these types of files using Disk Cleanup it could not just remedy Nps Error Codes, but could also create a dramatic change in the computer’s efficiency.
Tip: While ‘Disk Cleanup’ is definitely an excellent built-in tool, it even now will not completely clean up Nps Error discovered on your PC. There are numerous programs like Chrome, Firefox, Microsoft Office and more, that cannot be cleaned with ‘Disk Cleanup’.
Since the Disk Cleanup on Windows has its shortcomings it is extremely encouraged that you use a specialized sort of challenging drive cleanup and privacy safety application like CCleaner. This system can clean up your full pc. If you run this plan after each day (it could be set up to run instantly) you are able to be assured that your Pc is generally clean, often operating speedy, and always absolutely free of any Codes error associated with your temporary files.
How Disk Cleanup can help nps reason code 22
1. Click your ‘Start’ Button.
2. Style ‘Command’ into your search box. (no ‘enter’ yet)
3. When holding down in your ‘CTRL-SHIFT’ important go ahead and hit ‘Enter’.
4. You will see a ‘permission dialogue’ box.
5. Click ‘Yes’
6. You will see a black box open up plus a blinking cursor.
7. Variety in ‘cleanmgr’. Hit ‘Enter’.
8. Now Disk Cleanup will start calculating the amount of occupied disk space you will be able to reclaim.
9. Now a ‘Disk Cleanup dialogue box’ seems. There will be a series of checkboxes for you personally to pick. Generally it will likely be the ‘Temporary Files’ that consider up the vast majority of your disk area.
10. Verify the boxes that you want cleaned. Click ‘OK’.
How to repair nps reason code 48
3. System Restore can also be a worthwhile device if you ever get stuck and just desire to get back to a time when your computer system was working ideal. It will work without affecting your pics, paperwork, or other crucial information. You can discover this option with your User interface.
Nps Error
Manufacturer
Device
Operating System
Nps Error Codes
4.5 out of
5
based on
49 ratings.
Hi !
I’m trying to setup a captive portal (pfsense 2.2) for the wifi in a network that is managed with pfsense firewall.
The pfsense wifi interface is 10.1.0.254/16 and lan is 10.0.0.254/16.
DC server is on lan @ 10.0.0.5.
I’m using a vm to test portal authentication and the error i’m getting on with the windows server is an event 13 : https://technet.microsoft.com/en-us/library/cc735406%28v=ws.10%29.aspx
«A RADIUS message was received from the invalid RADIUS client IP address 10.0.0.254.»
The method i’m following is this one: https://www.youtube.com/watch?v=aCgsEAfn36c
I’ve managed successfully to make it work in another 2 setups so i know it can work that way.
From a tcpdump on the pfsense, all i see when a login attempt happens is this log on the lan intf (nothing seems to happen on the wifi intf):
the ip 10.1.1.1 is the one of the vm that is logged in the domain, the NPS accepts all domain users.
10.0.0.254.59882 > 10.0.0.5.1812: [udp sum ok] RADIUS, length: 188
Access Request (1), id: 0xae, Authenticator: *****
NAS IP Address Attribute (4), length: 6, Value: 10.1.0.254
NAS ID Attribute (32), length: 21, Value: pfSense.localdomain
Username Attribute (1), length: 4, Value: user
Vendor Specific Attribute (26), length: 58, Value: Vendor: Microsoft (311)
Vendor Attribute: 25, Length: 50, Value: *******
Vendor Specific Attribute (26), length: 24, Value: Vendor: Microsoft (311)
Vendor Attribute: 11, Length: 16, Value: ...........F.7I1
Service Type Attribute (6), length: 6, Value: Login
NAS Port Type Attribute (61), length: 6, Value: Ethernet
NAS Port Attribute (5), length: 6, Value: 2002
Framed IP Address Attribute (8), length: 6, Value: 10.1.1.1
Called Station Attribute (30), length: 12, Value: 10.1.0.254
The thing is i got no issue with ip or dns pinging, so i can’t figure out what is going wrong…
Ideas are much welcome !
Thanks for reading