Re: XP, or Not XP....that is the question.....

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: IBC (spamityspam_at_spam.spam)
Date: 02/27/04 

Date: Fri, 27 Feb 2004 12:59:10 -0600

Dave,

I frequently use Ad Aware, CW Shredder, and Spybot Search and Destroy on my
workstation and my home machine, but I would never have considered running
them on a server for 2 reasons:
1. I don't browse much from the server, so the odds of it picking up
something nasty would be slim I would think.
2. Not only does it violate the user agreement, I really don't consider any
of those programs "enterprise" or server ready.

Do you think its safe to try running these on the server or should I be
looking for something ab it more 'refined'?

Our AV also runs a common configuration on all workstations. The server gets
the same client installed, however it obviously tweaked to not scan exchange
and whatnot. (InoculateIT) I had to run the only patch I could find from CA
to get it to work on the XP box. Maybe that is what is gumming up that one.
Since all machines scan incoming and outgoing files, I wonder if disabling
the AV on the XP box alone would help or if I need to disable it on the
server too.....

Anything is possible, but the Network wiring was all certified last year
after I installed it, so I wouldn't THINK that would be a problem. Our only
'hub' is the Netopia router, otherwise we use 2 HP2524 Switches, and they
don't show any (obvious) errors.

I'll start file searching\googling all the processes in the task manager,
Right out of the chute thought I see 2 instances of DLLHOST.EXE running.
Seems odd to have 2 of the same thing.....

I'll post back what I find.

Thanks.

"Dave Nickason [SBS MVP]" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:O0Fr3F9#DHA.2336@TK2MSFTNGP11.phx.gbl...
> A couple things come to mind. I would check your anti-virus software
> settings in case that could be the problem. Here, we have a single
> configuration for AV on all the workstations, so a change to that
> configuration effects every machine. You can try disabling the AV on one
> machine that's having the problem to quickly rule that in or out. Another
> thing that came right to mind is a hub, switch, or network cable problem.
> Although, the slow response on the server argues against that.
>
> I'd also check for something running that should not be. This would
include
> spyware, but also unnecessary background services and programs that are
> installed by legitimate apps. Run msconfig and look at the startup tab,
or
> the processes tab in Task Manager. Make sure you know what everything is,
> and that you want it to be running. (When I don't know what something is,
I
> just search for the filename. Usually you can tell by the file's location
> or properties. I ignore anything from MS - they're liable to be part of
the
> OS or a necessary service).
>
>
> "IBC" <spamityspam@spam.spam> wrote in message
> news:eNw1Nj8%23DHA.552@TK2MSFTNGP11.phx.gbl...
> > As noted here before, I have been trying to deploy an XP box on our
SBS2K
> > network with miserable success. When browsing network drives, the
machine
> > would just hang and hang. Sometimes browsing would be fast, other times
> the
> > machine would actually go into the "not responding" mode. So I figure
this
> > new XP box is killing me and my network.
> >
> > Low and behold, I'm on the server yesterday trying to view some files
and
> > while navigating through directories suddenly I get the hourglass and
have
> > to stand and wait around a minute before my LOCAL drives and directories
> > appear. What in blazes is going on here?! I'm at a record low as far as
> > critical errors go in the event logs, all the patches ahve been applied
> (and
> > I'm starting to suspect they may have been the culprit) and I', flat out
> at
> > a loss to figure out why I'm having such huge delays in browsing. Before
> all
> > the patches, the screens would pop as fast as I could double click, now
> > there is at least a minimal wait on almost all machines.
> >
> > To the best of my knowledge, the DNS is fine, but if somebody cares to
> > elaborate exactly what I should be looking at inthe DNS, I can double
> check
> > it.
> >
> > Thanks.
> >
> >
> >
>
>

Relevant Pages

  • RE: Event ID 529
    ... The source is clear - workstations that are not part of my ... SBS2003 domain share the same local network (it's a shared local network in ... This kind of issue may be caused by Application logon such as while Outlook ... is connecting to Exchange Server, or this is an automated dictionary attack ...
    (microsoft.public.windows.server.sbs)
  • Re: Adding PC to SBS 2000 domain
    ... There are three workstations that have been working fine for years. ... I have inherited this network and my knowledge is based/limited to SBS ... On the SBS 2000 server I created and new user account and new computer ...
    (microsoft.public.windows.server.sbs)
  • Re: Applying Personal Settings
    ... I wouldn't rule out that or another network ... ruling out the server NIC). ... Running ipconfig /all on the workstations confirms that they're getting DHCP ... with ipconfig results pointing gateway & dns ...
    (microsoft.public.windows.server.sbs)
  • RE: howto let asigned user login destinated workstation
    ... among them we have 5 workstations ... our give them the rights to login every workstation i.e. any ... may be really setting up your network for failure. ... resources on their own server with very limited access to anything else. ...
    (microsoft.public.windowsxp.general)
  • Re: Deleting duplicate service pack files
    ... until we went Server 2003 and XP workstations. ... I liked my network a lot ... The good thing is we use terminal services and remote desktop for our ...
    (microsoft.public.windowsxp.general)