[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 564
  • Last Modified:

OMA - IIS - NetBIOS

I have an Exchange FE/BE 2003 Service Pack 2 environment running on Windows Server 2003. I am experiencing OMA issues which led me to this Microsoft Support Article - http://support.microsoft.com/kb/898131 - this explain my issue exactly the only problem is I have an underscore in my server's NetBIOS name, and IIS will not allow me to enter this as a valid Host Header value. Does anyone have any ideas or suggestions around this (other than renaming my server)?

Thank you for any ideas you may have,

Jack
0
Jack_French
Asked:
Jack_French
  • 4
  • 4
1 Solution
 
SembeeCommented:
Are you using SSL?
If not, why not?

If you were using SSL then this wouldn't be an issue as you cannot use host headers with SSL.

Which server has the underscore in it? The frontend or the backend?

Simon.
0
 
Jack_FrenchAuthor Commented:
Yes, I am using SSL on the front end, and both the FE and the BE have an underscore.  Why do you feel this would not be an issue?

Jack
0
 
SembeeCommented:
You can't use host headers with SSL.
The KB article that you have pointed to (Which is all that I have to go on) indicates that the problem is caused by host headers.
If you are using host headers then remove them - as they are of little use.

Simon.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Jack_FrenchAuthor Commented:
I am not using Host Headers, the KB article I understood as telling me I needed to add the NetBIOS name to a newly created host header.

• The host header for the OMA Web site does not include the NetBIOS name of the Exchange 2003 computer.  
The incoming requests are made to the /OMA virtual directory on the Exchange 2003 computer. These requests try to communicate by using the NetBIOS name of the /Exchange virtual directory. If the host header for the OMA Web site does not include the NetBIOS name, you receive the message that is mentioned in the Symptoms section.

thoughts?

jack
0
 
SembeeCommented:
You are looking at the solution, not the problem.

You don't need to use host headers to get OMA to work. I have OMA on at least a dozen servers and not one of them are using host headers. Host headers are not compatible with SSL, and as all of my deployments use SSL, it isn't something I have had to look at.

The article contains two conditions - the use of host headers, and the missing host header. If you are not using host headers at all then you fail to meet those conditions.

Simon.
0
 
Jack_FrenchAuthor Commented:
Then that leads me to the obvious next question. Have you received that error as stated in the KB article before?

Also, are you using Forms Based Authen. with SSL, in a FE/BE scenario anywhere and having issues with Active Sync or OMA?

Jack
0
 
SembeeCommented:
FE/BE scenarios with OMA/EAS, SSL and FBA are usually trouble free. The problems come in single server deployments. I have three or four that are working fine.

If you are getting the error in OMA, then that is usually associated with an error in the event viewer of the server at roughly the same time.

Simon.
0
 
Jack_FrenchAuthor Commented:
I have looked, I will dig deeper and possibly post again once I have a better handle on it. Thank you for your time.

Jack
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now