OP 6.7 blocking windows fileshare - strange problem

[Paradox52525]

Hi,

I've been having a problem the last few weeks with the latest version of Outpost Firewall 6.7. Two machines are involved - a Vista 64 machine with Outpost installed, and a Windows XP Media Center machine. The media center machine is accessing files from the Vista/Outpost machine via regular windows filesharing shared folders.

When I first attempt to access a shared folder from the media center, Outpost will block the incoming traffic. It lists the remote address as an IPv6 address (which is incorrect, the media center does not have IPv6 installed, and the Vista machine has IPv6 disabled on all network adapters). It shows the originating process as "System" and the block reason as "Learning Mode." I tried making a rule to allow this, but it still does not permit the incoming connection.

Here's the really weird part - if I wait about two minutes after the first attempt to access a share and then try again, it works! The incoming connection shows as the correct IPv4 LAN IP, and is allowed since the LAN is trusted. Still it's very annoying that every time I turn on the fileserver, I either have to suspend Outpost protection, or try to access the fileshares, then wait two minutes, and then try again. I never had this problem with 6.5 on the same system. I only started seeing it when I upgraded to 6.7 a few weeks ago.

Any thoughts?

[Paradox52525]

I've attached a screenshot of the Firewall window when the offending behavior is occurring. The source is identified as ::ffff:c0:a8:166. You can see in the screenshot that not every connection is blocked (the allowed connections from "FILESERVER" are from the same machine) but the end behavior is that I'll get a machine unreachable error. If I give it a few minutes and retry then everything works fine, but I have to do this little dance every time I use the media server.

[Paradox52525]

Sorry to bump, but I could really use assistance with this if anyone has any ideas. The same thing happened earlier today while trying to reformat a friend's PC. I have various utilities and software installs on shares on my main machine, and every time I had to reboot the machine I was working on, I could not immediately access my shares because of this issue. The only thing that works is to suspend protection in Outpost or shut it down.

[kronckew]

no specific cure, have a look at the following tho.

some of the newer windows flavours (win7) use ipv6 for home networking, not sure about latest vista incarnations. are their ip's in the lan settings with netbios enabled? check the machine.ini (with self protection off) there is a variable in there somewhere to block netbios by default. there are a whole lot of services vista/win7 need, upnp, ssdp, dcom, etc. as well as netbios. also make sure netbios over tcp is allowed in the advanced tcpip settings for the network adapter.

have you tried the trick of accessing shares by ip in the unc instead of share names? //johnsPC/emailshare becomes //192.168.2.17/emailshare, alternately try adding the ip and pcname to the hosts file in c:\windows\system32\drivers\etc, ie.
192.1689.2.17 johnsPC

this works if there is no browsemaster giving out names on windows networks...

[Paradox52525]

Thanks very much for the suggestions, but none of them have helped.
Netbios over TCP is enabled on the network adapter. Access via IP versus UNC path makes no difference. There are no IPv6 LANs in the LAN section of my firewall config, nor can it detect any. The only lan in the list is the regular 192.168.1.0 - which is trusted.

I tried manually adding ::ffff:c0a8 in several different ways (and trusting it), but that did not make any difference either. Allowing netbios in the machine.ini did not make a difference.

I don't understand why this IPv6 traffic is showing up. There is not a single PC or network device in the entire lan with IPv6 enabled on any adapter. I can only assume the traffic is being somehow misidentified by outpost. Even a global rule to allow this traffic does not permit it, it is still blocked by "Learning Mode."

This is getting to be very frustrating. Certain PCs cannot access my shared folders at all unless I suspend Outpost protection or shut it down.

[thalantis]

i have the same problem with the latest outpost security suite installed and network shares, when i uninstall outpost the network shares work fine

[thalantis]

when i have the shares already mapped and install security suite, the shares dont work after a reboot.

but when i first install the security suite and then map the drives, it goes good