That will tell the workstation to send traffic directly to the firewall, bypassing the router. On the workstation verify that RDP fails. In my experience, this sort of thing breaks RDP, SSH, or any sort of secure protocol that's sensitive to spoofing. If it tries, the router will most likely tell it to substitute the PC's MAC for the router's MAC on subsequent frames. The firewall will go directly to the PC because it has no reason to go through the router. Having the PC's gateway and the router's next hop in the same subnet will cause asymmetrical routing on the return. ![]() It's common in small business, but it causes no end of problems. The root of your problem is using a FW as a router. What's the square box with the arrows? Is that a switch? I'll assume so because it has no IP. That may explain the on again/off again with the PC firewall. Rebooting (or ending the session) would clear the entry from the table. I'd guess that if you start a session with the Win FW off, and then enable it, it will note that there is already a session open and create an entry in the established session table.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |