Hi! I have a problem with windows 2008 r2 (and windows 7 professional) not joining my NT domain, that is served by a linux+samba+LDAP server in the same IP subnet. The NT domain server works ok, windows 7 pro and windows xp physical hosts can perfectly join and log on into it. This infrastructure has been working for years now. The XEN server dom0 is based on latest debian with xen server from the debian packages. Xen hypervisor amd64 4.0.1-5.2. This dom0 serves linux and windows domU on the local subnet with no (or minor) problems, both with HVM and paravirtualization. The network on the dom0 is done using bridged interfaces. The dom0 is 192.168.0.132, windows domU is .142 and NT domain server is .100. The domU can use the services in the network and the Internet. The hosts in the IP subnet can use the network resources of the domU. The dom0 has all iptables general rules set as ACCEPT, the only rules added are done by xen startup scripts. When I install a new windows 2008 r2 standard system as domU and try joining the domain from the local NT domain server I get the following error: <pre> The following error occurred attempting to join the domain "<my domain name goes here>": The specified domain either does not exist or could not be contacted. </pre> I suspect that there is some problem with the networking. Did I miss something? Can you recommend looking into some obvious setting somewhere? I''ve tried looking for similar problems on the net with no result, so I suspect that I''ve messed up something basic. The configuration for the windows domU is the following: kernel = "/usr/lib/xen-default/boot/hvmloader" builder=''hvm'' memory = 1024 shadow_memory = 24 name = "win2008eval1" vif = [ ''type=ioemu, bridge=eth4'' ] acpi = 1 apic = 1 pae = 1 disk = [ ''phy:/dev/vg/win2008eval1,hda,w''] vcpus = 1 device_model = ''/usr/lib/xen-default/bin/qemu-dm'' boot="c" sdl=0 vnc=1 vncconsole=1 vncpasswd=''kuleczka'' serial=''pty'' usbdevice=''tablet'' -- Best regards Jakub Kulesza _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Peter Braun
2012-Jul-12 10:25 UTC
Re: Debian dom0, windows domU, problems joining NT domain
Hi, whats the settings of domU network card? Seems to me like you are missing correct DNS server config there. There should be IP of linux/samsa/LDAP server. You can verify by ping "name of the samba server" if its resolved correctly. Br Peter 2012/7/12 Jakub Kulesza <jakkul@gmail.com>:> Hi! > > I have a problem with windows 2008 r2 (and windows 7 professional) not > joining my NT domain, that is served by a linux+samba+LDAP server in the > same IP subnet. > > The NT domain server works ok, windows 7 pro and windows xp physical hosts > can perfectly join and log on into it. This infrastructure has been working > for years now. > > The XEN server dom0 is based on latest debian with xen server from the > debian packages. Xen hypervisor amd64 4.0.1-5.2. This dom0 serves linux and > windows domU on the local subnet with no (or minor) problems, both with HVM > and paravirtualization. > > The network on the dom0 is done using bridged interfaces. The dom0 is > 192.168.0.132, windows domU is .142 and NT domain server is .100. The domU > can use the services in the network and the Internet. The hosts in the IP > subnet can use the network resources of the domU. The dom0 has all iptables > general rules set as ACCEPT, the only rules added are done by xen startup > scripts. > > When I install a new windows 2008 r2 standard system as domU and try joining > the domain from the local NT domain server I get the following error: > <pre> > The following error occurred attempting to join the domain "<my domain name > goes here>": > > The specified domain either does not exist or could not be contacted. > </pre> > > I suspect that there is some problem with the networking. Did I miss > something? Can you recommend looking into some obvious setting somewhere? > I''ve tried looking for similar problems on the net with no result, so I > suspect that I''ve messed up something basic. > > The configuration for the windows domU is the following: > kernel = "/usr/lib/xen-default/boot/hvmloader" > builder=''hvm'' > memory = 1024 > shadow_memory = 24 > name = "win2008eval1" > vif = [ ''type=ioemu, bridge=eth4'' ] > acpi = 1 > apic = 1 > pae = 1 > disk = [ ''phy:/dev/vg/win2008eval1,hda,w''] > vcpus = 1 > device_model = ''/usr/lib/xen-default/bin/qemu-dm'' > boot="c" > sdl=0 > vnc=1 > vncconsole=1 > vncpasswd=''kuleczka'' > serial=''pty'' > usbdevice=''tablet'' > > > -- > Best regards > Jakub Kulesza > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
Jakub Kulesza
2012-Jul-12 10:51 UTC
Re: Debian dom0, windows domU, problems joining NT domain
Hi! DNS works nice. If I logon onto the domU and ping the hostname of the NT domain server, the DNS resolves the server name and returns pings from 192.168.0.100 correctly. The settings of the domU net card are OK. MAC address is the same as in the xen domU config, IP is 192.168.0.142 with correct netmask, route .1, dns .100, DNS search domain is OK. Of course, the NT domain server name is different than the NT domain name. And the latter is not discoverable through DNS. I have read about propper setting of the DNS in NT domain by samba environment and this seems like a correct procedure. Or do you suggest otherwise? Physical hosts join the domain with no problem. This infrastructure is running this way since 2007. Regards 2012/7/12 Peter Braun <xenware@gmail.com>> Hi, > > whats the settings of domU network card? > > Seems to me like you are missing correct DNS server config there. > There should be IP of linux/samsa/LDAP server. > > You can verify by ping "name of the samba server" if its resolved > correctly. > > Br > > Peter > > 2012/7/12 Jakub Kulesza <jakkul@gmail.com>: > > Hi! > > > > I have a problem with windows 2008 r2 (and windows 7 professional) not > > joining my NT domain, that is served by a linux+samba+LDAP server in the > > same IP subnet. > > > > The NT domain server works ok, windows 7 pro and windows xp physical > hosts > > can perfectly join and log on into it. This infrastructure has been > working > > for years now. > > > > The XEN server dom0 is based on latest debian with xen server from the > > debian packages. Xen hypervisor amd64 4.0.1-5.2. This dom0 serves linux > and > > windows domU on the local subnet with no (or minor) problems, both with > HVM > > and paravirtualization. > > > > The network on the dom0 is done using bridged interfaces. The dom0 is > > 192.168.0.132, windows domU is .142 and NT domain server is .100. The > domU > > can use the services in the network and the Internet. The hosts in the IP > > subnet can use the network resources of the domU. The dom0 has all > iptables > > general rules set as ACCEPT, the only rules added are done by xen startup > > scripts. > > > > When I install a new windows 2008 r2 standard system as domU and try > joining > > the domain from the local NT domain server I get the following error: > > <pre> > > The following error occurred attempting to join the domain "<my domain > name > > goes here>": > > > > The specified domain either does not exist or could not be contacted. > > </pre> > > > > I suspect that there is some problem with the networking. Did I miss > > something? Can you recommend looking into some obvious setting somewhere? > > I''ve tried looking for similar problems on the net with no result, so I > > suspect that I''ve messed up something basic. > > > > The configuration for the windows domU is the following: > > kernel = "/usr/lib/xen-default/boot/hvmloader" > > builder=''hvm'' > > memory = 1024 > > shadow_memory = 24 > > name = "win2008eval1" > > vif = [ ''type=ioemu, bridge=eth4'' ] > > acpi = 1 > > apic = 1 > > pae = 1 > > disk = [ ''phy:/dev/vg/win2008eval1,hda,w''] > > vcpus = 1 > > device_model = ''/usr/lib/xen-default/bin/qemu-dm'' > > boot="c" > > sdl=0 > > vnc=1 > > vncconsole=1 > > vncpasswd=''kuleczka'' > > serial=''pty'' > > usbdevice=''tablet'' > > > > > > -- > > Best regards > > Jakub Kulesza > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xen.org > > http://lists.xen.org/xen-users > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >-- Pozdrawiam Jakub Kulesza _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Jakub Kulesza
2012-Jul-12 13:28 UTC
Re: Debian dom0, windows domU, problems joining NT domain
One more funny thing: If I just want to login on the NT domain server to browse the shared files, I can do that. I just type \\<hostname> in the explorer, I get a popup that asks me to login, i do, and i get the files. The only thing not working is joining the domain. regards JK 2012/7/12 Jakub Kulesza <jakkul@gmail.com>> Hi! > > DNS works nice. > > If I logon onto the domU and ping the hostname of the NT domain server, > the DNS resolves the server name and returns pings from 192.168.0.100 > correctly. > > The settings of the domU net card are OK. MAC address is the same as in > the xen domU config, IP is 192.168.0.142 with correct netmask, route .1, > dns .100, DNS search domain is OK. > > Of course, the NT domain server name is different than the NT domain name. > And the latter is not discoverable through DNS. I have read about propper > setting of the DNS in NT domain by samba environment and this seems like a > correct procedure. Or do you suggest otherwise? Physical hosts join the > domain with no problem. This infrastructure is running this way since 2007. > > Regards > > > 2012/7/12 Peter Braun <xenware@gmail.com> > >> Hi, >> >> whats the settings of domU network card? >> >> Seems to me like you are missing correct DNS server config there. >> There should be IP of linux/samsa/LDAP server. >> >> You can verify by ping "name of the samba server" if its resolved >> correctly. >> >> Br >> >> Peter >> >> 2012/7/12 Jakub Kulesza <jakkul@gmail.com>: >> > Hi! >> > >> > I have a problem with windows 2008 r2 (and windows 7 professional) not >> > joining my NT domain, that is served by a linux+samba+LDAP server in the >> > same IP subnet. >> > >> > The NT domain server works ok, windows 7 pro and windows xp physical >> hosts >> > can perfectly join and log on into it. This infrastructure has been >> working >> > for years now. >> > >> > The XEN server dom0 is based on latest debian with xen server from the >> > debian packages. Xen hypervisor amd64 4.0.1-5.2. This dom0 serves linux >> and >> > windows domU on the local subnet with no (or minor) problems, both with >> HVM >> > and paravirtualization. >> > >> > The network on the dom0 is done using bridged interfaces. The dom0 is >> > 192.168.0.132, windows domU is .142 and NT domain server is .100. The >> domU >> > can use the services in the network and the Internet. The hosts in the >> IP >> > subnet can use the network resources of the domU. The dom0 has all >> iptables >> > general rules set as ACCEPT, the only rules added are done by xen >> startup >> > scripts. >> > >> > When I install a new windows 2008 r2 standard system as domU and try >> joining >> > the domain from the local NT domain server I get the following error: >> > <pre> >> > The following error occurred attempting to join the domain "<my domain >> name >> > goes here>": >> > >> > The specified domain either does not exist or could not be contacted. >> > </pre> >> > >> > I suspect that there is some problem with the networking. Did I miss >> > something? Can you recommend looking into some obvious setting >> somewhere? >> > I''ve tried looking for similar problems on the net with no result, so I >> > suspect that I''ve messed up something basic. >> > >> > The configuration for the windows domU is the following: >> > kernel = "/usr/lib/xen-default/boot/hvmloader" >> > builder=''hvm'' >> > memory = 1024 >> > shadow_memory = 24 >> > name = "win2008eval1" >> > vif = [ ''type=ioemu, bridge=eth4'' ] >> > acpi = 1 >> > apic = 1 >> > pae = 1 >> > disk = [ ''phy:/dev/vg/win2008eval1,hda,w''] >> > vcpus = 1 >> > device_model = ''/usr/lib/xen-default/bin/qemu-dm'' >> > boot="c" >> > sdl=0 >> > vnc=1 >> > vncconsole=1 >> > vncpasswd=''kuleczka'' >> > serial=''pty'' >> > usbdevice=''tablet'' >> > >> > >> > -- >> > Best regards >> > Jakub Kulesza >> > >> > _______________________________________________ >> > Xen-users mailing list >> > Xen-users@lists.xen.org >> > http://lists.xen.org/xen-users >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > > > -- > Pozdrawiam > Jakub Kulesza >-- Pozdrawiam Jakub Kulesza _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Shane Johnson
2012-Jul-12 13:39 UTC
Re: Debian dom0, windows domU, problems joining NT domain
Jakub, I ran into problems with 2008 R2 and a NT Domain due to R2 absolutely requires kerebos to join the domain. There are posts all over the internet regarding this and no solution that I have found but to migrate your domain controller to at least 2000 or higher. (Either that or wait for Samba to catch up.) Shane On Thu, Jul 12, 2012 at 7:28 AM, Jakub Kulesza <jakkul@gmail.com> wrote:> One more funny thing: > > If I just want to login on the NT domain server to browse the shared > files, I can do that. I just type \\<hostname> in the explorer, I get a > popup that asks me to login, i do, and i get the files. The only thing not > working is joining the domain. > > regards > JK > > > 2012/7/12 Jakub Kulesza <jakkul@gmail.com> > >> Hi! >> >> DNS works nice. >> >> If I logon onto the domU and ping the hostname of the NT domain server, >> the DNS resolves the server name and returns pings from 192.168.0.100 >> correctly. >> >> The settings of the domU net card are OK. MAC address is the same as in >> the xen domU config, IP is 192.168.0.142 with correct netmask, route .1, >> dns .100, DNS search domain is OK. >> >> Of course, the NT domain server name is different than the NT domain >> name. And the latter is not discoverable through DNS. I have read about >> propper setting of the DNS in NT domain by samba environment and this seems >> like a correct procedure. Or do you suggest otherwise? Physical hosts join >> the domain with no problem. This infrastructure is running this way since >> 2007. >> >> Regards >> >> >> 2012/7/12 Peter Braun <xenware@gmail.com> >> >>> Hi, >>> >>> whats the settings of domU network card? >>> >>> Seems to me like you are missing correct DNS server config there. >>> There should be IP of linux/samsa/LDAP server. >>> >>> You can verify by ping "name of the samba server" if its resolved >>> correctly. >>> >>> Br >>> >>> Peter >>> >>> 2012/7/12 Jakub Kulesza <jakkul@gmail.com>: >>> > Hi! >>> > >>> > I have a problem with windows 2008 r2 (and windows 7 professional) not >>> > joining my NT domain, that is served by a linux+samba+LDAP server in >>> the >>> > same IP subnet. >>> > >>> > The NT domain server works ok, windows 7 pro and windows xp physical >>> hosts >>> > can perfectly join and log on into it. This infrastructure has been >>> working >>> > for years now. >>> > >>> > The XEN server dom0 is based on latest debian with xen server from the >>> > debian packages. Xen hypervisor amd64 4.0.1-5.2. This dom0 serves >>> linux and >>> > windows domU on the local subnet with no (or minor) problems, both >>> with HVM >>> > and paravirtualization. >>> > >>> > The network on the dom0 is done using bridged interfaces. The dom0 is >>> > 192.168.0.132, windows domU is .142 and NT domain server is .100. The >>> domU >>> > can use the services in the network and the Internet. The hosts in the >>> IP >>> > subnet can use the network resources of the domU. The dom0 has all >>> iptables >>> > general rules set as ACCEPT, the only rules added are done by xen >>> startup >>> > scripts. >>> > >>> > When I install a new windows 2008 r2 standard system as domU and try >>> joining >>> > the domain from the local NT domain server I get the following error: >>> > <pre> >>> > The following error occurred attempting to join the domain "<my domain >>> name >>> > goes here>": >>> > >>> > The specified domain either does not exist or could not be contacted. >>> > </pre> >>> > >>> > I suspect that there is some problem with the networking. Did I miss >>> > something? Can you recommend looking into some obvious setting >>> somewhere? >>> > I''ve tried looking for similar problems on the net with no result, so I >>> > suspect that I''ve messed up something basic. >>> > >>> > The configuration for the windows domU is the following: >>> > kernel = "/usr/lib/xen-default/boot/hvmloader" >>> > builder=''hvm'' >>> > memory = 1024 >>> > shadow_memory = 24 >>> > name = "win2008eval1" >>> > vif = [ ''type=ioemu, bridge=eth4'' ] >>> > acpi = 1 >>> > apic = 1 >>> > pae = 1 >>> > disk = [ ''phy:/dev/vg/win2008eval1,hda,w''] >>> > vcpus = 1 >>> > device_model = ''/usr/lib/xen-default/bin/qemu-dm'' >>> > boot="c" >>> > sdl=0 >>> > vnc=1 >>> > vncconsole=1 >>> > vncpasswd=''kuleczka'' >>> > serial=''pty'' >>> > usbdevice=''tablet'' >>> > >>> > >>> > -- >>> > Best regards >>> > Jakub Kulesza >>> > >>> > _______________________________________________ >>> > Xen-users mailing list >>> > Xen-users@lists.xen.org >>> > http://lists.xen.org/xen-users >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> >> >> -- >> Pozdrawiam >> Jakub Kulesza >> > > > > -- > Pozdrawiam > Jakub Kulesza > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >-- Shane D. Johnson IT Administrator Rasmussen Equipment _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Jakub Kulesza
2012-Jul-12 13:46 UTC
Re: Debian dom0, windows domU, problems joining NT domain
Wow, thanks, that''s reasonable. What if I start windows 7 professional as domU and it fails joining with the exact same message. Windows 7 pro physical machines join perfectly. 2012/7/12 Shane Johnson <sdj@rasmussenequipment.com>> Jakub, > I ran into problems with 2008 R2 and a NT Domain due to R2 absolutely > requires kerebos to join the domain. There are posts all over the internet > regarding this and no solution that I have found but to migrate your > domain controller to at least 2000 or higher. (Either that or wait for > Samba to catch up.) > > Shane > > > On Thu, Jul 12, 2012 at 7:28 AM, Jakub Kulesza <jakkul@gmail.com> wrote: > >> One more funny thing: >> >> If I just want to login on the NT domain server to browse the shared >> files, I can do that. I just type \\<hostname> in the explorer, I get a >> popup that asks me to login, i do, and i get the files. The only thing not >> working is joining the domain. >> >> regards >> JK >> >> >> 2012/7/12 Jakub Kulesza <jakkul@gmail.com> >> >>> Hi! >>> >>> DNS works nice. >>> >>> If I logon onto the domU and ping the hostname of the NT domain server, >>> the DNS resolves the server name and returns pings from 192.168.0.100 >>> correctly. >>> >>> The settings of the domU net card are OK. MAC address is the same as in >>> the xen domU config, IP is 192.168.0.142 with correct netmask, route .1, >>> dns .100, DNS search domain is OK. >>> >>> Of course, the NT domain server name is different than the NT domain >>> name. And the latter is not discoverable through DNS. I have read about >>> propper setting of the DNS in NT domain by samba environment and this seems >>> like a correct procedure. Or do you suggest otherwise? Physical hosts join >>> the domain with no problem. This infrastructure is running this way since >>> 2007. >>> >>> Regards >>> >>> >>> 2012/7/12 Peter Braun <xenware@gmail.com> >>> >>>> Hi, >>>> >>>> whats the settings of domU network card? >>>> >>>> Seems to me like you are missing correct DNS server config there. >>>> There should be IP of linux/samsa/LDAP server. >>>> >>>> You can verify by ping "name of the samba server" if its resolved >>>> correctly. >>>> >>>> Br >>>> >>>> Peter >>>> >>>> 2012/7/12 Jakub Kulesza <jakkul@gmail.com>: >>>> > Hi! >>>> > >>>> > I have a problem with windows 2008 r2 (and windows 7 professional) not >>>> > joining my NT domain, that is served by a linux+samba+LDAP server in >>>> the >>>> > same IP subnet. >>>> > >>>> > The NT domain server works ok, windows 7 pro and windows xp physical >>>> hosts >>>> > can perfectly join and log on into it. This infrastructure has been >>>> working >>>> > for years now. >>>> > >>>> > The XEN server dom0 is based on latest debian with xen server from the >>>> > debian packages. Xen hypervisor amd64 4.0.1-5.2. This dom0 serves >>>> linux and >>>> > windows domU on the local subnet with no (or minor) problems, both >>>> with HVM >>>> > and paravirtualization. >>>> > >>>> > The network on the dom0 is done using bridged interfaces. The dom0 is >>>> > 192.168.0.132, windows domU is .142 and NT domain server is .100. The >>>> domU >>>> > can use the services in the network and the Internet. The hosts in >>>> the IP >>>> > subnet can use the network resources of the domU. The dom0 has all >>>> iptables >>>> > general rules set as ACCEPT, the only rules added are done by xen >>>> startup >>>> > scripts. >>>> > >>>> > When I install a new windows 2008 r2 standard system as domU and try >>>> joining >>>> > the domain from the local NT domain server I get the following error: >>>> > <pre> >>>> > The following error occurred attempting to join the domain "<my >>>> domain name >>>> > goes here>": >>>> > >>>> > The specified domain either does not exist or could not be contacted. >>>> > </pre> >>>> > >>>> > I suspect that there is some problem with the networking. Did I miss >>>> > something? Can you recommend looking into some obvious setting >>>> somewhere? >>>> > I''ve tried looking for similar problems on the net with no result, so >>>> I >>>> > suspect that I''ve messed up something basic. >>>> > >>>> > The configuration for the windows domU is the following: >>>> > kernel = "/usr/lib/xen-default/boot/hvmloader" >>>> > builder=''hvm'' >>>> > memory = 1024 >>>> > shadow_memory = 24 >>>> > name = "win2008eval1" >>>> > vif = [ ''type=ioemu, bridge=eth4'' ] >>>> > acpi = 1 >>>> > apic = 1 >>>> > pae = 1 >>>> > disk = [ ''phy:/dev/vg/win2008eval1,hda,w''] >>>> > vcpus = 1 >>>> > device_model = ''/usr/lib/xen-default/bin/qemu-dm'' >>>> > boot="c" >>>> > sdl=0 >>>> > vnc=1 >>>> > vncconsole=1 >>>> > vncpasswd=''kuleczka'' >>>> > serial=''pty'' >>>> > usbdevice=''tablet'' >>>> > >>>> > >>>> > -- >>>> > Best regards >>>> > Jakub Kulesza >>>> > >>>> > _______________________________________________ >>>> > Xen-users mailing list >>>> > Xen-users@lists.xen.org >>>> > http://lists.xen.org/xen-users >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> http://lists.xen.org/xen-users >>>> >>> >>> >>> >>> -- >>> Pozdrawiam >>> Jakub Kulesza >>> >> >> >> >> -- >> Pozdrawiam >> Jakub Kulesza >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > > > -- > Shane D. Johnson > IT Administrator > Rasmussen Equipment > > >-- Pozdrawiam Jakub Kulesza _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Shane Johnson
2012-Jul-12 13:57 UTC
Re: Debian dom0, windows domU, problems joining NT domain
Jakub, Sorry, I don''t have 7 joined to our NT domain, so I don''t know for sure. But from memory 7 doesn''t have the same requirements or that you can make a registry change to allow it to join the domain. Shane On Thu, Jul 12, 2012 at 7:46 AM, Jakub Kulesza <jakkul@gmail.com> wrote:> Wow, thanks, that''s reasonable. > > What if I start windows 7 professional as domU and it fails joining with > the exact same message. Windows 7 pro physical machines join perfectly. > > 2012/7/12 Shane Johnson <sdj@rasmussenequipment.com> > >> Jakub, >> I ran into problems with 2008 R2 and a NT Domain due to R2 absolutely >> requires kerebos to join the domain. There are posts all over the internet >> regarding this and no solution that I have found but to migrate your >> domain controller to at least 2000 or higher. (Either that or wait for >> Samba to catch up.) >> >> Shane >> >> >> On Thu, Jul 12, 2012 at 7:28 AM, Jakub Kulesza <jakkul@gmail.com> wrote: >> >>> One more funny thing: >>> >>> If I just want to login on the NT domain server to browse the shared >>> files, I can do that. I just type \\<hostname> in the explorer, I get a >>> popup that asks me to login, i do, and i get the files. The only thing not >>> working is joining the domain. >>> >>> regards >>> JK >>> >>> >>> 2012/7/12 Jakub Kulesza <jakkul@gmail.com> >>> >>>> Hi! >>>> >>>> DNS works nice. >>>> >>>> If I logon onto the domU and ping the hostname of the NT domain server, >>>> the DNS resolves the server name and returns pings from 192.168.0.100 >>>> correctly. >>>> >>>> The settings of the domU net card are OK. MAC address is the same as in >>>> the xen domU config, IP is 192.168.0.142 with correct netmask, route .1, >>>> dns .100, DNS search domain is OK. >>>> >>>> Of course, the NT domain server name is different than the NT domain >>>> name. And the latter is not discoverable through DNS. I have read about >>>> propper setting of the DNS in NT domain by samba environment and this seems >>>> like a correct procedure. Or do you suggest otherwise? Physical hosts join >>>> the domain with no problem. This infrastructure is running this way since >>>> 2007. >>>> >>>> Regards >>>> >>>> >>>> 2012/7/12 Peter Braun <xenware@gmail.com> >>>> >>>>> Hi, >>>>> >>>>> whats the settings of domU network card? >>>>> >>>>> Seems to me like you are missing correct DNS server config there. >>>>> There should be IP of linux/samsa/LDAP server. >>>>> >>>>> You can verify by ping "name of the samba server" if its resolved >>>>> correctly. >>>>> >>>>> Br >>>>> >>>>> Peter >>>>> >>>>> 2012/7/12 Jakub Kulesza <jakkul@gmail.com>: >>>>> > Hi! >>>>> > >>>>> > I have a problem with windows 2008 r2 (and windows 7 professional) >>>>> not >>>>> > joining my NT domain, that is served by a linux+samba+LDAP server in >>>>> the >>>>> > same IP subnet. >>>>> > >>>>> > The NT domain server works ok, windows 7 pro and windows xp physical >>>>> hosts >>>>> > can perfectly join and log on into it. This infrastructure has been >>>>> working >>>>> > for years now. >>>>> > >>>>> > The XEN server dom0 is based on latest debian with xen server from >>>>> the >>>>> > debian packages. Xen hypervisor amd64 4.0.1-5.2. This dom0 serves >>>>> linux and >>>>> > windows domU on the local subnet with no (or minor) problems, both >>>>> with HVM >>>>> > and paravirtualization. >>>>> > >>>>> > The network on the dom0 is done using bridged interfaces. The dom0 is >>>>> > 192.168.0.132, windows domU is .142 and NT domain server is .100. >>>>> The domU >>>>> > can use the services in the network and the Internet. The hosts in >>>>> the IP >>>>> > subnet can use the network resources of the domU. The dom0 has all >>>>> iptables >>>>> > general rules set as ACCEPT, the only rules added are done by xen >>>>> startup >>>>> > scripts. >>>>> > >>>>> > When I install a new windows 2008 r2 standard system as domU and try >>>>> joining >>>>> > the domain from the local NT domain server I get the following error: >>>>> > <pre> >>>>> > The following error occurred attempting to join the domain "<my >>>>> domain name >>>>> > goes here>": >>>>> > >>>>> > The specified domain either does not exist or could not be contacted. >>>>> > </pre> >>>>> > >>>>> > I suspect that there is some problem with the networking. Did I miss >>>>> > something? Can you recommend looking into some obvious setting >>>>> somewhere? >>>>> > I''ve tried looking for similar problems on the net with no result, >>>>> so I >>>>> > suspect that I''ve messed up something basic. >>>>> > >>>>> > The configuration for the windows domU is the following: >>>>> > kernel = "/usr/lib/xen-default/boot/hvmloader" >>>>> > builder=''hvm'' >>>>> > memory = 1024 >>>>> > shadow_memory = 24 >>>>> > name = "win2008eval1" >>>>> > vif = [ ''type=ioemu, bridge=eth4'' ] >>>>> > acpi = 1 >>>>> > apic = 1 >>>>> > pae = 1 >>>>> > disk = [ ''phy:/dev/vg/win2008eval1,hda,w''] >>>>> > vcpus = 1 >>>>> > device_model = ''/usr/lib/xen-default/bin/qemu-dm'' >>>>> > boot="c" >>>>> > sdl=0 >>>>> > vnc=1 >>>>> > vncconsole=1 >>>>> > vncpasswd=''kuleczka'' >>>>> > serial=''pty'' >>>>> > usbdevice=''tablet'' >>>>> > >>>>> > >>>>> > -- >>>>> > Best regards >>>>> > Jakub Kulesza >>>>> > >>>>> > _______________________________________________ >>>>> > Xen-users mailing list >>>>> > Xen-users@lists.xen.org >>>>> > http://lists.xen.org/xen-users >>>>> >>>>> _______________________________________________ >>>>> Xen-users mailing list >>>>> Xen-users@lists.xen.org >>>>> http://lists.xen.org/xen-users >>>>> >>>> >>>> >>>> >>>> -- >>>> Pozdrawiam >>>> Jakub Kulesza >>>> >>> >>> >>> >>> -- >>> Pozdrawiam >>> Jakub Kulesza >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xen.org >>> http://lists.xen.org/xen-users >>> >> >> >> >> -- >> Shane D. Johnson >> IT Administrator >> Rasmussen Equipment >> >> >> > > > -- > Pozdrawiam > Jakub Kulesza >-- Shane D. Johnson IT Administrator Rasmussen Equipment _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Jakub Kulesza
2012-Jul-12 15:14 UTC
Re: Debian dom0, windows domU, problems joining NT domain
Silly me, registry settings provided here http://wiki.samba.org/index.php/Windows7#Windows_7_Registry_settings allowed for the 2008 R2 windows server to join samba nt domain PDC. Case closed. Best regards 2012/7/12 Shane Johnson <sdj@rasmussenequipment.com>> Jakub, > Sorry, I don''t have 7 joined to our NT domain, so I don''t know for sure. > But from memory 7 doesn''t have the same requirements or that you can make > a registry change to allow it to join the domain. > > Shane > > > On Thu, Jul 12, 2012 at 7:46 AM, Jakub Kulesza <jakkul@gmail.com> wrote: > >> Wow, thanks, that''s reasonable. >> >> What if I start windows 7 professional as domU and it fails joining with >> the exact same message. Windows 7 pro physical machines join perfectly. >> >> 2012/7/12 Shane Johnson <sdj@rasmussenequipment.com> >> >>> Jakub, >>> I ran into problems with 2008 R2 and a NT Domain due to R2 absolutely >>> requires kerebos to join the domain. There are posts all over the internet >>> regarding this and no solution that I have found but to migrate your >>> domain controller to at least 2000 or higher. (Either that or wait for >>> Samba to catch up.) >>> >>> Shane >>> >>> >>> On Thu, Jul 12, 2012 at 7:28 AM, Jakub Kulesza <jakkul@gmail.com> wrote: >>> >>>> One more funny thing: >>>> >>>> If I just want to login on the NT domain server to browse the shared >>>> files, I can do that. I just type \\<hostname> in the explorer, I get a >>>> popup that asks me to login, i do, and i get the files. The only thing not >>>> working is joining the domain. >>>> >>>> regards >>>> JK >>>> >>>> >>>> 2012/7/12 Jakub Kulesza <jakkul@gmail.com> >>>> >>>>> Hi! >>>>> >>>>> DNS works nice. >>>>> >>>>> If I logon onto the domU and ping the hostname of the NT domain >>>>> server, the DNS resolves the server name and returns pings from >>>>> 192.168.0.100 correctly. >>>>> >>>>> The settings of the domU net card are OK. MAC address is the same as >>>>> in the xen domU config, IP is 192.168.0.142 with correct netmask, route .1, >>>>> dns .100, DNS search domain is OK. >>>>> >>>>> Of course, the NT domain server name is different than the NT domain >>>>> name. And the latter is not discoverable through DNS. I have read about >>>>> propper setting of the DNS in NT domain by samba environment and this seems >>>>> like a correct procedure. Or do you suggest otherwise? Physical hosts join >>>>> the domain with no problem. This infrastructure is running this way since >>>>> 2007. >>>>> >>>>> Regards >>>>> >>>>> >>>>> 2012/7/12 Peter Braun <xenware@gmail.com> >>>>> >>>>>> Hi, >>>>>> >>>>>> whats the settings of domU network card? >>>>>> >>>>>> Seems to me like you are missing correct DNS server config there. >>>>>> There should be IP of linux/samsa/LDAP server. >>>>>> >>>>>> You can verify by ping "name of the samba server" if its resolved >>>>>> correctly. >>>>>> >>>>>> Br >>>>>> >>>>>> Peter >>>>>> >>>>>> 2012/7/12 Jakub Kulesza <jakkul@gmail.com>: >>>>>> > Hi! >>>>>> > >>>>>> > I have a problem with windows 2008 r2 (and windows 7 professional) >>>>>> not >>>>>> > joining my NT domain, that is served by a linux+samba+LDAP server >>>>>> in the >>>>>> > same IP subnet. >>>>>> > >>>>>> > The NT domain server works ok, windows 7 pro and windows xp >>>>>> physical hosts >>>>>> > can perfectly join and log on into it. This infrastructure has been >>>>>> working >>>>>> > for years now. >>>>>> > >>>>>> > The XEN server dom0 is based on latest debian with xen server from >>>>>> the >>>>>> > debian packages. Xen hypervisor amd64 4.0.1-5.2. This dom0 serves >>>>>> linux and >>>>>> > windows domU on the local subnet with no (or minor) problems, both >>>>>> with HVM >>>>>> > and paravirtualization. >>>>>> > >>>>>> > The network on the dom0 is done using bridged interfaces. The dom0 >>>>>> is >>>>>> > 192.168.0.132, windows domU is .142 and NT domain server is .100. >>>>>> The domU >>>>>> > can use the services in the network and the Internet. The hosts in >>>>>> the IP >>>>>> > subnet can use the network resources of the domU. The dom0 has all >>>>>> iptables >>>>>> > general rules set as ACCEPT, the only rules added are done by xen >>>>>> startup >>>>>> > scripts. >>>>>> > >>>>>> > When I install a new windows 2008 r2 standard system as domU and >>>>>> try joining >>>>>> > the domain from the local NT domain server I get the following >>>>>> error: >>>>>> > <pre> >>>>>> > The following error occurred attempting to join the domain "<my >>>>>> domain name >>>>>> > goes here>": >>>>>> > >>>>>> > The specified domain either does not exist or could not be >>>>>> contacted. >>>>>> > </pre> >>>>>> > >>>>>> > I suspect that there is some problem with the networking. Did I miss >>>>>> > something? Can you recommend looking into some obvious setting >>>>>> somewhere? >>>>>> > I''ve tried looking for similar problems on the net with no result, >>>>>> so I >>>>>> > suspect that I''ve messed up something basic. >>>>>> > >>>>>> > The configuration for the windows domU is the following: >>>>>> > kernel = "/usr/lib/xen-default/boot/hvmloader" >>>>>> > builder=''hvm'' >>>>>> > memory = 1024 >>>>>> > shadow_memory = 24 >>>>>> > name = "win2008eval1" >>>>>> > vif = [ ''type=ioemu, bridge=eth4'' ] >>>>>> > acpi = 1 >>>>>> > apic = 1 >>>>>> > pae = 1 >>>>>> > disk = [ ''phy:/dev/vg/win2008eval1,hda,w''] >>>>>> > vcpus = 1 >>>>>> > device_model = ''/usr/lib/xen-default/bin/qemu-dm'' >>>>>> > boot="c" >>>>>> > sdl=0 >>>>>> > vnc=1 >>>>>> > vncconsole=1 >>>>>> > vncpasswd=''kuleczka'' >>>>>> > serial=''pty'' >>>>>> > usbdevice=''tablet'' >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Best regards >>>>>> > Jakub Kulesza >>>>>> > >>>>>> > _______________________________________________ >>>>>> > Xen-users mailing list >>>>>> > Xen-users@lists.xen.org >>>>>> > http://lists.xen.org/xen-users >>>>>> >>>>>> _______________________________________________ >>>>>> Xen-users mailing list >>>>>> Xen-users@lists.xen.org >>>>>> http://lists.xen.org/xen-users >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Pozdrawiam >>>>> Jakub Kulesza >>>>> >>>> >>>> >>>> >>>> -- >>>> Pozdrawiam >>>> Jakub Kulesza >>>> >>>> _______________________________________________ >>>> Xen-users mailing list >>>> Xen-users@lists.xen.org >>>> http://lists.xen.org/xen-users >>>> >>> >>> >>> >>> -- >>> Shane D. Johnson >>> IT Administrator >>> Rasmussen Equipment >>> >>> >>> >> >> >> -- >> Pozdrawiam >> Jakub Kulesza >> > > > > -- > Shane D. Johnson > IT Administrator > Rasmussen Equipment > > >-- Pozdrawiam Jakub Kulesza _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users