[Error Code] LDAP lookups - "Failed to resolve name in DNS server" <- C352s

[Guest]

Hi all,

We have several C352 printers and we need to authenticate them against AD. I have spent a long time testing and configuring LDAP to do lookups and each and everytime i click the "Test Connection" button I get the error Failed to resolve name in DNS server.
I know my DNS setting are correct and both forward and reverse maps resolve perfectly. (The printer has perfect LAN connectivity).

I am suspecting a firmware bug ?

Can anyone suggest how to debug this further ? (konica tools ?)

This is the current firmware dump (i have no clue what the latest is?)

MFP Controller BOOT Program
9J06-1E00-G00-01-000(00)
MFP Controller SubSet Program
9J06-1F00-G00-02-000(00)
MFP Controller
9J06-0100-G00-I8-000(00)
Operation PANEL Message Data
9J06-8100-G00-I2-008
FAX Board Controller1
　FAX Board Controller2
　IR
9J06-0023-G00-10-000
PRT
9J06-0050-G00-20-000
LPH
　ADF
9J07-0024-G00-06-000
Finisher
9J08-0071-G00-06-000
System Controller
9J06-1000-G00-I8-000(00)
Printer Controller
9J06-3000-G00-43-000(00)
Printer Controller-Font
9J06-3F00-G00-14-000(00)
Printer Controller-Demo Page
4037-3E00-G00-00-000
MIO
9J06-5000-G00-63-000(00)
PSWC
9J06-5100-G00-34-000(00)
MIB IF
9J06-5200-G00-20-000(00)
IPP IF
9J06-5300-G00-03-000(00)
External Controller IF
　TCP/Socket
9J06-6300-G00-00-000(00)
Open API
9J06-7000-G00-86-000(00)
Operation PANEL
9J06-8000-G00-E0-000(00)
CSRC
9J06-8300-G00-02-000(00)
PIC
9J06-8200-G00-07-000


Thanks

-Alex

[pepper38_cnd]

Maybe this will help?

[DeLF]

Maybe this will help?

Thanks, but i have tried all possible configuration possibilities and I still get the error Failed to resolve name in DNS server when clicking "check connection".

Besides resorting to a packet trace are there any other tools you can recommend to get more debug output than "Failed to resolve name in DNS server." on konica printers ?

-Alex

[JR2ALTA]

You could try to dump the DNS cache, from what I understand it's harmless and solves a lot of problems.

But Google it or talk to an IT professional first...

[Spidula]

Latest F/W is K0 for the 352s But I had an LDAP prob with a machine with K0 F/W on. I.T sorted it eventually, but don't know what the fix was!

[RRodgers]

Latest F/W is K0 for the 352s But I had an LDAP prob with a machine with K0 F/W on. I.T sorted it eventually, but don't know what the fix was!

Last time I had a problem with LDAP it turned out to be the time on the copier was off by more than an hour. CHECK the TIME on the copier.

[BlueBlazer]

Find out what your AD's server IP is and try connecting directly if flushing your DNS cache doesn't resolve the problem. Also double check that the IT department didn't do anything screwy with their AD server like set SSL or something.

[Stirton.M]