[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

no connection to SBS 2003

The server was recently infected by W32.Mytob.KU@mm, Norton was able to remove the virus, but I still can't connect from any workstation. The server will not respond to pings from its dns name, or from it's local IP address. It's basically invisible on the network.

I asked this question 1 month ago, I had to reformat the server. Now the virus and the same problem are back and I dont want to reformat this time, please help!!
0
dave1184
Asked:
dave1184
  • 3
  • 2
  • 2
  • +3
1 Solution
 
Irwin SantosComputer Integration SpecialistCommented:
Are you using the SBS 2k3 as a workstation?
0
 
dave1184Author Commented:
yes it is always logged in, sometimes I guess certain users do
0
 
Irwin SantosComputer Integration SpecialistCommented:
having users work directly on the server is a BIG no-no... looks like the reformat is looming around the corner.
0
2017 Webroot Threat Report

MSPs: Get the facts you need to protect your clients.
The 2017 Webroot Threat Report provides a uniquely insightful global view into the analysis and discoveries made by the Webroot® Threat Intelligence Platform to provide insights on key trends and risks as seen by our users.

 
r-kCommented:
Try reinstalling SP1
0
 
rpggamergirlCommented:
W32.Mytob.KU@mm blocks sites thru your hosts file.

Check your hosts file to make sure sites are not blocked.
Windows XP = C:\WINDOWS\SYSTEM32\DRIVERS\ETC\hosts

delete anything under this entry:(if using default MS hosts file)
127.0.0.1 Localhost
0
 
dave1184Author Commented:
tried reinstalling sp1 no success, host file is normal, any other suggestions? I also spent some time with microsoft, reinstalling tcp/ip. no luck there either
0
 
r-kCommented:
You can try this:

 http://www.spychecker.com/program/winsockxpfix.html

I would not normally suggest this for a server, but since you are not having luck with the usual methods, may as well give it a try, I suppose.

Before doing the above, I would uninstall any AV and anti-spyware programs, and reboot, and see if that alone is enough to fix the problem.
0
 
hack-4-goodCommented:
on the server, can the server ping itself (its inside ip address)?
on the server, can the server ping 127.0.0.1 and get replies?

if the workstations are set to use the server as their dns server, as they should be, and if the servers DNS itself is hosed, that would cause this.

you could delete the zones you have in the servers DNS server, then recreate them... ipconfig /registerdns, wait 15 minutes, and see what happens

0
 
webquartersCommented:
Do a system file check or repair the Os with CD.
0
 
r-kCommented:
Thanks. Hope it helped.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

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