Author Topic: Unable to intialize UDP on opening dedicated.command  (Read 795 times)

I forwarded my ports then opened dedicated.command. The code said "unable to initialize UDP - error 5
Port init failed on port 192.168.1.* trying next port."
And it never worked. What is wrong, did I forward my ports wrong. I followed portforward.com. Plz help.

I forwarded my ports then opened dedicated.command. The code said "unable to initialize UDP - error 5
Port init failed on port 192.168.1.* trying next port."
And it never worked. What is wrong, did I forward my ports wrong. I followed portforward.com. Plz help.
I have a mac. This also may sound noobish. Sorry.

you can't forward ports on a mac. dur.
Does that mean macs cant host servers?


Yes you can.
I got my ip address, entered it on firefox, logged in, forwarded my ports (I followed the PortForward.com intructions so I think I did it right*), and then Blockland could not connect to my ports?

*I made the rule name "Application", a UDP, source ports any, destination ports range 28000-28030, WAN Connection Type "All Broadband Devices, Forward to Port: "Same as incoming port" When should this rule occur "Always" and entered this all. I have a Actiontec MI-424-WR router.

Don't you have to set up a static IP address too?

Don't you have to set up a static IP address too?
I did that too. Just forgot to mention it.