If you attempt to connect to and send mail via command line to your Exchange Server, you may see the following error after you end the data section of the operation.
451 4.7.0 Temporary server error. Please try again later. PRX5
Solution 451 4.7.1 Error
Log into Exchange Amin Center > Mail Flow > Receive Connectors > Default Frontend {Server-Name} > Edit > Scope > Select the IPV4 entry (Either Remove it and ad a new one or edit it)
Specify the IP address you want to use.
So, it should look like this > Save > Exit Exchange Management.
Open Notepad (Note: you need to run as administrator). Navigate to C:\Windows 32\Drivers\Etc locate the hosts file (If you can’t see it change the option to “All Files“
At the bottom of the file enter the IP hostname and FQDN of the server then save and exit.
Then restart the Exchange Transport Service.
Related Articles, References, Credits, or External Links
I hadn’t seen this myself but it was asked in a forum the other day so I replicated it on the test bench.
You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
or
You were not connected because a duplicate name exists on the network. If joining a domain, go to System in Control Panel to change the computer name and try again. If joining a workgroup choose another workgroup name.
Solution
Those ‘recommendations’ are NOT what you should be doing to fix this problem!
This is happening because a resource you are trying to connect to (another PC or Server) is addressable by two different names. As you can see below if i ping the server name ‘dc1b’ and ‘files’, the same IP address responds.
In my case that’s because I’ve got a CNAME entry in my DNS for files, that points to the server name dc1b.
Note: If you have two Host A records, I would recommend deleting the additional one and using a CNAME entry instead.
Note2: If the client exhibiting the problem has multiple entries in its ‘hosts’ file that point to the same IP you can also see this problem.
Fix
1. On the server/computer you are connecting TO > Windows Key +R > regedit {Enter}.
Create a new DWORD Value (or 32 bit DWORD if you are on a newer OS).
3. Call the value DisableStrictNameChecking and set its value to decimal 1 (one).
4. Then either reboot the server or Windows Key +R > services.msc {enter} > Locate the Server service > Restart.
5. At this point your client should be able to connect via either name.
It’s Still Not Working
In some cases you need to set an alias SPN (Service Principle Name). If you are still running Server 2003 Download and install this update first (or it wont know what setspn.exe is).
Syntax
[box]
setspn -A host/<Alias Name><Host Name>
setspn -A host/<Alias FQDN> <Host Name>
e.g.
setspn -A host/files dc1b
setspn -A host/files.domainb.com dc1b
[/box]
Related Articles, References, Credits, or External Links
Windows did this with Windows 7 (and Vista). If you attempt to edit the hosts file you will see the following.
You don’t have permission to save in this location. Contact the administrator to obtain permission. Would you like to save in the My Documents folder instead?
Solution
1. You could run an admin command window, and use the EDIT command, but Notepad is easier. Open the Apps page (Windows Key+Q) > Locate Notepad and right click it > Run as Administrator.
Note: YES Even if you are logged in as an administrator.
2. Now you can open the hosts file (make sure you change the file type to all files or notepad wont see it!). And you can then edit the file and save the changes.
Related Articles, References, Credits, or External Links
