Hi @hacker05, welcome to the community and to OpenZiti!
As @stalow said, a missing policy can certainly cause this problem. The ziti CLI has a command that will help you verify if the network is setup correctly by making a client and server identity and then starting a test server to pass traffic from the client to the server. This command is:
ziti ops verify traffic
Run this ziti command from the client machine (or some other machine that isn't the controller or a router). You should see stuff like:
INFO successfully bound service: ...
INFO found terminator for service: ...
INFO successfully dialed service: ...
INFO traffic test successfully detected
INFO client complete
Can you run that and capture what you see? Another discourse post where I mention this sort of troubleshooting is over at Windows Desktop App Error - #15 by TheLumberjack -- have a look at that too and see if it helps