The Active Network
ActiveWin Anonymous | Create a User | Reviews | News | Forums | Advertise | VBA in Excel | Users Online: 0  
 

neowin.net

Amazon.com

  *  

DNS Issues on Server 2003
Forum: Windows Server 2003
Read Only Forum
Back to Windows Server 2003
All Forums
  Displaying Posts 1 through 2 of 2
  This is an archived static copy of ActiveWin.com.
#1 By 82659 (82.30.29.187) at Sunday, July 29, 2007 08:02:25 AM
Hi All, wonder if you can help I have a server with windows 2003 on 1 x desktop 1 x laptop 1 x 4 port router The server has been configured as a domain controller, a DNS server and a DHCP server The server scope is 192.168.0.1 to 198.168.254 Exceptions are 192.168.0.1 to 192.168.0.5 The router is on 192.168.0.1 - the Static IP addy of the server and the DNS addy is 192.168.0.5 the server is ported into lan port 1 on the router, desktop on 2 and laptop on 4 The laptop receives its TCP/IP settings from DHCP server above as does the desktop. Problem 1 - laptop receives it DHCP settings and is given 192.168.0.6 brill -- thats what I expect Desktop receives 192.168.0.10 - why does it not receive 192.168.0.7 - next ip addy in scope I can ping my server by name (Server01) and by domain - contoso.com from both laptop and desktop. I can also ping gateway and ping out to the net Problem 2 I cannot get either the desktop or the laptop to join a domain I get a Network not found error message. The DNS addy is the server addy which it should be If I do nslookup I get server not found. If I do nslookup server01 it finds it as it does if I do contoso.local DCDIAG also reports no errors - so why can I not get the computers to join the domain ? I am using an administrator account to join them that has the rights to !! Do I need to configure the server to have Router & RRAS Role aswell ? Absolutely stumped on this one - any hekp very much appreciated ---------------------------------------------- MCP, MCDST, A+

#2 By 81519 (124.184.80.244) at Sunday, August 12, 2007 05:41:02 AM
Problem 1: in short no idea....grab the MAC address off the NIC and reserve it on the DHCP scope to the IP address you want. Problem 2: Youe workstations may be trying to contact your ISP's DNS. What DNS options are @ssigned to your DHCP scope? ---------------------------------------------- Forsaken



 

  *  
  *   *
 
replica watches