Just connected to my University's wireless network and I found that I could not connect unless outpost was disabled. Does anyone know what settings I need to make sure are set in outpost so that wifi will work? Please reply ASAP as I am surfing at uni without outpost! S.
Anything in your logs to indicate something being blocked that may need to be permitted? Regards, CrazyM
This is a log of the type of blocked connections that were occurring: 08/11/2005 13:09:25 NETBIOS IN REFUSED UDP 169.254.124.165 NETBIOS_NS Block NetBIOS Traffic I tried adding the domain name of my university in Lan settings and then allowing netbios connections but this had no effect.... Help! S.
Hi SimonCC! Outpost-Firewall Forums seem to be down atm, but I think I remember something about a new feature, that can - in some cases - block your connection, especially if your machine is in a big network. Try disabling the (advanced?) ARP-Filter. Greets Storm
Outpost forums seem to be up again! Maybe reading this posts by Paranoid2000 will help you: http://www.outpostfirewall.com/forum/showthread.php?t=15061#arp-faq Greets Storm
Have your checked your university's webpage on wireless access? If you have not yet, you might want to do it. This is because there might be some specific requirement for certain wireless network access. For example, some wireless network may require your computer firewall allows ICMP Echo In while some others do not. You also might want to check if you have correct rules on DHCP, your DHCP service is enabled and so on.
I had several problems with my wireless connection with Outpost as well. If I turn off the wireless connection (802.11b) and turn it on again, I cannot reconnect to the internet again (802.11g router). Sometimes after rebooting, I still could not reconnect to the net and I have to run WinsockFix. Anyway, I gave up and switched to ZA a week ago and have not experienced any connection problems since.
Many issues with wireless connections can be resolved by updating the network card drivers (trying to connect an 802.11b card to an 802.11g router is going to be a problem anyway since these are different protocols - the router presumably is automatically falling back to 802.11b). However disabling the Ethernet tab options for the Attack Detection plugin would be a sensible step to see if these were causing the problem.
