| Author |
 Topic  |
|
|
zinpin
Junior Member
Australia
202 Posts |
 Posted - 14 October 2005 : 22:15:13
|
I know I'm crazy for running norton Personal firecrap on my server but it's what I have and up to now it's been OK I guess.
Now though it's really giving me the s**ts. It's blocking the .net framework from running.
I had a closer look and I have the choice of adding the exe for permission but there's so many, which one is the right one.
I tried a few in the .netframework directory but had no joy.
Has anyone got an idea which exe I should allow?
TIA
<edit>
If there's no solution to this, which software firewall to you guys recomend for remote installation one that supports the .net framework and that won't lock you out the minute you install it.
</edit>
|
Edited by - zinpin on 15 October 2005 02:19:16 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 15 October 2005 : 04:03:30
|
Does it have an option to block script execution? If it does, try to disable it. I've given up on Symantec's firewalls long ago.
I use ZoneAlarm, but for remote installation it will block you, initially, so it doesn't seem to fit your requirements... |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
|
zinpin
Junior Member
Australia
202 Posts |
Posted - 15 October 2005 : 04:31:24
|
thanks ruirib I just checked but there's no such setting. BTW I'm running NPF 2004 if that's any help. As for remote blocking I've trialed a few Firewalls and this one at least is smart enough not to kick in on install.
Such a simple thing for the other firewalls to implement but yet they don't... I hope someone might have a suggestion. |
|
|
|
zinpin
Junior Member
Australia
202 Posts |
Posted - 15 October 2005 : 22:12:14
|
Finally got it working. :) here's what I did (maybe this will help someone else:
Got a spare computer, clean install it, run the website locally from it and made sure that I could access the site from a second computer on the network. Installed ZA on the first (brilliant program letting you know what exactly is accessed at any time) and then run the site as normal from the second machine. When I got to the part where the .net framework thing kicks in, I found the cause of the problem. DLLHOST.exe was not enabled on the firewall.
Then it was simple, RD the server and change the DLLHost setting of Norton Personal BaggerAll :)
Can you guys see any problem - security risk with permiting DLLHOST.EXE on the firewall? |
|
|
|
pdrg
Support Moderator
United Kingdom
2897 Posts |
Posted - 17 October 2005 : 05:38:12
|
| DLLHOST.EXE is a really generic container for running DLL's - just an fyi it is possible that any other peocess running as a DLL would then punch right through your firewall, be worth keeping an eye on just in case :) |
|
|
| |
Topic |
|
Topic Locked
