I think this goes here, Problem with Plex Remote Access

Alciel

Honorable
Nov 9, 2013
203
0
10,690
I messed something up with my computer that's stopping my plex from doing remote access. I had an infected file on my computer so I rolled back, Then I had to fix my antivirus which is Kaspersky Total Security, It had a problem where it couldn't update. I contacted Kaspersky support and they told me to do this procedure on my computer.

These instructions were told to me by an official kaspersky tech.

This was done in an Admin Cmd prompt.

netsh
winsock
reset
netsh
int
ip
reset
all
netsh
winhttp
reset proxy
ipconfig
/flushdns

Restart the PC.

I did this but noticed that my internet was down so I ran the windows 7 64bit troubleshooter and got that fixed or so i thought.

When I went to check my plex server I noticed that I had the red exclamation point next to the remote access. What it says is that while my server is signed into plex its not reachable from outside my network. In the plex server web page it says that my private ip is 192.xxx.x.x: 32400 then there's a green arrow then my public ip 172.xxx.xxx.xx.xxx:32400 then it says X with internet greyed out.

As far as I know my ISP hasn't done anything, which happens to be AT&T Uverse, my router hasn't changed an Asus RT-N66u, The only thing that happened that could of changed it was the rollback or what kaspersky told me to do.

I have run into the problem of a double NAT before and I'm pretty sure I fixed it in my other thread. https://forums.plex.tv/discussion/214309/need-help-with-port-forwarding#latest

I also followed the Malware Guide on this forum posted by a Moderator, The steps included that I boot in safe mode then do a Malwarebytes Scan, That turned up nothing, So I then did ComboFix and that came up with a infected c:\windows\SysWow64\kernel32.dll file, But that was disinfected and then restored to a previous point. I used 2 other Scanners also, Kaspersky Total Security and Super Antispyware all 3 in Safe Mode.

I also did the Windows 7 SFC /Scannow, Nothing came up. I'm not sure what else to do.

Is there a way to rollback what I did with cmd prompt?
 
Solution
This has since been fixed. This was my solution.

I had to make my ISP router communicate with my Asus router then I had to make a static IP (Which was somehow cleared) once I remade the static IP again, I had to redo the port forwarding in my Asus to allow my static IP and port to be allowed though.

Doing this all just fixed my problem with my remote server issue.

I now have full access to my remote server again.

Alciel

Honorable
Nov 9, 2013
203
0
10,690
This has since been fixed. This was my solution.

I had to make my ISP router communicate with my Asus router then I had to make a static IP (Which was somehow cleared) once I remade the static IP again, I had to redo the port forwarding in my Asus to allow my static IP and port to be allowed though.

Doing this all just fixed my problem with my remote server issue.

I now have full access to my remote server again.
 
Solution