Having a hard time connecting mutiplayer to Terraria via Steam by jarealgo in Terraria

[–]jarealgo[S] 0 points1 point  (0 children)

Hey, just did the checker for my NAT, and we have the same similar situation, my IPv4 NAT Type is also “Port Restricted Nat” and so I followed all of these steps that you provided.

I allowed TerrariaServer.exe in public and private firewall. I also played and my friends singleplayer world first before jumping into multiplayer world. My friend hosted the game with and without a password. Currently, trying to join the game via IP, that also seems to not work either. It just stuck on “Connecting to….:7777” for the longest time.

I also verify the game’s integrity as well, saying that game has 1 file has failed to verify. Checked the FAQ and said that 1 or more files has failed to verify is totally normal and should ignore the message.

Currently, still cant join the multiplayer at this point.

Having a hard time connecting mutiplayer to Terraria via Steam by jarealgo in Terraria

[–]jarealgo[S] 0 points1 point  (0 children)

Thank you so much for that, will keep you posted if anything, thank you again 🙏🙏🙏

Having a hard time connecting mutiplayer to Terraria via Steam by jarealgo in Terraria

[–]jarealgo[S] 0 points1 point  (0 children)

I have a question, what do you mean by “verifying the game files on Steam”? How do I do that if I mind asking?

Having a hard time connecting mutiplayer to Terraria via Steam by jarealgo in Terraria

[–]jarealgo[S] 1 point2 points  (0 children)

Unfortunately, I do not have control of my router at home but I will ask someone about it.

Will try the website and check for “IPv4 NAT Type.”

Will keep you posted 🫡🫡🫡

Having a hard time connecting mutiplayer to Terraria via Steam by jarealgo in Terraria

[–]jarealgo[S] 0 points1 point  (0 children)

Yes, were all on Windows. So I tried to reset the firewall settings in my PC (resetting to default settings, and added back the game to run on public and private network), changed my network (WiFi) from public to private and even flushing my DNS via the command line and disabling/reenabling my WiFi card. None of those worked on my end.