Windows Forum

Ask something
Discussion Locked

Trouble with Domain Logons

0 helpful
14 replies

by bravelittletoaster 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm running 2k advanced server with appropriate updates and hotfixes. My domain is independant of the others on the netowork which do have domain controllers. These are out of my control but don't pose a problem to my knowledge. After building myserver, enabling DNS and active directory I expected user logons to work. On a Win 2k pro workstation, I opened the control panel >> system >> network ID tab >> properties. Instead of workgroup, I type in my domain PXDOM in the domain field. I amthen instructed to enter a username and password. I enter the server's admin password or a user with admin privledges. I recieve this error:

The following error occoured attepting to join the domain "PXDOM". (next line) The network path was notfound.

Here is the interesting part. I can borwse to the server through the Network Places and click on the server. It then asks me to authenticate myself. I enter a username and password, for example a user account stored on the server, and Ican gain access to all my shares and resources until the next workstation reboot, naturally. So why can't I join computers to the domain?

Curtis
ParallaxTech@earthlink.net

14 replies

by bravelittletoaster

Let me clarify, the other domain controllers are in charge of seperate domains, one of which houses the firewall and internet gateway.

by erikdr

Browsing the server in PXDOM happens through WINS emulation. Joining its domain relies fully on DNS. It seems that there is something wrong in your DNS settings.
a) Can you PING the server from the workstation with its DNS name?
b) Is the ws referring to your DC as its main DNS server?

Also please note that DNS servers _often_ have interferences with each other. So make sure your DNS names spaces are consistent with those of the other DNS servers inhouse!

Hope this helps,

- The Netherlands

by will shakespeare

Hi,

Erik's right in that the domain search is with DNS. If your domain controller is not running in mixed mode, it may need a dns suffix to find the domain controller, which you are not supplying.
It sounds that if you have setup DNS and AD correctly, integrated, then you will have had to change the mode at some point to native mode, if you didn't from installation, so your domain name will most likely be pxdom.com, or something similar.
But, of course, I could be way off! :)
(I'm only abeginner with Windows 2000)
Just adding to the conversation to see if it helps! :)

Will

by will shakespeare

Also, are you sure you are not typing the W2K Adv Servers name in the Domain field, as opposed to the Domain? Try right clicking the My Computer icon and network ID tab on the domain controller to see what the computer is called including DNS suffix.
On our native mode servers here, the domain (not computer name) is entwan.com on the Net ID tab in My Computer properties, but in our mixed mode network it is all caps MDFLAN for domain.

Will

by matrex

Curtis
I if you haven't been able to log in your pro 2000 workstation to your domain. You must change your dns on your pro 2000 workstation with the IP of your domain. Depending on how many NIC cards you have on your server and make sure your dns is setup right on the server with out any errors. I had the same problem with my server and 2000 pro so I just added the IP address of my server in the dns area of 2000 pro and boom. It worked right away. Hope this works for you.

by shanghai sam

am i right in saying your trying to access a domain(server) from another machine on the same segment and log on with admin priv`s ?. have you configured at server end with your u/name and pass(which you are using) to be member of either domain/users or domain/administrators?

the user and pass your trying to log on with may have admin priv`s at server end but from another machine you will have to be member of either domain/users or domain/admins.

another possibility would be when tryingto log on you may not be assigning path to server. eg: server domain= mydomain.com would be machinename.mydomain.com, therefor when you log onto mydomain.com and type in pass with admin rights your pass would be machinename\pass.

by oxymoronx

DNS settings are incorrect or you're surfing the network with NetBEUI not IP. make sure your protocols are set up right on the workstation. DNS Scopes aren't that hard and if you set up AD, then you set up DNS. Are you using DHCP?? run the IPCONFIG utility on your workstations, make sure they're snagging an IP address.

This discussion is closed to new replies.