Tag Archives: alias

Windows Accessing a Share Error – “You were not connected because a duplicate name exists on the network”

Posted on by

KB ID 0000991 

Problem

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}.

2. Navigate to:

[box]HKEY_LOCA_MACHINE > SYSTEM > CurrentControlSet > Services > lanmanserver > Parameters[/box]

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

NA

Exchange Mailbox Move Error”Property expression isn’t valid”

Posted on by

KB ID 0000238 

Problem

Seen when attempting to move a mailbox.

Error:
Property expression “username” isn’t valid. Valid values are: Strings that include ‘@’ where ‘@’ cannot be the last character

During the move.

When the move process has finished.

Note: If your error says

“Property expression “username” isn’t valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.” Then click here.

Solution

This is caused because for that particular user there is no entry in the “domain” attribute on the user object.

1. Log onto a domain controller.

2. Start > Administrative tools> Active Directory Users and Computers.

3. Locate the user > Right click > Properties > Account Tab.

4. Put the domain name in the domain section. (use the drop down).

5. Now when you try and move the mailbox you will see this error instead.

Error:
The queue in ‘Mailbox Database xxxxxxxx’ database already contains a move request for {username}. While AD reports the mailbox as not being moved. It is possible that someone created the move request recently……..{text removed}…If you believe this to be an abandoned move request you can remove it by running ‘Remove-Move-Request -MoveRequestQueue ‘Mailbox Database xxxxxxx -MailboxGuid xxxxx-xxxxx-xxxxx-xx-xxx

6. Press CTRL+C to copy all that to the clipboard.

7. Open Notepad > Press CTRL+V to paste the text in.

8. Locate the command its asking you to run.

9. Launch the Exchange Management Shell > Paste in the command.

10. Now when you try and move the mailbox it should be OK.

 

Related Articles, References, Credits, or External Links

NA

Exchange 2010 Mailbox Move Error “Property expression isn’t valid”

Posted on by

KB ID 0000430 

Problem

Seen while trying to execute a move mailbox move.

Error:
Property expression “username” isn’t valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.

Note: If your error says..

“Property expression “username” isn’t valid. Valid values are: Strings that include ‘@’ where ‘@’ cannot be the last character” click here

Solution

1. On the Exchange server, launch the Exchange Management Console > Below Recipient Configuration > Mailbox, locate the user/mailbox that you have a problem with > Right click > Properties.

2. On the General tab > Locate the users “Alias” > delete anything that isn’t A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~

3. Once you have changed > Apply > Try and move the mailbox again (Note: You may need to delete the move request, in the “Move Request” section.)

 

Related Articles, References, Credits, or External Links

NA

Update Global Address List Error “WARNING: The recipient “xxxxxMicrosoft Exchange System Objects/xxxxx” is invalid and couldn’t be updated

Posted on by

KB ID 0000516 

Problem

Seen when manually trying to update the Global Address List, with the following powershell command:

[box]Update-GlobalAddressList -identity ‘Default Global Address List'[/box]

Error: WARNING: The recipient “{your domain name}/Microsoft Exchange System Objects/{A Public Folder Name}” is invalid and couldn’t be updated.

or

Error: WARNING: The recipient “{your domain name}/Microsoft Exchange System Objects/OAB Version 2” is invalid and couldn’t be updated. WARNING: The recipient “{your domain name}/Microsoft Exchange System Objects/OAB Version 3a” is invalid and couldn’t be updated. WARNING: The recipient “{your domain name}/Microsoft Exchange System Objects/Offline Address Book – /o={your domain name}V/cn=addrlists/cn=oabs/cn=123” is invalid and couldn’t be updated.

This is commonly seen when an Exchange environment has been migrated from Exchange 2003. And it happens because the Alias names for the particular public folders have spaces in them (or a character that Exchange does not like).

Solution

1. On your Exchange 2007/2010 Server Launch the Exchange Management Console > Toolbox > Public Folder Management Console.

2. If you error is about OAB / Address books skip to step 5, If it’s to do with a public folder that your organisation has created, expand default public folders and locate one of them that’s causing the error (In the example above I’ve highlighted one called “1045 – Greengairs” > Select its parent > Then select it (in the central pane) and open its properties.

3. As soon as you select the “Exchange General” tab, you will get an error popup which indicates the problem, there is a problem with the Alias name, in this example there’s spaces in it remove them.

Error: The properties on this object have invalid data. If you click OK, default values will be used instead and will be saved if you do not change them before hitting Apply or OK on the property page. If you click cancel, the object will be displayed read-only and corrupted values will be retained.

4. Once removed apply the changes.

5. If your error references OAB or address books, expand system Public Folders > OFFLINE ADDRESS BOOK > Check the properties of ALL its child objects > and on the Exchange General tab remove any spaces or unusual characters.

 

Related Articles, References, Credits, or External Links

NA