PHWinfo - Afficher un message - IBM MQ series 5.1 for win NT failing on 2003 server,

14/07/2006, 15h32

"Jetender" <jetender.ghuman@honeywell.com> wrote in message
news:O7uawUwpGHA.4988@TK2MSFTNGP04.phx.gbl...
>
>
> Hi ,
> I am trying to configure IBM MQ series 5.1 for win NT on a windows 2003
> server machine. The Installtion of MQseries was clean , however when i try
> to create a Q manager , either through MQExplorer or using crtmqm from
> the
> prompt , the command does not execute completely and remains in some sort
> of
> a loop.
> I had a similar problem with a 2000(Prof )machine but that was because the
> domain controller had be turned off and the machine was not able to
> authenticate properly with the domain controller.

Although you might get lucky and find someone here with
expertise in MQ, this is a DNS list for Microsoft so it isn't
as likely as if you posted in an IBM or (better) MQ specific
list.

No one here will get very excited about an off-topic (but
well intentioned like this) post but you just aren't very likely
to get much unless it is a DNS problem which IS POSSIBLE.

> The 2003 server is under the same domain controller as the win 2000
> machine,
> which has started working fine after the domain controller was started.

We must assume you mean "in the same domain".

> In the 2003 machine's event log, there is an error by NETLOGON that it was
> unable to it was unable to establish a "secure session" with the domain
> controller.

This is frequently a (client side) DNS error, but the actual
message is due to the computer failing to authenticate itself
with the domain. (Computers authenticat themselves before
any user can logon to the domain.)

> I have tried removing it from the domain controller and adding
> it again but this error message persists.

Random tests seldom work. Win2000+ domain machines almost never
need to be re-added to the domain (that was a common practice
in NT days). [If a computer account gets hosed in Win2000+ domain,
just reset the account by right-clicking in AD Users/Computers or
using one of the command line tools: NLTest, DSMod, NetDom.]

> What needs to be done to ensure
> that a "secure session" gets established?

The most likely problem if you network and DC is basically
operation is that you don't have the DNS correct. If it is a CLIENT
side problem then likely it is due to specifying the WRONG or
MULTIPLE 'sets' of DNS server on the client's NIC->IP property.

All internal DNS clients must specify STRICTLY the internal
DNS set which can resolve ALL names needed by the client.

That it, you must NOT mix internal and external DNS servers
on the client NIC settings (which is a very common mistake.)

You can run NetDiag on the client and DCDiag on the DCs to
test your configuration.

> The domain controller is a windows 2000 server .

Will it pass DCDiag (in Support Tools on the CDROM)

> Is MQ series 5.1 for NT compatible with 2003 server ? if yes , what might
> i
> be missing out?

???

> Any on this will be greatly appreciated.

We'll try but if it isn't a pure authentication or DNS issue
then likely MQ expertise will be needed.

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

> Jeet.
>
>

14/07/2006, 15h32	#2
Herb Martin Messages: n/a Hébergeur:	Re: IBM MQ series 5.1 for win NT failing on 2003 server, "Jetender" <jetender.ghuman@honeywell.com> wrote in message news:O7uawUwpGHA.4988@TK2MSFTNGP04.phx.gbl... > > > Hi , > I am trying to configure IBM MQ series 5.1 for win NT on a windows 2003 > server machine. The Installtion of MQseries was clean , however when i try > to create a Q manager , either through MQExplorer or using crtmqm from > the > prompt , the command does not execute completely and remains in some sort > of > a loop. > I had a similar problem with a 2000(Prof )machine but that was because the > domain controller had be turned off and the machine was not able to > authenticate properly with the domain controller. Although you might get lucky and find someone here with expertise in MQ, this is a DNS list for Microsoft so it isn't as likely as if you posted in an IBM or (better) MQ specific list. No one here will get very excited about an off-topic (but well intentioned like this) post but you just aren't very likely to get much unless it is a DNS problem which IS POSSIBLE. > The 2003 server is under the same domain controller as the win 2000 > machine, > which has started working fine after the domain controller was started. We must assume you mean "in the same domain". > In the 2003 machine's event log, there is an error by NETLOGON that it was > unable to it was unable to establish a "secure session" with the domain > controller. This is frequently a (client side) DNS error, but the actual message is due to the computer failing to authenticate itself with the domain. (Computers authenticat themselves before any user can logon to the domain.) > I have tried removing it from the domain controller and adding > it again but this error message persists. Random tests seldom work. Win2000+ domain machines almost never need to be re-added to the domain (that was a common practice in NT days). [If a computer account gets hosed in Win2000+ domain, just reset the account by right-clicking in AD Users/Computers or using one of the command line tools: NLTest, DSMod, NetDom.] > What needs to be done to ensure > that a "secure session" gets established? The most likely problem if you network and DC is basically operation is that you don't have the DNS correct. If it is a CLIENT side problem then likely it is due to specifying the WRONG or MULTIPLE 'sets' of DNS server on the client's NIC->IP property. All internal DNS clients must specify STRICTLY the internal DNS set which can resolve ALL names needed by the client. That it, you must NOT mix internal and external DNS servers on the client NIC settings (which is a very common mistake.) You can run NetDiag on the client and DCDiag on the DCs to test your configuration. > The domain controller is a windows 2000 server . Will it pass DCDiag (in Support Tools on the CDROM) > Is MQ series 5.1 for NT compatible with 2003 server ? if yes , what might > i > be missing out? ??? > Any on this will be greatly appreciated. We'll try but if it isn't a pure authentication or DNS issue then likely MQ expertise will be needed. -- Herb Martin, MCSE, MVP Accelerated MCSE http://www.LearnQuick.Com [phone number on web site] > Jeet. > >