We are up!

You guys nailed it with our terminal input.
Our initial connection to the device was via Terminal (explains brief connectivity before we began over-writing) but we quickly switched to SerialTools to mitigate the "creep" to the right and lack of echo.
We shifted back to Terminal and were able to successfully configure our new Printer

--- You guys were tremendously helpful ---

Good call - We are using Apple/USB

I will definitely explore the thread you linked and reply after testing (and lunch)

This is a wonderful forum!

Thank you for your help Droftarts and Phaedrux,

We do have 2.4 available and bandsteering is not aggressive in our environment.

I cannot see the unit referenced anywhere in our systems, so it never reaches our Wi-Fi controllers, DHCP server, etc.

It does not appear to be successfully storing networks (it was able to briefly a couple of days ago)
Output:
WiFi module stopped
ok
M552
WiFi module is disabled
ok
M552 S0
ok
WiFi module started
M552
WiFi module is idle
ok
M587 S"BA-Devices" P"******"
M587
Remembered networks: none
ok

Notes:
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5v0.11
Board ID: 0JD0M-9P6M2-NW4SD-6JTD8-3SN6R-*****

I'm not sure if this may be of use also...

M552 S0
ok
WiFi module started
M587
Remembered networks: none
ok
M587 S"BA-Devices" P"********""
M587
Remembered networks: none

Additional Info: I tested connecting to an iPhone hotspot but the duet2 fails to connect to that network as well.

M122 Output: === Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.5 (2022-11-30 19:36:12) running on Duet WiFi 1.02 or later + DueX5v0.11
Board ID: 0JD0M-9P6M2-NW4SD-6JTD8-3SN6R-9UQMK
Used output buffers: 1 of 26 (4 max)
=== RTOS ===
Static ram: 23836
Dynamic ram: 77256 of which 12 recycled
Never used RAM 8120, free system stack 176 words
Tasks: NETWORK(ready,8.2%,331) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,91.2%,461) IDLE(ready,0.5%,30), total 100.0%
Owned mutexes: USB(MAIN)
=== Platform ===
Last reset 00:02:39 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 8120, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 27.1, current 30.9, max 31.2
Supply voltage: min 1.3, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/14, heap memory allocated/used/recyclable 2048/212/8, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a
Driver 1: standstill, SG min n/a
Driver 2: standstill, SG min n/a
Driver 3: standstill, SG min n/a
Driver 4: standstill, SG min n/a
Driver 5: standstill, SG min n/a
Driver 6: standstill, SG min n/a
Driver 7: standstill, SG min n/a
Driver 8: standstill, SG min n/a
Driver 9: standstill, SG min n/a
Driver 10:
Driver 11:
Date/time: 1970-01-01 00:00:00
Cache data hit count 4294967295
Slowest loop: 500.26ms; fastest: 0.15ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 10.6ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is ready with “M122” in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Filament sensors ===
Extruder 0 sensor: no data received
Extruder 1 sensor: no data received
=== DueX ===
Read count 1, 0.38 reads/min
=== Network ===
Slowest loop: 11.17ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 0 of 8
= WiFi =
Network state is changingMode
WiFi module is idle
Failed messages: pending 0, notready 0, noresp 3
Failed to get WiFi status
Socket states: 0 0 0 0 0 0 0 0

Hi All,

We have a brand new Modex180 in-house and got the wifi to connect briefly this morning but now it is no longer pingable or visible from our wifi controllers.

This is a wpa2 network, in an Aruba environment and running on AP 535's
The signal strength is excellent.

I'm wondering if this community can share any troubleshooting steps with us to make the system usable.

Note: Please do not recommend restarting our router(s) - We (the IT department) will not consider this a viable troubleshooting step.