SOLVED: Windows 7 Pro won't connect to isolated Windows Server 2003 domain

-

leo huanglijun of windows 7 networking forum told me should post here instead:

i purchased new laptop windows home premium installed. upgraded windows 7 professional.

i have existing isolated (intentionally without connection internet) network domain name bds1 , following computers:

192.168.10.5   grumpy - windows server 2003 standard - domain controller - dns server
192.168.10.6   happy  - windows server 2003 standard
192.168.10.15  sneezy - windows xp professional sp2
192.168.10.16  doc    - windows xp professional sp3

the network has worked these 4 computers several years.

i setup new laptop's network adapter ipv4 as:

192.168.10.250 vaiolaptop - windows 7 professional

all 5 computers : mask            = 255.255.255.0
                             gateway       = 192.168.10.16
                             dns servers = 192.168.10.5
                                                    192.168.10.6
                                  
5 machines can ping each of other four.

both grumpy , vaiolaptop have hosts file listing 5 computers in c:\windows\system32\drivers\etc.

"vaiolaptop" has been added grumpy's active directory under "computers".
                  
when go laptop , try add domain, get:
                  
"your computer not joined domain because following error occurred. attempt resolve dns name of domain controller in domain being joined has failed. please verify client configured reach dns server can resolve dns names in target domain."


thanks -

i'm not sure how work though, since mine account on machine , administrator account.

in event, answer problem, me anyway, at:

http://social.technet.microsoft.com/forums/en-us/w7itpronetworking/thread/69213952-2605-43a0-b7ed-756522985954?prof=required

mdj


Windows Server  >  Windows Server General Forum



Comments

Post a Comment

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

-
hello, i'm getting error when trying add print services role in windows 2012 standard. i'm getting same error whether use gui or powershell. this new server install. the powershell error follows: add-windowsfeature : request add or remove features on specified server failed. installation of 1 or more roles, role services, or features failed. the referenced assembly not found. error: 0x80073701 at line:1 char:1 + add-windowsfeature print-services + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + categoryinfo          : invalidoperation: (@{vhd=; credent...name=localhost}:psobject) [install-windowsfeature],     exception     + fullyqualifiederrorid : dismapi_error__failed_to_enable_updates,microsoft.windows.servermanager.commands.addwind    owsfeaturecommand success restart needed exit code      feature result ------- -------------- ---------      -------------- false   no             failed         {} issue appreciated. hi, i think should st
Read more

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

-
i've been trying disconnect server while , haven't been able to. there quick way this? i've used net session , net user , work sometime never consistent. can task? hi yrusad, thanks post. does work when check “computer management > system tools > shared folders > open files/sessions”. directly manage from gui. and based on knowledge, quick way mentioned net session /delete /y. mean never consistent? best regards, mary please remember mark replies answers if , unmark them if provide no help. if have feedback technet subscriber support, contact tnmff@microsoft.com . Windows Server  >  Windows Server 2012 General
Read more

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL

-
Image
i'm attempting setup windows 2016 rds standard deployment session hosting.  layout follows: rds01 - rds connection broker , web access ts02 - rds session host ts03 - rds session host domain these servers part of has (1) windows 2008 server , (2) windows 2016 servers acting dcs.  domain running @ windows 2003 functional level. servers on single routed network no firewall between them.  dns , ptr records servers exist , resolve on hosts.  servers can pinged each other. in other words, there no network connectivity issues. i've setup rds deployment several times w/ same results. the issue can login via rdweb interface on rds01 win10 desktop , connect published rdp desktop without issue (i.e. no error messages user) , no errors in logs.  when try directly rdp rds01, authenticate user (per event log) error stating user doesn't have access system.  in event log event id 1306 message of "remote desktop connection broker client failed redirect user &
Read more