| Author |
Message |
Tony Su
Guest
|
 Posted:
Wed Jan 19, 2005 5:37 am Post subject:
LCS 2003 - Configuring TLS routing error |
|
|
Am following the LCS 2003 EOUS document,
On page 6, "The Routing Tab" I have configured all but when I click OK, I
receive the following error
The user name is not valid. Enter a valid user name.
The configured username is
*@su-networking.com
where su-networking.com is my public FQDN and is fully supported as an email
alias in the domain (Exchange default recipient policy).
Suggestion?
TIA,
--
Tony Su
www.su-networking.com
ISA
SBS
Enterprise Mobile Solutions Architect |
|
| Back to top |
|
 |
Bob Christian
Guest
|
| Posted:
Wed Jan 19, 2005 6:48 am Post subject:
Re: LCS 2003 - Configuring TLS routing error |
|
|
Is it configured at the forest level for LCS? Right-click on your forest
name and see if it is in your list of supported domains. If not, click the
add button and add it. See if that clears it up.
Bob
"Tony Su" <TonySu@discussions.microsoft.com> wrote in message
news:EC832028-CE68-46B8-B754-69003F082673@microsoft.com...
| Quote: | Am following the LCS 2003 EOUS document,
On page 6, "The Routing Tab" I have configured all but when I click OK, I
receive the following error
The user name is not valid. Enter a valid user name.
The configured username is
*@su-networking.com
where su-networking.com is my public FQDN and is fully supported as an
email
alias in the domain (Exchange default recipient policy).
Suggestion?
TIA,
--
Tony Su
www.su-networking.com
ISA
SBS
Enterprise Mobile Solutions Architect |
|
|
| Back to top |
|
|
Tony Su
Guest
|
| Posted:
Wed Jan 19, 2005 6:48 am Post subject:
Re: LCS 2003 - Configuring TLS routing error |
|
|
Thx Bob,
As is usual the Windows Domain and internal name resolution is different
than external name resolution and when I inspect the AD Forest properties, I
see the Windows Domain (LAN) name only.
What I'm trying to do is enable external name resolution (Remote User on the
Internet) to a LAN resource (LCS).
So, currently there is no problem if the User connects from a LAN Host to
the LCS because as expected LAN Name Resolution is fine.
On the other hand, when the User connects from the Internet, one of two
situations exists...
- The Windows Domain name if something like dotLocal will be unroutable
- The Windows Domain name if a subdomain of the public domain may be
routable but is normally unpublished or not preferred.
Are you saying that adding the domain name as an UPN suffix might solve this?
Thx,
Tony
"Bob Christian" wrote:
| Quote: | Is it configured at the forest level for LCS? Right-click on your forest
name and see if it is in your list of supported domains. If not, click the
add button and add it. See if that clears it up.
Bob
"Tony Su" <TonySu@discussions.microsoft.com> wrote in message
news:EC832028-CE68-46B8-B754-69003F082673@microsoft.com...
Am following the LCS 2003 EOUS document,
On page 6, "The Routing Tab" I have configured all but when I click OK, I
receive the following error
The user name is not valid. Enter a valid user name.
The configured username is
*@su-networking.com
where su-networking.com is my public FQDN and is fully supported as an
email
alias in the domain (Exchange default recipient policy).
Suggestion?
TIA,
--
Tony Su
www.su-networking.com
ISA
SBS
Enterprise Mobile Solutions Architect
|
|
|
| Back to top |
|
|
Tony Su
Guest
|
| Posted:
Thu Jan 20, 2005 12:13 am Post subject:
Re: LCS 2003 - Configuring TLS routing error |
|
|
Bob,
Thx for the suggestion but it didn't work.
LCS works fine using LAN name resolution in the LAN(Windows Domain and FQDN
alias name).
As I posted in my other most recent post, am trying to configure support for
WAN name resolution using the public FQDN.
Of course, the public domain was not automatically a supported Domain, so I
added it as a UPN suffix, but with no effect.
Tony Su
"Bob Christian" wrote:
| Quote: | Is it configured at the forest level for LCS? Right-click on your forest
name and see if it is in your list of supported domains. If not, click the
add button and add it. See if that clears it up.
Bob
"Tony Su" <TonySu@discussions.microsoft.com> wrote in message
news:EC832028-CE68-46B8-B754-69003F082673@microsoft.com...
Am following the LCS 2003 EOUS document,
On page 6, "The Routing Tab" I have configured all but when I click OK, I
receive the following error
The user name is not valid. Enter a valid user name.
The configured username is
*@su-networking.com
where su-networking.com is my public FQDN and is fully supported as an
email
alias in the domain (Exchange default recipient policy).
Suggestion?
TIA,
--
Tony Su
www.su-networking.com
ISA
SBS
Enterprise Mobile Solutions Architect
|
|
|
| Back to top |
|
|
Tony Su
Guest
|
| Posted:
Thu Jan 20, 2005 4:13 am Post subject:
Re: LCS 2003 - Configuring TLS routing error |
|
|
This issue resolved.
Thx Bob for the suggestion, the additional step I didn't implement was to
configure the User account to logon using the alternative FQDN instead of the
default Windows Domain FQDN.
On to the next issue...
Thx,
Tony
"Tony Su" wrote:
| Quote: | Bob,
Thx for the suggestion but it didn't work.
LCS works fine using LAN name resolution in the LAN(Windows Domain and FQDN
alias name).
As I posted in my other most recent post, am trying to configure support for
WAN name resolution using the public FQDN.
Of course, the public domain was not automatically a supported Domain, so I
added it as a UPN suffix, but with no effect.
Tony Su
"Bob Christian" wrote:
Is it configured at the forest level for LCS? Right-click on your forest
name and see if it is in your list of supported domains. If not, click the
add button and add it. See if that clears it up.
Bob
"Tony Su" <TonySu@discussions.microsoft.com> wrote in message
news:EC832028-CE68-46B8-B754-69003F082673@microsoft.com...
Am following the LCS 2003 EOUS document,
On page 6, "The Routing Tab" I have configured all but when I click OK, I
receive the following error
The user name is not valid. Enter a valid user name.
The configured username is
*@su-networking.com
where su-networking.com is my public FQDN and is fully supported as an
email
alias in the domain (Exchange default recipient policy).
Suggestion?
TIA,
--
Tony Su
www.su-networking.com
ISA
SBS
Enterprise Mobile Solutions Architect
|
|
|
| Back to top |
|
|
Bob Christian
Guest
|
| Posted:
Thu Jan 20, 2005 9:58 pm Post subject:
Re: LCS 2003 - Configuring TLS routing error |
|
|
Thanks for the follow-up information!
"Tony Su" <TonySu@discussions.microsoft.com> wrote in message
news:5B17ABF8-5830-4551-B532-4F22B4AA62FE@microsoft.com...
| Quote: | This issue resolved.
Thx Bob for the suggestion, the additional step I didn't implement was to
configure the User account to logon using the alternative FQDN instead of
the
default Windows Domain FQDN.
On to the next issue...
Thx,
Tony
"Tony Su" wrote:
Bob,
Thx for the suggestion but it didn't work.
LCS works fine using LAN name resolution in the LAN(Windows Domain and
FQDN
alias name).
As I posted in my other most recent post, am trying to configure support
for
WAN name resolution using the public FQDN.
Of course, the public domain was not automatically a supported Domain,
so I
added it as a UPN suffix, but with no effect.
Tony Su
"Bob Christian" wrote:
Is it configured at the forest level for LCS? Right-click on your
forest
name and see if it is in your list of supported domains. If not,
click the
add button and add it. See if that clears it up.
Bob
"Tony Su" <TonySu@discussions.microsoft.com> wrote in message
news:EC832028-CE68-46B8-B754-69003F082673@microsoft.com...
Am following the LCS 2003 EOUS document,
On page 6, "The Routing Tab" I have configured all but when I click
OK, I
receive the following error
The user name is not valid. Enter a valid user name.
The configured username is
*@su-networking.com
where su-networking.com is my public FQDN and is fully supported as
an
email
alias in the domain (Exchange default recipient policy).
Suggestion?
TIA,
--
Tony Su
www.su-networking.com
ISA
SBS
Enterprise Mobile Solutions Architect
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in