After using this program for a few months I thought I got the hang of it, no so, Transit Packet Madness has set in again and I cant remember how i fixed it last time.
Ok heres the setup if anyone can help.
Server has various IP's bound to the adapter
10.68.47.41 Default
10.68.47.42
Waxy.org: Links Miniblog::
Tina Feys pinball past (she provided voices for the 1997 game Medieval Madness) Vinylscrobbler (packet sniffing Shazam to update Last.fm from analog
http://www.waxy.org/links/HOME |
10.68.47.70
10.68.47.71
10.68.47.72
statesman.com::
March Madness. Life. Books. Faith. Gardening. Glossy. Health & Medical. Life Guide/ Consumer by the Federal Transit Administration revealed that, based
http://www.statesman.com/blogs/content/shared-gen/blogs/austin/opinions/index.htmlHOME |
10.68.47.77
10. is example only.
Anyway, when someone tried to reach a game server located on 42, 70, 71, 72, or 77 I see Transit Packet rule kick in.
I know about the transit rule, but these packets are destined for my machine, just one of the other addresses other than the default, so it should allow it.
Any ideas?
Oh and it's kinda difficult to open the 5 gb log file :stunned:
I re-installed the machine today, loaded my saved config and was greeted with transit packet rule, oh happy days.
Thanks
Would you be using multiple IPs because you are running VMWare? If so, there have been multiple threads about this in the past and a search should turn up some possibilities (IIRC, you need to run it in bridged mode).
Otherwise, it would appear that Outpost is not picking up your secondary IPs for some reason. Try doing a Detect under Options/System/LAN/Settings and checking that all the IP addresses are listed separately. If not, then you may need to add them individually yourself (using a 255.255.255.255 subnet mask) - if so, ensure that the Auto-Detect box at the bottom is cleared.
HI there, no it's straight Windows Server 2003.
It's been working fine for a few months, I took off my eval 2003 and installed my full version then couldnt remember how the firewall was setup. I did take a backup config, used that but still got the transit packet problem.
Just dont understand it. Done the detects etc, finds my network address XX.68.47.0 should it see each individual IP or just the network address?
The IP's are all live external IP's on a 128 subnet.
I'm baffled by it.
I would suggest clearing the existing entries in your LAN settings and adding each IP address individually (with a 255.255.255.255 subnet mask). I suspect that your setup (multiple IP addresses within a single network subnet) may be confusing the auto-detect and having a knock-on effect with regard to application of the Transit Rule.
 Red Hat's Rough Recovery From CFO Exit
 Windows Live Finds a New, Pre-installed Home |
Transit Packet Madness