Neat! Sounds like an issue with the NAT code in the ActionTec. We've never run into this, but it sounds intriguing. I'm not very familiar with the ActionTec internals, so I"m not sure this is possible, but can you get the routing table and dynamic NAT table when the problem is occuring? The cisco equivalents would be show ip route and show nat. Just to be sure and eliminate the ActionTec as the problem, can you tcpdump from both your machine and the colo box and confirm that traffic is leaving your network and the colo box is NOT getting it? If it does turn out to be the crAptionTec, you might want to just pick up a 678 off of Ebay and save yourself a lot of hassle. AT tech support is alright (when you have the ISP on the phone, and have already done the troubleshooting). But we've seen soem problems with the code in the past, and they really don't appear to be "the shite" that Qwest makes them out to be. Adam Maloney Systems Administrator Sihope Communications On Sat, 8 Nov 2003, Michael D. Cassano wrote: > I recently got 256K/256K DSL through Qwest and Black-Hole (ISP). I have the ActionTec R1524SU DSL modem/router, with the most recent firmware. > > I also have a colocated Redhat 7.3 (fully patched) web server. > > I have alot of forums running on my web server, using YABBSE. Whenever I make one or more (most the time around 2 or 3) posts ot the forums I can not longer access my remote web server. I cannot ping or otherwise connect to the server from any machines on my network. If I telnet into the ActionTec router I can NOT ping the server from the router either. > > Once this happens I can still ping/connect to the other colocated servers I have, no problem. If I reboot the Actiontec router I can connect again, but if I make a couple more posts at the forums then I get blocked again. > > I can browse the sites on my web server just fine, for hours, the only problem comes when I go to post on the forums. Anyone else on the Internet can also makes posts/connect just fine to the web server while I am locked out. > > Any ideas?? I have contacted Black-Hole support and they have no solutions. > > It seems like it could be something with my web server configuration, but it's not just Apache, I can't even ping the machine. And it's not a firewall issue, I have tried turning off the firewall for extended periods of time and this still happens. I was on Black-Hole 56K Dialup for almost 4 years and I never had this problem. > > Thank you for reading! > Mike _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list