Okay, I'm desperately behind in my certifications. I finished my MBA instead of upgrading my NT 4.0 certification 3 years ago. I didn't have much problem using Server 2000 without the training, but looks like 2003 may be a different beast. I don't have the money to take the classes for...
Well, it turned out to be an internal DNS issue on the old server. The new server registered in the domain but not the Exchange organization. Very weird. It said it was part of the same organization, but the two never communicated on the Exchange level.
We'll at least have to demote the...
Thanks PScottC. The 5.5 and 2000 are the same organization. I can us EXMerge to create the .pst file from 5.5, but it errors out trying to load into 2000. It says it can't read the list of recipients. I've given the administrator every right known to man.
The clients can't see the 2000...
No, it's not the DNS. I'm talking about creating mailboxes on Exchange 2000 and importing existing email with EXMerge. The mailbox doesn't show up until it has an email, but it won't have an email until I import the existing email and turn off the 5.5 server.
Okay, I know the mailbox doesn't really exist until it gets its first email. But how do you send it an email when you have another Exchange 5.5 server online? I'm trying to setup the new mailboxes to prepare for the EXMerge, and it doesn't think there are any users yet because the email goes...
We cut our outside people off because of the RPC attack. They have to go through the Internet client. Not as convenient, but a whole lot more secure. We're in the process of installing VPN, so it may be available in the future. But I don't want to live dangerously with that port open...
http://securityresponse.symantec.com/avcenter/venc/data/w32.blaster.worm.html
I believe this is the one attacking us. We closed the FTP port and a TCP port, don't remember which one. Installed SP4, plus some patches...not sure where we downloaded those from, though.
Good luck.
It's not an internal virus. It's an Internet attack. Go to syamntec.com to read about it. There's several patches, plus some ports to close on the firewall. We've been good for 36 hours.
BTW, sp4 install went off without a hitch.
SP4 install went fine but didn't fix the problem. Turns out it's an attack via Internet. See Symantec for more details. Closed off some ports on the firewall and installed a few patches. It's been 36 hours and all's still well.
I'm thinking it might be a virus launching a DOS attack. About 10 of our users have the W32.Mimmail.A@mm. NAV caught it on most machines and deleted it or quanrantined it. But I'm going to use their removal tool to try to undo the damage on the workstations. SP4 also apparently has the patch...
We're getting this error (event id 1000) logged every 5 minutes. It happened in the middle of the night when no one was logged in while the backup was running. Any ideas? It shut the backup down 3 consecutive nights before we got a clean backup last night.
Microsoft says install SP 4, but...
I'm a contract IT administrator for a small company like yours. What I do is go in every week or two and check the event viewers; make sure the backups run and restore files every so often for safety's sake; setup new users and disable old ones; help with workstations issues; plan new rollouts...
We're getting an RPC error every night during the backup which effectively shuts down the backup and Exchange. The server has to be hard rebooted (shut the power off) to recover. I'm going to manually kick off the backup early tonight to see if we can get a good backup (last one was Thursday)...
I'm a contractor for a small firm that up til now has used one wimpy little server for 20 users. Since the server is out of warranty, I've convinced them of the wisdom to add another server. The new server will be the PDC and Exchange server. The old server will remain the file and print...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.