Fri Jul 26, 2013 5:26 pm
Serviio and Norton 360 (fixing the issue) Problem Fixed
Disclaimer- All modifications listed below require an extreme knowledge of computers (as well as Norton)
Possibly someone could make this easier, and or check the information I have presented. Make no modifications without backing up all your files, so that if something does not work you may return to what you have-
This worked for me, an I have posted it to share- I am not responsible, for the modifications you make to your computer.
However would like feedback from other users.
Windows 7
Norton 360
Sony BR Player
I was running Norton 360, as well as serviio, for quite a while- Then One day all went away! I checked port 1900 as well as 8895 (all was good) however I no longer saw my connections (on a Sony BR Player)
I was totally upset, Serviio was showing as having started, however was no where to be found, when checking the Sony device for my Serviio Network.
Having Multiple Backups of my hardrive I decided to get to the bottom of this problem. I tried disabling Norton's Firewall, THIS DID NOT WORK (even though this was the problem)
I ended up Looking at the advanced Firewall Rules inside of Norton, and found my problem there. There was a rule (labeled Windows File Sharing Default) when I clicked on the edit tab it refused to allow
port 139 traffic in any direction. I tested this by allowing traffic on this port, rebooted, and Lo and behold ALL WAS WORKING!.
If you research port 139- You will find as I did that this port can allow others to share your files, without your knowledge-All depending on how this is set up. Without a windows password-
your network drive could be mapped an accessed by others.
The Area in Norton is Located in Advanced Settings and Traffic Rules (in the Firewall Settings)
The Rule I modified was Block Windows File Sharing (if you click on modify the port will be listed as local netbios-ssn(port 139)( it shows in communications) I changed this rule from Block- to Allow Connections From Other Computers.
I further specified Any Computer in the local Subset (by clicking that button (under the computers tab). I clicked save and rebooted. My Servioo was now Working and Communicating.
Realizing that this port was subject to attack I decide to write one more rule, in that same area
You may write Custom Rules in this area also- So I wrote a rule Called Jeff's Rule version 1 This rule helps (I believe) to ward off hackers as well as the last rule I talked about.
The Rules sez BlocK TCP and UDP communications on remote netbios (Port 139) This one under computers (I checked Any Computer).
I rebooted again and all still was working.
I then further checked my security of ports with https://www.grc.com/intro.htm (there are some nice security checking tools here) and my 139 port showed unavailabvle. (so I did what I set out to do.)
I hope this can help someone else- this took about a week to flog out- I love Serviio, and I needed it fixed. (Norton was unable to help in this problem)
Hopefully this post could be a Sticky to others, or someone could expand on this - Jeff
Possibly someone could make this easier, and or check the information I have presented. Make no modifications without backing up all your files, so that if something does not work you may return to what you have-
This worked for me, an I have posted it to share- I am not responsible, for the modifications you make to your computer.
However would like feedback from other users.
Windows 7
Norton 360
Sony BR Player
I was running Norton 360, as well as serviio, for quite a while- Then One day all went away! I checked port 1900 as well as 8895 (all was good) however I no longer saw my connections (on a Sony BR Player)
I was totally upset, Serviio was showing as having started, however was no where to be found, when checking the Sony device for my Serviio Network.
Having Multiple Backups of my hardrive I decided to get to the bottom of this problem. I tried disabling Norton's Firewall, THIS DID NOT WORK (even though this was the problem)
I ended up Looking at the advanced Firewall Rules inside of Norton, and found my problem there. There was a rule (labeled Windows File Sharing Default) when I clicked on the edit tab it refused to allow
port 139 traffic in any direction. I tested this by allowing traffic on this port, rebooted, and Lo and behold ALL WAS WORKING!.
If you research port 139- You will find as I did that this port can allow others to share your files, without your knowledge-All depending on how this is set up. Without a windows password-
your network drive could be mapped an accessed by others.
The Area in Norton is Located in Advanced Settings and Traffic Rules (in the Firewall Settings)
The Rule I modified was Block Windows File Sharing (if you click on modify the port will be listed as local netbios-ssn(port 139)( it shows in communications) I changed this rule from Block- to Allow Connections From Other Computers.
I further specified Any Computer in the local Subset (by clicking that button (under the computers tab). I clicked save and rebooted. My Servioo was now Working and Communicating.
Realizing that this port was subject to attack I decide to write one more rule, in that same area
You may write Custom Rules in this area also- So I wrote a rule Called Jeff's Rule version 1 This rule helps (I believe) to ward off hackers as well as the last rule I talked about.
The Rules sez BlocK TCP and UDP communications on remote netbios (Port 139) This one under computers (I checked Any Computer).
I rebooted again and all still was working.
I then further checked my security of ports with https://www.grc.com/intro.htm (there are some nice security checking tools here) and my 139 port showed unavailabvle. (so I did what I set out to do.)
I hope this can help someone else- this took about a week to flog out- I love Serviio, and I needed it fixed. (Norton was unable to help in this problem)
Hopefully this post could be a Sticky to others, or someone could expand on this - Jeff