Ideally the network should be fully ready when you start your node. For Windows you may configure a dependency, like there:
for Linux and service you should configure the service unit to start after the network is ready.
For docker nodes under Windows there is likely no issues, because to start a Docker desktop you need to login to the session and the network is likely fully ready to this time (unless you use Windows Task Scheduler, but in this case you may specify to trigger only when the network also ready).
For docker nodes under Linux (except podman and RHEL-like OSes where you can configure it as a some kind of service still using a docker image: Guide for installing Storage Node without docker (Linux)? - #3 by arrogantrabbit and of course you can configure it to start after the network is ready) you need to configure the docker daemon to start after the network is ready (I believe it’s by default though).
Please note, the node will check-in on the satellites once a hour by default and satellites will check QUIC availability again. So maybe you just need to refresh a dashboard to see the latest status.
However if you see errors related to QUIC/udp in your logs, then you likely has a network configuration issue or some filtering between the satellite and the node.