OK, I've half cracked this.

I loaded up Ethereal and watched traffic between my PC and the DNS server.
When I tried to add a new printer driver profile, my PC queried the DNS
server for the A record of the virtual server that runs the NDPS service.
The DNS server shrugged its shoulders as it didn't have a record for it.

I've added one and now I get further, but after a few second the error

The remote procedure call failed.
Error group: Windows
Erros code: 1726

Time to hit the packet trace / knowledgebase again....

Innit great when things work like they should?!?!?!?

"Iain McLaren" <iain.mclaren@scott-moncrieff.moc> wrote in message
news:rkDWc.3501$Zi4.153@prv-forum2.provo.novell.com...
> Hi,
>
> I saw your post just after I'd posted mine (that's always the way).
>
> I've tried what Suzanne Miles suggested - putting the servers in the hosts
> file - but got the same result.
>
> I'm fairly convinced it's something to do with iManager trying to verify
> that server.domain.com has IP address w.x.y.z and IP address w.x.y.z is
> known as server.domain.com.
>
> Why it has to do this I don't know...
>
> "Andrew" <atrofimo@gisbornesc.vic.edu.au> wrote in message
> news:cxzWc.3292$Zi4.1614@prv-forum2.provo.novell.com...
> > Iain,
> >
> > I have the same problem with the same error code and couldn't work it

out
> so
> > far ( see my message from 17.08 below ). I think it has something to do

> with
> > my PTR's ..
> >
> > Andrew
> >
> > "Iain McLaren" <iain.mclaren@scott-moncrieff.moc> wrote in message
> > news:02mWc.2448$Zi4.1543@prv-forum2.provo.novell.com...
> > > Hi,
> > >
> > > I'm trying to create a printer driver profile on my newly-sp2'd NW6.5
> > > servers.
> > >
> > > When I do, I get the error documented in TID 10093970:
> > >
> > > Error message: Winsock 11004 - The DNS has been found in the database,

> but
> > > its associated data is not correct.error
> > > group: WINSOCK
> > > Error code: 11004
> > >
> > > The TID suggests checking the DNS A records and the DNS domain is set

on
> > > the
> > > client PC, but this all seems to be correct.
> > >
> > > I suspect the problem is arising from my clustered environment

confusing
> > > something. I have an IP address for each of the 2 nodes and for each
> > > virtual
> > > server - of which the NDPS server is one.
> > >
> > > I've tried accessing iManager with the DNS name of the server, the DNS
> > > name
> > > of the virtual server, the IP address of the cluster node and the IP
> > > address
> > > of the virtual server - but the same thing happens each time.
> > >
> > > Can anyone offer a suggestion? Even finding out which DNS record

> iManager
> > > is
> > > having issues with would help!
> > >
> > > Thanks,
> > >
> > > Iain
> > >
> > >

> >
> >

>
>