Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 367
  • Last Modified:

SQL server causing network collisions

I am the IT admin for a medium size NT domain running win2k server, win2k pro terminals.

The network architecture is thus:
3 networks -->
192.168.0.0 --> A network specifically to connect to my router, contains no client computers
server-->router-->DSL modem

192.168.1.0--> A network for _most_ users. Using RAS I am able to bridge this with the other networks seamlessly, making my server also a gateway.

192.168.2.0--> A network for administrative users, so that our bandwidth use is not affected by, and doesn't affect, other users...

As I said-Server runs win2k server, sp4. Also running MSSQL server 2000.
Whenever the SQL server is running for more than a few minutes, it somehow takes over the network and sends massive amounts of data to one or other of the networking cards...
I can see the network lights blinking like mad, and the only fix I have found is to disable MSSQL server and restart the machine... Please note, even disabling the network cards does not fix the issue, as it only switches the traffic to another device...

Any questions for me? If I can provide more information I will.
0
jmecham
Asked:
jmecham
  • 3
  • 3
1 Solution
 
arbertCommented:
This sounds like slammer?  Are you sure you don't have a virus?
0
 
jmechamAuthor Commented:
housecall.antivirus.com says I don't, and I had applied the patch for it... I was thinking it might be something to do with IAS or IIS, possibly RAS...
0
 
arbertCommented:
There are a million possibilities.  Have you use NETMON to see what the packets contain?  That would probably be the next step--see whats in the packets and what ports are being used....
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jmechamAuthor Commented:
Problem is I can't do a whole lot of testing because the only cure is to stop SQL server and restart the machine... Try telling 15 users that you need to restart... heh
Just so you know, the packets look a lot like collisions, they aren't going anywhere... And they transmit _very_ fast, so much so that a 10/100 network is entirely bogged so that no traffic goes anywhere...
0
 
arbertCommented:
Well, you either keep rebooting the server, or you make some time for troubleshooting.  You need to get netmon (or some other sniffer on the network) and see what's going on.

Exactly how do you have RAS configured to bridge the networks?  Are you using a switch or hub on the network, or just the router?

Make sure you have all uneeded protocols turned off--you should, for the most part, only route TCPIP--make sure you aren't routing a bunch of broadcast messages.

0
 
jmechamAuthor Commented:
Nevermind all that. ;-) It _was_ slammer. Reason I couldn't detect it is because it is MEMORY resident only... No file for a virus scanner to catch, and it would only show while the machine was infected... IE while my networking issues occured... Meaning I couldn't scan w/housecall cause I can't get on the web. ;-) I applied the patch and all things are in order, thank you for pointing me in the right direction.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now