[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 519
  • Last Modified:

Workstation login to new SBS 2003 server gives domain unavailable error

I have just installed Small Business Server 2003 to a new PC.  I believe I have set it up to emulate the network settings used by our old Windows 2000 Server-based server.

I have set up a small test network that doesn't have the old server connected.
For testing workstation access, I have set up a test user account, "aaron" and added the workstation computer name to Active Directory.

Our domain is "ASRC".  
I can log in to the workstation as administrator and browse the whole network, including the server.

But when I attempt to log in as the test user, "aaron", I get an error message such as:

  "The system cannot log you in because the domain ASRC is unavailable"

Copies of the ipconfig info for server and workstation follow below...

P.S. I assume a domain name is not case sensitive, i.e. "asrc" is same as "ASRC"?

Regards

Leigh

SERVER:=======================================================


Windows IP Configuration



   Host Name . . . . . . . . . . . . : server

   Primary Dns Suffix  . . . . . . . : ASRC.net

   Node Type . . . . . . . . . . . . : Hybrid

   IP Routing Enabled. . . . . . . . : No

   WINS Proxy Enabled. . . . . . . . : No

   DNS Suffix Search List. . . . . . : ASRC.net



Ethernet adapter Server Local Area Connection:



   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller

   Physical Address. . . . . . . . . : 00-1A-92-34-63-CC

   DHCP Enabled. . . . . . . . . . . : No

   IP Address. . . . . . . . . . . . : 192.168.1.1

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Default Gateway . . . . . . . . . : 192.168.1.2

   DNS Servers . . . . . . . . . . . : 192.168.1.2

                                       192.231.203.132

   Primary WINS Server . . . . . . . : 192.168.1.1

WORKSTATION:=======================================================


Windows IP Configuration



        Host Name . . . . . . . . . . . . : PC005

        Primary Dns Suffix  . . . . . . . : asrc.net

        Node Type . . . . . . . . . . . . : Hybrid

        IP Routing Enabled. . . . . . . . : No

        WINS Proxy Enabled. . . . . . . . : No

        DNS Suffix Search List. . . . . . : asrc.net

                                            ASRC.local



Ethernet adapter Local Area Connection:



        Connection-specific DNS Suffix  . : ASRC.local

        Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection

        Physical Address. . . . . . . . . : 00-0D-60-09-F7-B6

        Dhcp Enabled. . . . . . . . . . . : Yes

        Autoconfiguration Enabled . . . . : Yes

        IP Address. . . . . . . . . . . . : 192.168.1.102

        Subnet Mask . . . . . . . . . . . : 255.255.255.0

        Default Gateway . . . . . . . . . : 192.168.1.2

        DHCP Server . . . . . . . . . . . : 192.168.1.1

        DNS Servers . . . . . . . . . . . : 192.168.1.1

                                            192.168.1.2

        Primary WINS Server . . . . . . . : 192.168.1.1

        Secondary WINS Server . . . . . . : 192.168.1.2

        Lease Obtained. . . . . . . . . . : Thursday, 9 August 2007 11:13:06 AM

        Lease Expires . . . . . . . . . . : Friday, 17 August 2007 11:13:06 AM

0
LeighWardle
Asked:
LeighWardle
4 Solutions
 
bluetabCommented:
What is your internal domain name; ASRC.net or ASRC.local.  I would recommend only using ASRC.local for your internal domain name.  It will make life much easier down the line.  For your DNS suffixes you should only use your internal domain (ie; ASRC.net)

Here's a couple other things:
Server: The only DNS server should be the server itself (192.168.1.1)
Workstation: The only DNS and WINS server should be the Windows servers, in this case 192.168.1.1.
  You're DNS suffix is ASRC.net but your search is ASRC.local.  Change this to whatever your actual internal domain is.  


The only DNS servers you should have on the server and workstation are the actual Windows DNS servers, in this case only 192.1681.1


0
 
tigermattCommented:
The DNS server at the server should be the server itself. You would then generally configure forwarders in DNS to send any queries for domains the server isn't authoritive for to your external ISP server, which in this case looks like 192.231.203.132?

What is your internal domain? You should really use a TLD which isn't registered on the internet for your internal setup, such as .local or .internal
Using a TLD registered on root name servers can cause you problems further down the line...
0
 
rshooper76Commented:
Like the others have said the DNS server on the server should be itself and only itself.  The primary and only dns server for the workstations should be the server.  Use forwading in DNS on the server to put in the ISP DNS servers.  Make sure you can ping the server by ip address and by name.  Also, make sure that this machien is a member of the domain.  If you have setup a new server, you might have have to remove it from the domain, and join it to the new domain.  You shoudl be able to tell if this is necessary by looking in Active Directory and seeing if this computer is listed.
0
 
kadadi_vIT AdminCommented:
n your internal dns server also use the primary dns address is the local Ip of the server  as 192.168.1.1 and  put the ISP dns in forwarders inDNS server console and on workstation configure  prinary dns is IP address of the server and alternative is the ISP then try to add the workstion on that domain.



Regards,

V.K.
0
 
LeighWardleAuthor Commented:
hi everyone,

I am sorry it has taken so long to reply.

Everyone helped with the solution so I have split the points 500/4 each.

Regards
Leigh
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now