Unable to remotely connect

[Zuglord 4]

Hello, I noticed i was unable to remotely connect to my server, and this appears to include LAN access as well. I do not believe i made any changes to my settings, how can i figure out what happened? 

 

I had been able to access content successfully for years before this. 

[pwhodges 2012]

3 hours ago, Zuglord said:

Hello, I noticed i was unable to remotely connect to my server, and this appears to include LAN access as well. I do not believe i made any changes to my settings, how can i figure out what happened?

First guess - you've updated Windows, and now the network on your server is designated as "public" instead of "private".

If not, then give us more information on what you are trying, and attach the log from the server covering your attempt to connect.

Paul

[Zuglord 4]

Thank you for taking the time to reply.

I have tried switching from private, to public, and back to several times, with several reboots. This does not seem to make a difference.

I do note, the connection failure message is instant, implying the connection is being refused, rather than timing out. 

I am unsure what logs to attach, here are the three that do not appear to be duplicates.

Please let me know what other data i can provide to further enable assistance. 

embyserver-63826839683 (1).txt hardware_detection-63826839695.txt embyserver (1).txt

[pwhodges 2012]

At the start of the Emby server log, it checks the local IP address, and finds that it is 192.168.1.10 .  So, check that in the Emby network settings, and in your port forwarding.  Set the network to private, not public (public is more restrictive, and can block things).

If that works, great.

(EDIT: had included remarks addressed at another user by mistake).

Paul

Edited August 5, 2023 by pwhodges

[justinrh 260]

On 8/5/2023 at 12:01 AM, Zuglord said:

this appears to include LAN access as well

It might be import to figure this out first.

To be sure, is your network profile Public or Private right now?

[Luke 42080]

@Zuglordhas this helped?

[Zuglord 4]

Hello

@pwhodgesI have dedicated this IP to my machine on local network. I have dedicated IP (not dedicated but static) via VPN service that also worked prior to August 1st. Now system fails to connect regardless of VPN connection, via both intranet and remote. 

@justinrhOver the course of the last few days, i have tried both private and public. I believe i was on private prior to these issues, and think i have made settings appropriate, or at least how they were before things stopped working. No change in connectivity, there is none. 

@Luke unfortunately, no. I remain in the same situation, able only to play on my local machine . I have attached updated logs. I appologize for not being as responsive as i would like to be but will attempt any and all suggestions.

Thank you all for your time and effort.

 

embyserver-63826959062.txt embyserver (3).txt

Edited August 7, 2023 by Zuglord
added logs

[Luke 42080]

Can you try turning off the vpn and sew how that compares? Thanks.

[Zuglord 4]

I had disabled the VPN for the most part, for the past week once this posting went live, only re activating last night and during text connections between private and public network testing as requested above

Edited August 7, 2023 by Zuglord
added content

[Luke 42080]

Ok, nothing shows up in the server log because the traffic isn’t even reaching the server.

I would suggest taking a look at our connection troubleshooter:

Connectivity

 please try the steps listed there and let us know which ones succeed and which ones do not. thanks.

[justinrh 260]

What clients are you trying connect with locally (not on the Emby server machine)?
Is IPv6 in the network picture at all?

What errors do you get?  (How do the clients respond?)

Can you ping the machine from with the LAN?

Have you checked the firewall?

[Zuglord 4]

Looks like simplest answer was the right one.

Update to antivirus had major changes to firewall. 

thanks - everything is back to how it needs to be!

[Luke 42080]

Thanks for following up.