Ok, I've done my homework (after forgetting all about this, sorry). In red is what the default DHCP assigned IP address is via my main router, and this is already configured in AP mode with separate WiFi names setup. for configuration's sake, I'd like to keep any AP and switch above a .240 IP address on my home network for ease of remembering which is which. See below, and compare times if you'd like, they were run simultaneously to show that for a moment, it did recognize the newer IP, and then it reverts back to the old .22. I have even tried manually assigning through my main router via MAC, no success.
C:\Users\%username%>time
The current time is: 21:57:37.64
Enter the new time:
C:\Users\%username%>ping 10.0.1.22 -n 50
Pinging 10.0.1.22 with 32 bytes of data:
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 10.0.1.250: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Request timed out.
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Reply from 10.0.1.22: bytes=32 time<1ms TTL=64
Ping statistics for 10.0.1.22:
Packets: Sent = 34, Received = 29, Lost = 5 (14% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C
C:\Users\%username%>time
The current time is: 21:57:34.33
Enter the new time:
C:\Users\%username%>ping 10.0.1.250 -n 50
Pinging 10.0.1.250 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Reply from 10.0.1.250: bytes=32 time<1ms TTL=64
Request timed out.
Request timed out.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Reply from 10.0.1.22: Destination host unreachable.
Ping statistics for 10.0.1.250:
Packets: Sent = 21, Received = 17, Lost = 4 (19% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Control-C
^C