Samsung SCX-3405W WPA2 AES issues

Samsung SCX-3405W WPA2 AES Wireless connection problems

Problem with Samsung SCX-3405W WPA2 AES wireless security setting, failing to connect to a WPA2 wireless router.

Test setup

• Samsung SCX-3405W
  • Main Firmware Version V3.00.01.13 MAY-18-2012
  • Network Firmware Version V6.01.00(SCX-3400 Series)
  • IP Core Software Version 22.01.NW Stack Version
  • Engine Firmware Version V1.00.06 11-14-2011
  • SPL Firmware Version SPL 5.58 03-14-2012
• Apple Airport Extreme v5, firmware 7.6.4

Procedure

1. With router wireless security set to WPA/WPA2 Personal, everything works, connects by WPS, gets IP from DHCP, can be accessed through HTTP and set to connect without WPS.

2. I’ve set printer wireless to connect to WPA2 Personal with AES, re-entered key and saved settings. Printer still connected and working, but WPS led on printer panel turned off.

3. After setting router wireless security set to WPA2 Personal AES, printer does not reconnect at all.

More information on this issue

There is a report that firmware version SCX3405W_V3.00.01.17.exe resolves some wireless issues, related to not holding the assigned static IP and ping response time.

Ping test result on version V3.00.01.13 in the above specified setup

Pinging 10.0.1.3 with 32 bytes of data:
Reply from 10.0.1.3: bytes=32 time=441ms TTL=128
Reply from 10.0.1.3: bytes=32 time=118ms TTL=128
Reply from 10.0.1.3: bytes=32 time=17ms TTL=128
Reply from 10.0.1.3: bytes=32 time=36ms TTL=128
Reply from 10.0.1.3: bytes=32 time=35ms TTL=128
Reply from 10.0.1.3: bytes=32 time=32ms TTL=128
Reply from 10.0.1.3: bytes=32 time=58ms TTL=128
Reply from 10.0.1.3: bytes=32 time=76ms TTL=128
Reply from 10.0.1.3: bytes=32 time=75ms TTL=128
Reply from 10.0.1.3: bytes=32 time=53ms TTL=128
Reply from 10.0.1.3: bytes=32 time=12ms TTL=128
Reply from 10.0.1.3: bytes=32 time=92ms TTL=128
Reply from 10.0.1.3: bytes=32 time=81ms TTL=128
Reply from 10.0.1.3: bytes=32 time=70ms TTL=128
Reply from 10.0.1.3: bytes=32 time=59ms TTL=128
Reply from 10.0.1.3: bytes=32 time=58ms TTL=128
Reply from 10.0.1.3: bytes=32 time=46ms TTL=128
Reply from 10.0.1.3: bytes=32 time=33ms TTL=128
Reply from 10.0.1.3: bytes=32 time=20ms TTL=128

Ping statistics for 10.0.1.3:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 441ms, Average = 74ms

Firmware update

Samsung does not provide historical firmware updates for download, only the latest version is available for download on their support website

That may be because of firmware hacks available for firmware versions up to V3.00.01.19, fixing the toner cartridge chipset for refill.

Older firmware updates can still be found on other websites like softpedia.com, just google for desired version.

Samsung SCX-3405W firmware changelog history

• V3.00.01.13 (MAY-18-2012)
• V3.xx.01.17
• V3.xx.01.19
  • Machine performance improvements
• V3.xx.02.00
  • From this version on, if update from an older than .02.00 version, a patch should be applied first
• V3.xx.02.01
  • Copy fixes and Machine performance improvements
• V3.00.02.02_GCP (MAY-15-2014)
  • Fixed the Google Cloud Print Issue
    

    							Category	Change Notes
    Main F/W	Engine	Emulation		Network	GUI	ETC
    V3.00.02.02_ 0401040_1.00	V1.00.14	SPLC	V5.58.01	–	–	–	Fix Defect	1) Fixed the Google Cloud Print Issue

Firmware versions availability for cartridge chip mod

After firmware update to v3.00.1.19 test

New firmware versions (changes from v3.00.1.13 highlighted in bold)

• Main Firmware Version V3.00.01.19 MAY-06-2013
• Network Firmware Version V6.01.01(SCX-3400 Series)
• IP Core Software Version 22.01.NW Stack Version
• Engine Firmware Version V1.00.11 10-31-2012
• SPL Firmware Version SPL 5.58.01 06-27-2012

Ping test results

When Power, WPS light and display are on

Pinging 10.0.1.3 with 32 bytes of data:
Reply from 10.0.1.3: bytes=32 time=1ms TTL=64
Reply from 10.0.1.3: bytes=32 time=1ms TTL=64
Reply from 10.0.1.3: bytes=32 time=1ms TTL=64
Reply from 10.0.1.3: bytes=32 time=1ms TTL=64
Reply from 10.0.1.3: bytes=32 time=1ms TTL=64
Reply from 10.0.1.3: bytes=32 time=1ms TTL=64
Reply from 10.0.1.3: bytes=32 time=8ms TTL=64
Reply from 10.0.1.3: bytes=32 time=1ms TTL=64
Reply from 10.0.1.3: bytes=32 time=1ms TTL=64

Ping statistics for 10.0.1.3:
Packets: Sent = 9, Received = 9, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 8ms, Average = 1ms

When only Power light is on (display and WPS light off)

Pinging 10.0.1.3 with 32 bytes of data:
Reply from 10.0.1.3: bytes=32 time=83ms TTL=128
Reply from 10.0.1.3: bytes=32 time=11ms TTL=128
Reply from 10.0.1.3: bytes=32 time=38ms TTL=128
Reply from 10.0.1.3: bytes=32 time=86ms TTL=128
Reply from 10.0.1.3: bytes=32 time=104ms TTL=128
Reply from 10.0.1.3: bytes=32 time=25ms TTL=128
Reply from 10.0.1.3: bytes=32 time=80ms TTL=128
Reply from 10.0.1.3: bytes=32 time=108ms TTL=128
Reply from 10.0.1.3: bytes=32 time=36ms TTL=128
Reply from 10.0.1.3: bytes=32 time=85ms TTL=128
Reply from 10.0.1.3: bytes=32 time=104ms TTL=128
Reply from 10.0.1.3: bytes=32 time=40ms TTL=128

Ping statistics for 10.0.1.3:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 108ms, Average = 66ms

Changing printer from WPA2 Personal TKIP-AES to AES resulted in WPS led turning off, printer still connected

Restarted printer to check if WPS led turns on, printer powers on but WPS led button turns on only after pressing it.

Changing router from WPA/WPA2 Personal to WPA2 Personal AES

Changing router setting resulted in router restart, WPS led turning off, printer not reconnecting after router restarted.

Restarted printer, pressing WPS button does nothing..

Changed back router setting to WPA/WPA2 Personal, printer not reconnecting after router restarted.

Pressing WPS button on printer does nothing but bring from standby to on.

Restarted printer, WPS button light came on by itself.

Conclusion

The Samsung SCX-3405W WPA2 AES problem was still not solved in V3.00.01.19, and I doubd they solved it in the latest V3.00.02.02.