2000SBS unable to be viewed by network clients

We have a Windows 2000 Small Business Server with SP3 that was recently formatted and reinstalled.
All seems fine with the system itself, however when it was put back onto the customer site, none of the pcs can view it via Network Neighbourhood.
It can be pinged my name and Ip address.
All clients (25 CAL's) can log in as normal, but programs and printers installed on the server can not be accessed from any of the client pcs (mostly Win 2K, few 98 and few XP)
Has anybody got any ideas?
LVL 1
total123Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If it was reformated and reinstalled then all of the SID's (Security ID's) were wiped out.  You need to re-attach the workstations using the connection disk.  Basically reinstalling your entire network.

Also, you should be running SP4 on your server.

Jeff
TechSoEasy
0
total123Author Commented:
Cheers Jeff,

The server is currently working through all the updates as we speak.

All the pcs were connected using the Network ID wizard, is this not enough or shall i use something else?
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Perhaps I jumped to conclusions... did you restore the server's system state (ie, Active Directory) before reconnecting it to the Network?  Or did you rebuild AD?

Jeff
TechSoEasy
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

total123Author Commented:
We rebuilt the AD.
problem i have noticed is that if i don't log the server on i can get the pc's to see the server and it acts fine. when i login the server drops off of the network, only to the point where i can't see it. I can still ping it thou.
I have ran adaware, antivirus.
I have also found things on admin share's not being available and that hasn't worked.
I have tried login on as another user and that does the same. There isn't anything in the startup folder or in the reg under runservices apart from MS update.
If i log the server off after being logged on it still plays up. Needs a complete reboot to get it work properly then left to stand on the log on screen

cheer
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Since you rebuilt the AD, the client workstations should have been removed from the domain and readded using a newly created setup disk.

Jeff
TechSoEasy
0
total123Author Commented:
We have added the workstations using the network wizard on the workstations. We shouldn't need to use a disk should we. Never have done before
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, otherwise you need to configure all the clients manually:  http://support.microsoft.com/kb/316418

Jeff
TechSoEasy
0
total123Author Commented:
already done it that way. I have a fairly good idea on networking. and have tried various other ways of connecting it.
Any other idea's ?
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If you restored your System State / Active Directory, etc. before you had applied the same service packs and patches (Windows Server 2000 SP4, and SBS SP1a http://support.microsoft.com/kb/326914) then you could experience this type of problem.  Honestly, this is not an area I'm very well versed in, but every disaster recovery method I've seen has always stated that you need to reinstall the server to it's exact operational state before restoring AD and data.

If that's not what's causing the problem.. it could be due to automatic updates on the client side the week before you posted this question: http://support.microsoft.com/kb/917767

Beyond that, you will need to scour the event logs and see what is actually NOT happening.

Jeff
TechSoEasy
0
total123Author Commented:
what i have noticed is in the registry i have under
hkey_local_machine\software\microsoft\windows\currentversion\run and runservice

there is a link :-
name -                                           data
microsoft update adbpro        -      msupdate33.exe
microsoft windows update 32 -      winupdate32.exe

when i delete the adbpro line from the reg it regens itself. yet the winupdate32.exe doesn't.
i'm assuming that the winupdate32.exe is part of normal ms update ?
i don't no what msupdate33.exe does or what adbpro is.
any ideas
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, probably not a good assumption because that's what virus writers expect.  What Anti-virus are you running on your system?

Jeff
TechSoEasy
0
total123Author Commented:
Symantec Norton Antivirus Corp edit
0
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, I'd run these and see what they says about those files:  www.pandasoftware.com/activescan and www.kaspersky.com/virusscanner

Jeff
TechSoEasy
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
total123Author Commented:
it was a spybot virus in the end
cheers jeff
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.