cancel
Showing results for 
Search instead for 
Did you mean: 
ericklans
Level 9

Problem with connecting MWG 7.x to Windows AD

We have webagteway 7.2.0.1.0 and Windows 2008 server with AD, both teared in vmware ESXi.

We trying to add with Windows Domain Membership at Configuration.

Joining Domain.jpg

But it's falied. Status is red.

WinDomMember.jpg

But we can see that the MWG is added to DC as computer:

MWGinDC.jpg

Please, help us to solve this problem. We cann't understand where is problem.

0 Kudos
6 Replies
ivan.s
Level 7

Re: Problem with connecting MWG 7.x to Windows AD

try to use short(NTLM) domain name(MYDOMAIN instead mydomain.com)

0 Kudos
McAfee Employee

Re: Problem with connecting MWG 7.x to Windows AD

I second this notion!

This is the recomended method. It is related to what is described here:

https://kc.mcafee.com/corporate/index?page=content&id=KB72822

~jon

0 Kudos
ericklans
Level 9

Re: Problem with connecting MWG 7.x to Windows AD

Перепробовал, не получается.

0 Kudos
McAfee Employee

Re: Problem with connecting MWG 7.x to Windows AD

English helps, but I can google translate.

Check your DNS, make sure the MWG can forward resolve the DC's name, as well as backward:

nslookup dc.yourdomain.local

nslookup x.x.x.x (dc.yourdomain.local)

You can do this from the CLI or under Troubleshooting > Network tools.

If the MWG cannot do this, then you will have issues.

Best,

Jon

akill
Level 9

Re: Problem with connecting MWG 7.x to Windows AD

you can edit the host file of the webgateway also if you dont have the internal dns on the MWG....

Configuration->file editor->hosts to edit the webgateway host file

ash_s
Level 7

Re: Problem with connecting MWG 7.x to Windows AD

Had similar issues.

when I removed '-'   (dashes)  from the server name (webgateway) it worked. i.e. renamed 'wg-server-1'  to 'wgserver1' and it worked.

I had the domain and Dcs in host file

eg.

n.n.n.n   Mydomain   DC1.mydomain.com

n2.n2.n2.n2   Mydomain  DC2.mydomain.com

Also use the name of the (webgateway) server itself when registering with AD. i.e. Don't use "webgateway" in AD config when the actual server name is "Proxy1".

Message was edited by: ash_s on 13/07/12 07:32:41 CDT