Web shield blocking access to 192.168.1.100, even with exclusions

[Eddy]

35+ years IT for me

[REDACTED]

35+ years IT for me

I believe it.  We don't have to turn this into a pissing contest 

[DavidR]

@  quastjoe
Sorry if I come to this party late, I have quickly skimmed what has been posted, but I could well have missed something. Excuse me if I have missed something and ask about it again.

Does this synaccess functionality use a program to control any traffic over the browser connection ?

If so:
1.  I wonder if checking Web Shield > Customise > Main Settings > now check the 'Scan traffic from well-known browser  processes only' option.
or
2.  You might consider the Web Shield > Customise > Exclusions > scroll down to the Processes to exclude - check that box and add any process involved in synaccess functionality.

[REDACTED]

@  quastjoe
Sorry if I come to this party late, I have quickly skimmed what has been posted, but I could well have missed something. Excuse me if I have missed something and ask about it again.

Does this synaccess functionality use a program to control any traffic over the browser connection ?

If so:
1.  I wonder if checking Web Shield > Customise > Main Settings > now check the 'Scan traffic from well-known browser  processes only' option.
or
2.  You might consider the Web Shield > Customise > Exclusions > scroll down to the Processes to exclude - check that box and add any process involved in synaccess functionality.

David,

Thank you for the suggestions, but I don't think either will help.

It isn't a program that runs.  It is a web interface that is hosted by the device itself over the LAN.

So we would just type in the IP in any browser to log into it and manage it.

[DavidR]

OK, sorry about that.

[lukor]

Hi quastjoe, very strange problem especially considering the fact that whitelisting the url does not help. We process the whitelist in the user-mode, so there is still some processing of the packets in kernel and we might corrupt something there.

Would you be able to capture a packet dump (Wireshark) for us? And what about avast 17.5 beta? Wouldn't that help? We have made one update in the packet parser inside the kernel driver in this upcoming release. It is possible that we have already fixed the issue.

Thanks
Lukas

[bigwilly_312000]

Did you try pressing the reset button on the device and reset
To factory default settings ?? May have to hold the button in a
Few seconds to fully reset.

[Alikhan]

I've received information that this issue should be fixed in latest BETA.

[REDACTED]

dunno if its gonna work.I configured IP camera's at home back then, The web interface only works in IE(Internet Explorer) browser which supported the device plugin. Newer browsers like chrome doesnt work.
=
try pinging the ip address if there is a response.
=
also, the network topography is kinda off,  u need at least 2 LAN cards or a LAN card with two ports on each of them to be able to work(CLASSIC) OR connect them to a HUB or a SWITCH(by today standards).
=
note: still an IT student, I MIGHT BE WRONG.

[bruce_b]

Try adding the IP for the modem or router into your browser network connections "no proxy list" .... This has been known to fix issues with connecting to the modem / router in the past. Very easy to do.
For Firefox: Tools, Options, Advanced, Connections, Settings ... no proxy list is in there, but you will need to click
on Manual Proxy radio button, then enter the IP's you want to bypass the proxy / internet .. Then recheck "No Proxy" button.

Internet explorer is similar to do.