Problem with 802.1x authetification on a MPC3503

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • PillePalle
    Technician
    • May 2013
    • 42

    #1

    Problem with 802.1x authetification on a MPC3503

    Hi Guys

    I`m having a Case that is driving me nuts. A Customer wants to activate the 802.1 Authentification for a MPC3503. Anything works fine for the activation and all but as soon the want to authenticate on the Device they get a Error message on the Radius Server telling them that the User name or PW is not right.

    They got 14 other machines but none of the same type. On all others 802.1x is working just fine. I send a Technician that changed the Board and made a factory reset but the problem still persists. Firmware is up to date.

    I don`t know anymore what to do with this Problem. Maybe someone got an idea?

    This image is the Configuration on the Device and it`s absolutely the same on the other Devices where it works perfectly.

    Hediger.jpg
  • PillePalle
    Technician
    • May 2013
    • 42

    #2
    Re: Problem with 802.1x authetification on a MPC3503

    Hi Guys

    Well thanks for nothing

    Never no one had no idea in here but there is always a first Time right. Well i found the Problem and i can say it was no Ricoh Machine Problem but a Configuration Error that the IT Guy of the Company made on the Radius Server.

    I had to search for ages to find a decent Tutorial where i could check if anything was right and that helped to find the Error.

    So just in Case someone is getting to the Point where he has to make this here you got the 2 Documents that explain how this is done correctly.

    Have Fun with it. Case can be closed as Resolved

    8021x_Configuration_WinSrv2012.pdf

    Comment

    • anothertech
      Service Manager

      Site Contributor
      1,000+ Posts
      • Nov 2007
      • 1760

      #3
      Re: Problem with 802.1x authetification on a MPC3503

      Sorry for no replies, I don't think 802.1 Authentication is commonly used.

      Thanks for posting when you got it fixed.

      Comment

      Working...