Recent content by danielwestendorf

Thanks TechyMcSe2k! It was pointing at the Operation Master by default. Changing it to Any Domain Controller sped things up!

Thanks for the replies and ideas. All DC's are GC servers. Sites are set up, and the DC's are assigned to their sites. There are no resources being pulled. The only only GPO I have set up currently changes some power and display settings. Even if there were resources being pulled, it wouldn't...

Hi there, Have two sites, connected by a slow but stable site-to-site VPN. Each site has two Domain Controllers. The Main site, which holds all of the Active Directory FSMO/OM roles is fine and works great. The remote site, which has two DC's, experiences very slow client logins, particularly...

That's what I needed, thanks!

Hello All, We've recently upgraded our CP firewall, and our point-to-point h.323 trunks between to IPO units aren't working. This is a Checkpoint issue for sure, but they suggested turning TTS or Time To Service off on the IPO units to try and resolve the issue. I'm either blind, or these...

Hello all, I had a working installation under R61, with some static nat rules. Everything worked great, but the hardware was getting old, so I decided to upgrade to a new system and an R65 release. The export/upgrade seems to have gone fine, no problems there. Outbound access is working fine...

If you end up dragging any contents of OST files into your new Exchange mailboxes via Outlook, make sure you give them a few minutes, even if it says the action is 100% done. I had a new client who the previous admin never made a backup, and the server blew up. I ended up building a new one and...

Great to hear that the problem isn't with Exchange as we thought. Too bad you had to do all the leg work for the developers though :( I'll keep my fingers crossed for you.

Where are you getting the NDR from, Exchange or the SMTP gateway? I would be that your linux box is rejecting the email because it doesn't think it is a real user. Do you have the same results for every mail enabled group, or just this specific one?

I have found that most consumer level internet packages block port 25. They make you upgrade to a business level package to have full access to port 25.

Sounds like everything with Exchange is working then, probably something screwy with the desktop client. Can you create a new Outlook profile and configure it for the same user and see if that resolves the issue?

Is the user's mailbox over the size limit? Do you have the rule restricting a user from sending emails when their mailbox is over a certain size limit?

Are you getting these results from inside or outside the network? Whenever I run into these types of problems, I eliminate NAT/Port Forwarding/Firewalling from the equation. This does sound like a DNS issue though. If it is responding via IP, but not hostname, that is the first thing I would...

Okay, if you can ping mymailserver.mydomain.local, is that the hostname you're using in the web app? Can you telnet from your webapp box to exchange using the FQDN and attempt to send an email to an external account? In the Exchange System Manager> YourServer>Protocols>SMTP>Default SMTP...

Depending on your setup, probably not. MX records are so a system can go "Who handles mail for this domain?" Since you already know that, and aren't querying that dynamically, no. From the same box as your webapp, can you ping your exchange server via the hostname? You are using the FQDN right...