On Thu, 2004-03-04 at 16:20, Jim Gifford wrote:
> Well, after having spent 3 days pounding on this, I finally found a bad
> ethernet cable that was causing all sorts of funky behavior. Replacing
> the cable and rebooting the m0n0wall fixed the DMZ issues I was having.
> Server NAT is working fine. The cutover to the m0n0wall setup from
> the old linksys NAT box was otherwise painless. Network downtime for
> clients was less than 2 minutes.
> The client is extremely pleased with the result.
Glad to hear its all working and you have a happy client. Happy clients
are nice clients - they generally refer you to their colleagues. :)
Dodgey Ethernet cables can be a right cnut to detect and will, as you
mentioned, play havoc with all of your tests and troubleshooting
procedures. Especially those that work 99% of the time, usually this 1%
doesn't fall due when testing the said cables. :(
VPN connections being made to a device instead of a network are a common
fault. Unfortunately, errors like this are REALLY easy to overlook - to
the point of recreating the same error when blowing the connection away
and starting from scratch. Sometimes the janitor can help! :)
Hilton Travis Phone: +61-(0)7-3343-3889
Manager, Quark AudioVisual Phone: +61-(0)419-792-394
Quark Computers http://www.QuarkAV.com/
(Brisbane, Australia) http://www.QuarkAV.net/
Open Source Projects: http://www.ares-desktop.org/
Non Linear Video Editing Solutions & Digital Audio Workstations
Network Administration, SmoothWall Firewalls, NOD32 AntiVirus
Conference and Seminar AudioVisual Production and Recording
War doesn't determine who is right. War determines who is left.