>> Sorry, I must have misunderstood completely. I have never used the   
   >> Windows firewall on my BBS boxes, so it didn't even cross my mind   
   >> thjat this was the issue.   
   > your internal machines are all connected to the same network and are   
   > running naked with no protecting from each other?   
      
    TM> I have no internal threats, one firewall against the Internet is   
    TM> more than enough.   
      
   so you trust all machines that may be brought into your place and connected to   
   your network?   
      
   >> Lap Top? Are you running your BBS system on a lap top computer? are   
   >> you seroius?   
   >what's wrong with that?   
      
    TM> Lap tops are not designed to run 24/7.   
      
   i don't know about "designed" but i have three of them here that have all been   
   running 24x7 for over 5 years... i'm also aware of several thousand all over   
   the world who use laptops as their firewall machine running customized *nix   
   installations... a huge majority of those also run 24x7... especially those in   
   "small" (<1000 employees) corporate and SOHO environments...   
      
   > my laptop is more powerful than any of my workstations   
   > and servers... so what... there's nothing wrong there...   
      
    TM> Not the case here. All of my stationary systems except the old BBS   
    TM> box are more powerful than any of my lap tops. BBBS/NT however   
    TM> requires very little "juice" to run properly, so that is taken care   
    TM> of here by a very old desktop computer, with Windows Server as OS.   
      
   that's all fine and good but denigrating someone for running their setup on a   
   laptop or no longer trying to support them because of that is No   
   AGoodThing :?   
      
   > heck, i know many folks using a laptop as their perimeter firewall    
   > because it is low power, has built in battery for power failures, and    
   > is fast with plenty of memory for filtering and scanning web pages    
   > (squid), email (smtp proxying) and handling their routing needs...    
   > again, so what...   
      
    TM> Except that it's not built for 24/7 operation. :-)   
      
   and? why do you think it is not built for 24x7 use?   
      
   >> I rest my case. Sorry Rudi....   
   > the hardware is not the problem... the OS limitations are the problem... at   
   > least one problem, anyway...   
      
    TM> I beg to differ, both are a problem as far as I'm concerned.    
      
   whatever... narrow minded is narrow minded as far as i'm concerned ;)   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)