Search results for query: *

Please tell us a bit more about your network and your implementation of Exchange... If there are no third party s/w to interfere, the you could check: *problems with disk space? Check all drives on your Exchange server. *Are you running 10base-t? *Does the slowness happen to everyone on the...

Yes, we have TS on our clustered servers (not the server, but the '2 user' version). Works well, there are no issues with it on Exchange 2000 or on clustered servers. I didn't install it on our cluster, but I reckon its just a case of installing Terminal Services on ALL nodes of the cluster...

Unless these external servers are recognised by you, this may be spam. You can probably tell - some of the queues will have improbable names like msk.ru Spam email may arrive at your server where they guess at a user being at your server. Your server tries to send a NDR, but being spam, the...

I didn't think this was possible. An Exchange 2000 mailbox is 'just' an object to AD, that has to be associated with an account. The mailbox doesn't have an address without the AD mailbox enabled account. But I'm often wrong! You don't say why you need this mailbox. I wondered if you could...

I don't think that backing up and restoring would work. Exchange 2000 is very fussy about what it wil restore to. Back in the day, you could name a new 5.5 the same as the old 5.5 and that would be about it (domain accounts aside). With Exchange 2000, a lot of info about this server is written...

The new server should definitely have the same name as the old server. Otherwise you will find that your mailstores will refuse to mount. To that end, there should be no need to delete any computer accounts. If the disk structure is the same when you rebuild the server, then you shouldn't...

That's a lot to ask! ;-) But I'll kick the discussion off by saying that a first task should be to make sure that DNS is working on your proposed mail server. You need to be sure that your Internal DNS servers can resolve your network queries fine, but also that it can hand over external...

If you check the Services on your Exchange Server, you can see the dependancies for each service. You would then shut them down in reverse order, so that the System Attendant is the last to shut down. The order you already have for 5.5 looks like it should work for 2000...... RobbyB

And what if it gets lost?

That's not a dumb question. When you telnet, you'll telnet in on port 25. This port must already be open otherwise other mailservers won't be able to send you mail. You won't need to know your firewall address. From home, you'll type in something like telnet yourmailserver.domain.com 25...

OK. So it seems that your server is OK. Which is good! How long has that message been returning to your queues? I must admit I'm not sure at this stage how it got into your system. That it ends up in BadMail is normal as I'll bet that hornyxgsmvycs@mail.de isn't a valid address. At a guess...

Good Luck - let us know!

Mail gets transmitted along port 25. SMTP protocol chatters up and down port 25. I reckon something along the lines of the below should return Exchange 2000 back to the default: ======================= For your Default SMTP Virtual Server, Under relay, select 'Only the list below' and check...

I'll try: Spammers are always looking for a way to get extra bandwidth without being detected. If they can connect to your server, they will send their mail through your server. This is not good because it increases traffic dramatically for you, and it looks as if you are the purveyor of the...

Sorry, just a term for a server that's open for spamming. You should try to telnet to your server, and then see if you are able to send a message from your server to someone else.

No, that's OK. As long as your email domain is known to the outside world in DNS. This would mean that you have had to be specific and define your domain to stuff like your SMTP Connector and your Recipient Policies. But all is well because you are receiving messages OK?

Could be like you are being relayed off? It's from <> - typical spamming. It's on it's way to some funny address. Hmmm. Ordinarily, your system should reject (because the domain is not your doamin) it b4 it gets to be queuing. Messages can go to BadMail when the system doesn't know where to...

Had something a little like this once. It was intermittent, and with well known domains at that (but only one or two). Turned out that if a message routed out via a certain server on its hops, then that particular server would reject the mail. We found this out by looking at where the NDR...

Are you still using the default port 80 for OWA? If not, then your user may have a firewall that is blocking the new port? Ask your user if he is using any software firewalls like ZoneAlarm. He may have too restrictive a setting that isn't allowing authentication to happen. He/she may have an...

1000 apologies. I misinterpreted that. It won't be a profile problem and I'm sorry for leading down this path. For the entries in your Application Log, a MS article suggests that you should rebuild the Recipient Update Service. The article might not describe exactly what's happened to your...