Search Issue Tracker

By Design

Votes

2

Found in

2017.2.3f1

2018.2.0f2

Issue ID

1064218

Regression

Yes

[Networking]Client side projects/builds cannot connect to Host side projects

Networking

-

Steps to reproduce:
1. Download and open the attached project
2. Build for standalone
3. Transfer build to a different machine
4. Start the build
5. In the original project, start the Playmode
6. Start as host
7. In the transferred build, enter the IP and connect as client

Expected result: both instances connect
Actual result: client is unable to connect

Reproduced on 2017.2.3f1, 2017.4.8f1, 2018.1.9f1, 2018.2.1f1, 2018.3.0a6
Not reproduced on 5.5.2f1, 2017.2.0a4

Notes: builds can still connect to builds

By Design: issue occurs if Editor is blocked for the current connection type in the Advanced Firewall Settings
Log in to vote on this issue

Comments (2)

  1. byrdarlbar

    Aug 24, 2018 12:28

    To get things to work again, the user must do the following in Unity 2017.x and later:

    On PC, go to Windows Defender Firewall -> Advanced Settings -> Inbound Rules

    Single Select the Unity applications with the "Block" action and bring up their context menu.
    Select Properties, click on the General tab, go to Action, and select "Allow the connection". Click OK.

    Also make sure the Unity applications are allowed under the "Allow an app or feature through Windows Defender Firewall" option.

  2. byrdarlbar

    Jul 30, 2018 13:15

    Under Severity you mention that there is a workaround. What is the workaround?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues