Options

Unable to login into Windows 2003 Domain.

OkasonOkason Member Posts: 57 ■■□□□□□□□□
in Server 70-290
Happy New Year all, I recently installed the Eval copy of Win 2003 Server and set it up as DC and DNS but not the DHCP.
I succesfully joined an XP Pro machine to this domain that I called Okasonconcerns.
The Server name is hqokcsvr001
The Workstation name is hqokcwks001
Both are connected to a D link 4 port router, that has a DHCP capability, with a range of 192.168.0.100-200. I gave a static IP address of .254 to the server to avoid conflict.

However when I try to log into the domain through the Workstation it said that the domain is not available and I know for sure that is online and both can ping each other.Below is the TCP/IP configuration of both machines, Any thought/ suggestions to why I am having this problem is greatly appreciated.

Windows IP Configuration for the Server

Host Name . . . . . . . . . . . . : hqokcsvr001
Primary Dns Suffix . . . . . . . : okasonconcerns.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : okasonconcerns.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.254
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 127.0.0.1



Windows IP Configuration for the Work Station

Host Name . . . . . . . . . . . . : hqokcwks001
Primary Dns Suffix . . . . . . . : okasonconcerns.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : okasonconcerns.com
sd.cox.net

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : sd.cox.net
Description . . . . . . . . . . . : VIA Compatable Fast Ethernet Adapte

Physical Address. . . . . . . . . :
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.101
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Thursday, January 04, 2007 12:06:31 PM
Lease Expires . . . . . . . . . . : Thursday, January 11, 2007 12:06:31 PM
Thank You
All things work together for good........to them that believe..
· Share on FacebookShare on Twitter

Comments

  • Options
    sprkymrksprkymrk Member Posts: 4,884 ■■■□□□□□□□
    Your client is using your ISP DNS. Have your DLINK router assign the DC as DNS for the client, and set up your DNS on the server as a forwarder to your ISP.
    All things are possible, only believe.
    · Share on FacebookShare on Twitter
  • Options
    AlienAlien Member Posts: 398
    Your client is using your ISP DNS. Have your DLINK router assign the DC as DNS for the client, and set up your DNS on the server as a forwarder to your ISP.

    Once i experienced a problem of a similar nature while setting up a clients new WAP and an existing ADSL router.
    Hard times on planet earth.
    · Share on FacebookShare on Twitter
  • Options
    bighornsheepbighornsheep Member Posts: 1,506
    your workstation has to use your server's ip address as the DNS. Plan your DNS forest ahead of time to your needs. Dont forget to add a forwarder of your ISP's DNS address in your DNS Server on your server machine.
    Jack of all trades, master of none
    · Share on FacebookShare on Twitter
  • Options
    bighornsheepbighornsheep Member Posts: 1,506
    sprkymrk wrote:
    Your client is using your ISP DNS. Have your DLINK router assign the DC as DNS for the client, and set up your DNS on the server as a forwarder to your ISP.
    bighornsheep wrote:
    your workstation has to use your server's ip address as the DNS. Plan your DNS forest ahead of time to your needs. Dont forget to add a forwarder of your ISP's DNS address in your DNS Server on your server machine.

    4 minutes behind...err
    icon_lol.gif next time, next time.... icon_lol.gif
    Jack of all trades, master of none
    · Share on FacebookShare on Twitter
  • Options
    sprkymrksprkymrk Member Posts: 4,884 ■■■□□□□□□□
    bighornsheep wrote:
    sprkymrk wrote:
    Your client is using your ISP DNS. Have your DLINK router assign the DC as DNS for the client, and set up your DNS on the server as a forwarder to your ISP.
    bighornsheep wrote:
    your workstation has to use your server's ip address as the DNS. Plan your DNS forest ahead of time to your needs. Dont forget to add a forwarder of your ISP's DNS address in your DNS Server on your server machine.

    4 minutes behind...err
    icon_lol.gif next time, next time.... icon_lol.gif

    Hey, I never mind it when someone agrees with me. icon_lol.gif
    All things are possible, only believe.
    · Share on FacebookShare on Twitter
  • Options
    OkasonOkason Member Posts: 57 ■■□□□□□□□□
    Thank you sprkymrk and Bighorn, it work as you said, I appreciate your help.

    Thanks
    All things work together for good........to them that believe..
    · Share on FacebookShare on Twitter
  • Options
    bighornsheepbighornsheep Member Posts: 1,506
    okason wrote:
    Thank you sprkymrk and Bighorn, it work as you said, I appreciate your help.

    Thanks

    you're welcome.

    in preparation for GPO, I suggest you research into cached creditials. That is another potential issue with domain authentication.
    Jack of all trades, master of none
    · Share on FacebookShare on Twitter
Sign In or Register to comment.