by DBeard » Oct 16 03 2:03 am
I have in fact installed the MSBlaster patch. We install all critical patches quickly. Any way to solve the issues caused by the MSBlaster patch?
OS = 2K
Internet Connectivity
I have two NICs, one for incoming one for outgoing via wingate. They have a gateway defined that is a Netopia Router/Firewall. Both of these are attached to my LAN and the gateway is my WAN. (T1 provided by cogent)
I have another NIC for incoming traffic for websites through a different provider with a gateway defined as a different Netopia Router/Firewall.
This NIC resolves via DHCP and is not accessible to others on the LAN. (Business Class DSL provided by SBC)
Bindings, AHA!!! I did not realize each service was bound to interfaces independently. I have made the change to reflect what I described above. All traffic comes in on one adapter and out on another, ignoring the third all together. Let me see how well this works. I can not run a full test until the weekend, however.
The third NIC interface has been stopped, mostly now because of 1.) Hacker 2.) Wingate chokes on the additional gateway. It has been enabled while wingate is running. Wingate won't see the new interface for upto an hour or so, then when it does, CPU spikes and Wingate quits functioning. (this also happens when I access Gatefilter, so I've discontinued using Gatefilter).
Gateways
For the first two NICs that Wingate is supposed to use and that are bound to in and outgoing (now on all services), have only one gateway.
The third NIC has it's own gateway.
It could be because I had improperly bound some services to use all connections (which I have changed now, due to your information) causing the problem with enabling the third NIC in the OS!?
Clients
Clients are not using any WGIC or Java. I currently do not authenticate, everyone uses the guest account. They connect via the proxy settings in the webbrowser. No NAT involved on this side of the routers.
Plugins
I have Gatefilter, it has caused 100% CPU spike when making changes to the ban list. I have discontinued it's use for now.
The infamous third NIC
When Wingate is already running and this NIC is enabled from the OS, after some delay, I'm notified via Wingate System Messages tab that it has found a new interface, after that Wingate stops passing traffic.
I have made changes to the bindings, that I missed, I hope that is the issue with the this third adapter. I will not be able to test it until this weekend, I can't risk taking the Internet offline again this week during core business hours.
I hope all that is clear, it's a ton of information to digest. I greatly appreciate your help with these issues. Ya'll have been very responsive. I hope I can iron these wrinkles out.
Last edited by
DBeard on Oct 24 03 1:22 am, edited 1 time in total.