False Error on Steam Link if host PC is connected via Ethernet Cable and Steam Link is wired (Port Error: 27031)

[Torte de Lini]

Hello,

I've recently discovered an issue with my Steam Link not connecting to my host PC. When I first used it, it worked - but subsequent tries after failed to have it connect to the PC under the false-error: "could not connect through port 27031"

I've done everything else suggested throughout the years:
- Port-forward locally (through rules on Windows Firewall)
- Port-forward on my ASUS Home Router
- Disable Firewall on the Router
- Disable Firewall on the home PC
- Reset back to Factory Setting 2x

When I used Steam Link to connect to my Surface Book, it worked flawlessly.

--
I realized that it was a port-forwarding or firewall issue but an incompatibility in recognizing the different connection types (to note: I tried by 2.4Ghz and 5Ghz connections).

Simply put If you're getting the error that a port is block (27031), have your PC be on an wireless connection as your Steam Link [or wired if the Steam Link is wired] to resolve this error

If it's possible to push out a fix for this issue, I'd appreciate it.

[Xjph]

Link and PC don't have to be on the same connection type. I'm not sure how you came to your conclusion, but my wireless Link works perfectly with my wired PC.

Do you by any chance have any wireless isolation settings enabled on your router? That would separate your wired and wireless connections into separate logical networks.

[Torte de Lini]

Автор сообщения: Vithigar

Link and PC don't have to be on the same connection type. I'm not sure how you came to your conclusion, but my wireless Link works perfectly with my wired PC.

Do you by any chance have any wireless isolation settings enabled on your router? That would separate your wired and wireless connections into separate logical networks.

My approach is broken down into the post.

Tell me where I can see this 'wireless isolation setting' and I'll check. I'm using the ASUS RT-AC56U

[wolffenstein]

What is the IP address and subnet of the host PC, your Steam Link (both when wired and wireless), and your Surface Book?

[Torte de Lini]

Автор сообщения: wolffenstein

What is the IP address and subnet of the host PC, your Steam Link (both when wired and wireless), and your Surface Book?

Host PC: 192.168.1.9
Steam Link: 192.168.1.89
Surface Book: 192.168.1.252

[Zagreus]

Wireless isolation is called "AP isolation" and should be under wireless advanced or is called "professional" wireless settings perhaps in asus lingo.

Whether wired or wireless as long as they are on the correct subnet it should be fine.

Make sure the windows connection type is "home" or "work".

I did notice the IPs you are using are not linear order which the router would have given out by default e.g. not 1.9, 1.10 etc so did you chose them yourself?
Did you do this using DHCP reservations (the term asus use I think) or manual static addressing?

On some routers its possible for a wireless AND wired connections (e.g. two different mac-addresses) for single device to share the same IP address (something that causes nothing but problems in my opinion) If you did DHCP reservations make sure the wired and wireless cards have different IPs.

[Torte de Lini]

Автор сообщения: Zagreus

Wireless isolation is called "AP isolation" and should be under wireless advanced or is called "professional" wireless settings perhaps in asus lingo.

Whether wired or wireless as long as they are on the correct subnet it should be fine.

Make sure the windows connection type is "home" or "work".

I did notice the IPs you are using are not linear order which the router would have given out by default e.g. not 1.9, 1.10 etc so did you chose them yourself?
Did you do this using DHCP reservations (the term asus use I think) or manual static addressing?

On some routers its possible for a wireless AND wired connections (e.g. two different mac-addresses) for single device to share the same IP address (something that causes nothing but problems in my opinion) If you did DHCP reservations make sure the wired and wireless cards have different IPs.

I checked under Wireless -> Professional -> Set AP Isolated and the setting was already off.|

"Make sure the windows connection type is "home" or "work"." -> How would I do this? I see on my laptop that it says "public". My Host PC is wired-connected.

"I did notice the IPs you are using are not linear order which the router would have given out by default e.g. not 1.9, 1.10 etc so did you chose them yourself?"

No, this was automated. I've had a lot of PCs connected to this router over the years because I move countries/computers a lot. There can be over 7 devices connected to it, but not usually: 3x Laptop, 2x Desktops, Steam Link, 2x Phones, Console

"On some routers its possible for a wireless AND wired connections (e.g. two different mac-addresses) for single device to share the same IP address (something that causes nothing but problems in my opinion) If you did DHCP reservations make sure the wired and wireless cards have different IPs."

Tell me how to check this and I can but I did not do anything in this regard before-hand.

[Zagreus]

""Make sure the windows connection type is "home" or "work"." -> How would I do this? I see on my laptop that it says "public". My Host PC is wired-connected."

This is your problem.

In windows when you first connect to a network you get choice home/work/public.

Chosing public is what you would pick when you are in say a public wifi point like lets a say a coffee shop. It turns all security and firewall settings on. I know you said you turned off the firewall but give it a go perhaps you missed something when you did it.

Personally I set to "Work" when at home. Setting "home" turns on all the windows homegroup crap.

You have not mentioned your windows version but will be roughly the following:

To change from public go to Control panel->network and sharing centre.
it will show your network name. Under it will say home/work/public highlighted. Click on it and you allow to select again. DO NOT tick treat all networks this way. When you are not at home public is the safest thing to use.

[Torte de Lini]

Автор сообщения: Zagreus

""Make sure the windows connection type is "home" or "work"." -> How would I do this? I see on my laptop that it says "public". My Host PC is wired-connected."

This is your problem.

In windows when you first connect to a network you get choice home/work/public.

Chosing public is what you would pick when you are in say a public wifi point like lets a say a coffee shop. It turns all security and firewall settings on. I know you said you turned off the firewall but give it a go perhaps you missed something when you did it.

Personally I set to "Work" when at home. Setting "home" turns on all the windows homegroup crap.

You have not mentioned your windows version but will be roughly the following:

To change from public go to Control panel->network and sharing centre.
it will show your network name. Under it will say home/work/public highlighted. Click on it and you allow to select again. DO NOT tick treat all networks this way. When you are not at home public is the safest thing to use.

No, it's not my problem:

1. My Laptop is set to Public but the Steam Link CAN connect to it and properly stream
2. My Host PC is wired-connected, it does not have the option to set the 'status' of the connection to work, public or home.

As I said, I removed all firewall setting on the host PC AND the Router. I already eliminated this issue and it's relative to what you're suggesting (it's not even an option and if it was, I've already proven that the status of the network has no effect).

--
I firmly believe my assessment is correct. That if the connection is under two different states of connection (wired vs. wireless) the Steam Link will falsely display a port error.

[slouken]

Автор сообщения: Torte de Lini

Автор сообщения: Zagreus

""Make sure the windows connection type is "home" or "work"." -> How would I do this? I see on my laptop that it says "public". My Host PC is wired-connected."

This is your problem.

In windows when you first connect to a network you get choice home/work/public.

Chosing public is what you would pick when you are in say a public wifi point like lets a say a coffee shop. It turns all security and firewall settings on. I know you said you turned off the firewall but give it a go perhaps you missed something when you did it.

Personally I set to "Work" when at home. Setting "home" turns on all the windows homegroup crap.

You have not mentioned your windows version but will be roughly the following:

To change from public go to Control panel->network and sharing centre.
it will show your network name. Under it will say home/work/public highlighted. Click on it and you allow to select again. DO NOT tick treat all networks this way. When you are not at home public is the safest thing to use.

No, it's not my problem:

1. My Laptop is set to Public but the Steam Link CAN connect to it and properly stream
2. My Host PC is wired-connected, it does not have the option to set the 'status' of the connection to work, public or home.

As I said, I removed all firewall setting on the host PC AND the Router. I already eliminated this issue and it's relative to what you're suggesting (it's not even an option and if it was, I've already proven that the status of the network has no effect).

--
I firmly believe my assessment is correct. That if the connection is under two different states of connection (wired vs. wireless) the Steam Link will falsely display a port error.

What's the exact model of ASUS router you're using, so we can try to reproduce it here?

Thanks!

[Torte de Lini]

Автор сообщения: slouken

Автор сообщения: Torte de Lini

No, it's not my problem:

1. My Laptop is set to Public but the Steam Link CAN connect to it and properly stream
2. My Host PC is wired-connected, it does not have the option to set the 'status' of the connection to work, public or home.

As I said, I removed all firewall setting on the host PC AND the Router. I already eliminated this issue and it's relative to what you're suggesting (it's not even an option and if it was, I've already proven that the status of the network has no effect).

--
I firmly believe my assessment is correct. That if the connection is under two different states of connection (wired vs. wireless) the Steam Link will falsely display a port error.

What's the exact model of ASUS router you're using, so we can try to reproduce it here?

Thanks!

Asus RT-AC56U.
Let me know if that worked. I have multiple PCs so I can test multiple systems.

To note, this PC is very new (recently built yesterday) and the Surface Book is also brand new (swapped out an old one for this one that arrived 5 days ago).

It may be a router or build-relative issue as I set my father up a few years ago with the 66U and had no problems [and I recently checked on this last week before leaving to go back home].

[Torte de Lini]

Ok, I did more testing over the weekend. I'm 100% convinced it is a false-error message and I found the root of the problem.

I went out and bought a very long ethernet cable to then plug into my Steam Link and router. Naturally, it was then able to connect to my host PC.

Tried wireless vs. wired with another PC (PC-wired), it did not work posting the same "port error". I also turned off my TV's WiFi and all other PC's and phone devices WiFi and still received the same error.

I adjusted various settings via Big Picture Mode and In-Home Streaming: Same error

I turned off my secondary monitor, set my main monitor to 1080p-60Hz: Same error

I manually factory-reset my Steam Link and used a flashdrive to manually update my Steam Link: Same error

I cannot think of anything else I could do relative to this error. It must be exactly what I've originally determined.

[Xjph]

Literally none of the things you tried rule out your wireless network not being routable to your wired network as a possibility, in which case the error is correct.

[Torte de Lini]

Автор сообщения: Vithigar

Literally none of the things you tried rule out your wireless network not being routable to your wired network as a possibility, in which case the error is correct.

I'm confident you didn't read the original post (as shown in your first reply) nor my follow-ups.

Additionally, you don't offer any alternative suggestions or ideas leading me to believe you don't have anything contributory to say.

Not going to correct someone who clearly doesn't want to help nor read my methods.

[Xjph]

I did read the original post. I, in turn, am confident that you don't understand the nature of the error you're getting. Nothing you've done eliminates "traffic cannot traverse from the wireless to wired network" as a possibility.

Original post:

Disabling router firewall: Not involved in the first place. Router firewall is on the WAN interface, which isn't used by the Link.
Port-forwarding on router: Completely irrelevant, for similar reasons. Port-forwarding on your router is a WAN interface issue.
Adding exceptions/disabling windows firewall: Could've been the cause, disabling it proved it wasn't.
Reset Link to factory: Eliminates Link configuration as possible cause.

Later post:

Tested wired connection: Confirms that issue only happens on wireless.
Tested wireless-to-wired with another PC: Confirms issue happens with other hosts.
Adjusted Steam streaming settings: None of them involve network discovery or connectability. Irrelevant.
Turned off second monitor: Doesn't involve network discovery or connectability. Irrelevant.
Factory reset/manual update: Already confirmed that Link configuration wasn't the problem, but you never know. Still doesn't address problem if the cause is wireless network traversal.

You're literally doing things at random now that have nothing to do with how your wireless network is handling traffic. Here are some things you can try in order of decreasing usefulness/simplicity that are actually related to the issue:

- Use In Home Streaming from another wireless PC running Steam (the surface pro maybe?) to connect to your wired PC. If this works it confirms there is something wrong with the Link, as it uses exactly the same method to find and connect to the host.
- Try to connect to any service running on a wired host from a wireless client. Windows file sharing, for example. If this works then it confirms that traffic can traverse from wireless to wired, if it doesn't then it confirms a wireless networking issue.
- Factory reset your router. This would eliminate any weird router configuration that might be interfering with wireless traffic.
- Try a different router entirely.

[Torte de Lini]

Given you, again, contribute nothing and simply act as a contrarian confirms my suspicion. Nice try.

I've ordered a PCI-E WiFi card to further test this.

Автор сообщения: Vithigar

I did read the original post. I, in turn, am confident that you don't understand the nature of the error you're getting. Nothing you've done eliminates "traffic cannot traverse from the wireless to wired network" as a possibility.

Original post:

Disabling router firewall: Not involved in the first place. Router firewall is on the WAN interface, which isn't used by the Link.
Port-forwarding on router: Completely irrelevant, for similar reasons. Port-forwarding on your router is a WAN interface issue.
Adding exceptions/disabling windows firewall: Could've been the cause, disabling it proved it wasn't.
Reset Link to factory: Eliminates Link configuration as possible cause.

Later post:

Tested wired connection: Confirms that issue only happens on wireless.
Tested wireless-to-wired with another PC: Confirms issue happens with other hosts.
Adjusted Steam streaming settings: None of them involve network discovery or connectability. Irrelevant.
Turned off second monitor: Doesn't involve network discovery or connectability. Irrelevant.
Factory reset/manual update: Already confirmed that Link configuration wasn't the problem, but you never know. Still doesn't address problem if the cause is wireless network traversal.

You're literally doing things at random now that have nothing to do with how your wireless network is handling traffic. Here are some things you can try in order of decreasing usefulness/simplicity that are actually related to the issue:

- Use In Home Streaming from another wireless PC running Steam (the surface pro maybe?) to connect to your wired PC. If this works it confirms there is something wrong with the Link, as it uses exactly the same method to find and connect to the host.
- Try to connect to any service running on a wired host from a wireless client. Windows file sharing, for example. If this works then it confirms that traffic can traverse from wireless to wired, if it doesn't then it confirms a wireless networking issue.
- Factory reset your router. This would eliminate any weird router configuration that might be interfering with wireless traffic.
- Try a different router entirely.