|
||||||||
|
|
#1
|
|
I have setup a 2003 domain called domain.pri and it seems
to be running OK with the exception of one workstation. The workstation is running XP Pro and doesn't seem to want to join the domain cleanly. If I try to join the workstation to the Domain it gives an error message saying it can't find a domain controller. However If I join it to Domain.pri it connects just fine. After that, the workstation is unable to have any of its shares seen by the rest of the computers. However, it can see all of the shares of other computers. When I ping the server, I can see it both as server and server.domain.pri. Any ideas as to what is going on with this workstation? Thanks. Jeff Adamson |
|
#2
|
|||
|
|||
|
W2k/W2k3 domains are based on DNS and LDAP. Your XP Pro will find the
logon server through DNS/LDAP, so it is logical to use the DNS/AD name of the domain, not its Netbios name. What other clients do you have, and how are they configured? Do you have "legacy" (W9x/NT) clients? For these clients and the XP/W2k3 to all appear in the same browse list, they all need to be using Netbios over TCP/IP. XP/W2k3 doesn't have Netbeui support. "Jeff Adamson" <(E-Mail Removed)> wrote in message news:210601c3ffbe$640341b0$(E-Mail Removed)... > I have setup a 2003 domain called domain.pri and it seems > to be running OK with the exception of one workstation. > The workstation is running XP Pro and doesn't seem to > want to join the domain cleanly. > > If I try to join the workstation to the Domain it gives > an error message saying it can't find a domain > controller. However If I join it to Domain.pri it > connects just fine. After that, the workstation is unable > to have any of its shares seen by the rest of the > computers. However, it can see all of the shares of other > computers. > > When I ping the server, I can see it both as server and > server.domain.pri. > > Any ideas as to what is going on with this workstation? > Thanks. |
|
#3
|
|||
|
|||
|
I don't have any legacy computers on the domain, the
server is 2003 and the workstations are all XP Pro. I can't figure out why this workstation is acting so different from the others. >-----Original Message----- > W2k/W2k3 domains are based on DNS and LDAP. Your XP Pro will find the >logon server through DNS/LDAP, so it is logical to use the DNS/AD name of >the domain, not its Netbios name. > > What other clients do you have, and how are they configured? Do you have >"legacy" (W9x/NT) clients? For these clients and the XP/W2k3 to all appear >in the same browse list, they all need to be using Netbios over TCP/IP. >XP/W2k3 doesn't have Netbeui support. > >"Jeff Adamson" <(E-Mail Removed)> wrote in message >news:210601c3ffbe$640341b0$(E-Mail Removed)... >> I have setup a 2003 domain called domain.pri and it seems >> to be running OK with the exception of one workstation. >> The workstation is running XP Pro and doesn't seem to >> want to join the domain cleanly. >> >> If I try to join the workstation to the Domain it gives >> an error message saying it can't find a domain >> controller. However If I join it to Domain.pri it >> connects just fine. After that, the workstation is unable >> to have any of its shares seen by the rest of the >> computers. However, it can see all of the shares of other >> computers. >> >> When I ping the server, I can see it both as server and >> server.domain.pri. >> >> Any ideas as to what is going on with this workstation? >> Thanks. > > >. > |
|
#4
|
|||
|
|||
|
In the TCP/IP Advanced settings, check what DNS suffix it is using, and
compare that to one that works normally. "Jeff Adamson" <(E-Mail Removed)> wrote in message news:41d901c401f2$058b86c0$(E-Mail Removed)... > I don't have any legacy computers on the domain, the > server is 2003 and the workstations are all XP Pro. > I can't figure out why this workstation is acting so > different from the others. > > > >-----Original Message----- > > W2k/W2k3 domains are based on DNS and LDAP. Your XP > Pro will find the > >logon server through DNS/LDAP, so it is logical to use > the DNS/AD name of > >the domain, not its Netbios name. > > > > What other clients do you have, and how are they > configured? Do you have > >"legacy" (W9x/NT) clients? For these clients and the > XP/W2k3 to all appear > >in the same browse list, they all need to be using > Netbios over TCP/IP. > >XP/W2k3 doesn't have Netbeui support. > > > >"Jeff Adamson" <(E-Mail Removed)> > wrote in message > >news:210601c3ffbe$640341b0$(E-Mail Removed)... > >> I have setup a 2003 domain called domain.pri and it > seems > >> to be running OK with the exception of one workstation. > >> The workstation is running XP Pro and doesn't seem to > >> want to join the domain cleanly. > >> > >> If I try to join the workstation to the Domain it gives > >> an error message saying it can't find a domain > >> controller. However If I join it to Domain.pri it > >> connects just fine. After that, the workstation is > unable > >> to have any of its shares seen by the rest of the > >> computers. However, it can see all of the shares of > other > >> computers. > >> > >> When I ping the server, I can see it both as server and > >> server.domain.pri. > >> > >> Any ideas as to what is going on with this workstation? > >> Thanks. > > > > > >. > > |
![]() |
| Tags |
| 2003, domain, issues |
| Thread Tools | |
| Display Modes | |
|
|