Treeroof Posted August 25, 2015 Share Posted August 25, 2015 Bug Submission: Category: General Issue Title: 147734 osx_steam Local server visible but not allowed to connect - long cable suggested Issue Description: Two Macs on the same LAN, one is host the other joined fine as of last night (i.e. prior to update!) but since the update the "Server only allows local connections." message appears when trying to connect to an existing or new host instance. Taking the suggestion literally, turned off networking and joined via thunderbolt assigned IP addresses in the same subnet - GREAT command line ping From 169.254.0.1 ... PING 169.254.0.2 (169.254.0.2): 56 data bytes 64 bytes from 169.254.0.2: icmp_seq=0 ttl=255 time=0.300 ms 64 bytes from 169.254.0.2: icmp_seq=1 ttl=255 time=0.405 ms 64 bytes from 169.254.0.2: icmp_seq=2 ttl=255 time=0.358 ms Also tried new world, same results - "Server only allows local connections." Can't get more local than hooked together. Steps to Reproduce: Update to 147734 osx_steam on two Macs Host a local game on one, attempt connection with the other. Link to comment Share on other sites More sharing options...
boggan Posted August 25, 2015 Share Posted August 25, 2015 Same here Linux server, I got this issue right after updating the server, can't host dedicated LAN game anymore, even when both machine are on the same subnet. Link to comment Share on other sites More sharing options...
Developer Diabu Posted August 26, 2015 Developer Share Posted August 26, 2015 Hello,We are currently working on this issue, we will tell you when the bug will be fixed.Thanks for the report : Link to comment Share on other sites More sharing options...
chris11 Posted August 28, 2015 Share Posted August 28, 2015 I have the same problem Link to comment Share on other sites More sharing options...
necropotame Posted August 29, 2015 Share Posted August 29, 2015 Same for me.Host on Linux, client on Windows Link to comment Share on other sites More sharing options...
smcv Posted September 2, 2015 Share Posted September 2, 2015 I also had this bug on Linux, but build 148470 (2015-09-01) fixes it for me. Hopefully the same is true for OS X. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.
Please be aware that the content of this thread may be outdated and no longer applicable.