|
|||||||||
|
|||||||||
|
|||||||||
 |
|||||||||
| |
||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
ASP Free Forums Sponsor:
|
|
|
|
#1
November 29th, 2006, 09:20 AM
|
||||
|
||||
|
New to networking - I just want to setup a domain controller and connect to it!
Hi Guys,
Im new to networking... I have just bought a new PC and I want to set it up as the server for my home network (mainly so that I can play around with it and learn more about networking). I have installed Windows Server 2003 on it (we get loads of free software from our university!), and I have gone through the 'simple setup wizard'. Its installed the Domain Controller, DNS server, DHCP server, and a Remote Access/VPN Server. I called my server lozware.local. Now... how do I go about joining this domain from my other computer? I have gone into the network properties for the wireless connection that I am using, and I have changed the DNS server IP to my Windows Server's IP (192.168.2.5). I've then gone into Control Panel > System > Computer Name, and typed in lozware.local into the domain textbox, and clicked Join. It loaded for about 10 seconds then said "DNS name does not exist". Also, I cannot access any websites when my Windows Server is set as the DNS server. How do I make it so that my Windows Server forwards outbound connections to by ISP's DNS server? Thanks! EDIT: If I type NSLOOKUP into cmd.exe on the client machine, it just says the following: Code:
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.2.5: Timed out
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.2.5
__________________
LozWare Website Directory Whooo! Free submissions, no recip needed. I'm a nice guy 
Last edited by LozWare : November 29th, 2006 at 09:24 AM.
|
|
#2
November 29th, 2006, 06:23 PM
|
|||
|
|||
|
In DNS, you need to right click on your domain and select properties.
Click on Forwarders. In DNS domain, click New and select All other DNS domains. Down the page a bit you shoud see Selected domains fowarder IP address list. Type in the address of your modem/router (if you have one) or ISP's DNS server here and click Add. Add a secondary DNS server if you want as well. That is probably enough to get you going.
|
|
#3
November 29th, 2006, 06:34 PM
|
||||
|
||||
|
Thanks for the reply.
Yeah, I've already done all that, but the workstation still isnt having any of it. Here's the weird thing: I have an IIS server running on both the Server and the Workstation. The one running on the Workstation can be accessed fine from the server, but the one running on the server cannot be accessed from the workstation. This is when I reset the workstation's network setting back to the default router settings.
|
|
#4
November 29th, 2006, 08:18 PM
|
|||
|
|||
|
On your workstation do this from a command line:
ipconfig /all and let me see what is there. Do the same on your server. Do you have WINS and DHCP running on your server? When joining the domain, you could also try just lozware instead of lozware.local
|
|
#5
November 29th, 2006, 09:06 PM
|
|||
|
|||
|
You are using a version of windows on the workstation that allows joining a domain, i.e., XP Pro not XP Home? You shouldn't have needed to do any changes to your workstation DNS settings to join the domain.
I'd suggest you make sure the workstation can find the domain server on the network before trying to change the workstation to join the domain. Try to map a network drive and use a domain login (connect as a different user) and get that working first.
__________________
====== Doug G ====== I didn't attend the funeral, but I sent a nice letter saying I approved of it. --Mark Twain
|
|
#6
November 30th, 2006, 02:36 AM
|
||||
|
||||
|
But surely if I leave the DNS settings to that of my router / ISP, then my workstation wont be able to lookup the name 'lozware.local' from my server? I know that Im probably wrong, but like I said, I'm to new this.
When I have the DNS settings on the Workstation set to default (that of the router) I get this: Code:
Windows IP Configuration
Host Name . . . . . . . . . . . . : lloyd-box
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Belkin
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-11-09-5E-BC-89
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : D-Link AirPlus G DWL-G510 Wireless P
CI Adapter(rev.C)
Physical Address. . . . . . . . . : 00-17-9A-81-3D-49
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
62.31.64.39
62.31.112.39
62.31.144.39
Lease Obtained. . . . . . . . . . : 29 November 2006 23:53:45
Lease Expires . . . . . . . . . . : 19 January 2038 03:14:07
When I have the DNS server set to that of the Windows Server, I get this (remember, 192.168.2.1 is my router, and 192.168.2.5 is my Server): Code:
Windows IP Configuration
Host Name . . . . . . . . . . . . : lloyd-box
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Belkin
Ethernet adapter Local Area Connection:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-11-09-5E-BC-89
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : Belkin
Description . . . . . . . . . . . : D-Link AirPlus G DWL-G510 Wireless P
CI Adapter(rev.C)
Physical Address. . . . . . . . . : 00-17-9A-81-3D-49
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.5
Lease Obtained. . . . . . . . . . : 30 November 2006 08:28:03
Lease Expires . . . . . . . . . . : 19 January 2038 03:14:07
From the server, I get this: Code:
Host Name . . . . . . . . . . . . : lozware-server Primary Dns Suffix . . . . . . . : lozware.local Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : lozware.local Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : D-Link AirPlus G DWL-G510 Wireless PCI Ad apter(rev.C) Physical Address. . . . . . . . . : 00-19-5B-2C-B9-00 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.2.5 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 DNS Servers . . . . . . . . . . . : 192.168.2.5 I have not setup a WINS servers or settings on the server. Im not even too sure what WINS is. In the DHCP server settings on my Windows Server, I have expanded the 'Server Options' tree and I dont think that what I am seeing is correct. There are 2 objects in there, one called '003 Router' and one called '006 DNS Servers'. However, both of the IP addresses for them are 192.168.0.1 - that IP does not belong to the router or the server, I have never even seen it before. Also, this whole 'I cant connect to the servers IIS server under a normal connection to the router' is a bit odd too. Theres not firewall installed on the server and the IIS server is assigned to all IP addresses, so I have no idea why it wont let me connect to the server's IIS server from the workstation. The server can access the workstation's IIS server just fine - its really bizarre - almost as if the server cant accept incoming connections. Last edited by LozWare : November 30th, 2006 at 02:38 AM.
|
|
#7
November 30th, 2006, 07:39 AM
|
|||
|
|||
|
Quote:
Change those setting to be your server 192.168.1.5 then do ipconfig /release then ipconfig /renew See if that does anything... ps it is past my Zzzzz time, so I won't be able to help anymore until tomorrow...
|
|
#9
November 30th, 2006, 12:44 PM
|
||||
|
||||
|
Okay, I tried to do that, but I got some weird results...
Code:
C:\Documents and Settings\Administrator>ipconfig Windows IP Configuration Ethernet adapter Wireless Network Connection: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.2.5 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.2.1 C:\Documents and Settings\Administrator>ipconfig /release Windows IP Configuration The operation failed as no adapter is in the state permissible for this operation. C:\Documents and Settings\Administrator>ipconfig /renew Windows IP Configuration The operation failed as no adapter is in the state permissible for this operation. C:\Documents and Settings\Administrator> What on earth is going on?!? Why wont it let me release or renew the connection? I think I know why the workstation cant connect to the server, and that's because the server doesnt seem to be allowing inbound connections. I have ran NETSTAT -a -n, and I have at least 10 processes listening on various ports on all IP addresses (0.0.0.0), but I cant connect to any of them from my workstation. Does windows server has some sort of built-in firewall that would do this? Or is it some other network problem? Like I said before, I can connect to the workstations fine from the server, just not the other way around. Thanks!
|
|
#10
November 30th, 2006, 04:52 PM
|
|||
|
|||
|
Sorry, it was a bit late last night...I don't think you are getting your ip address via DHCP are you?
Yes, your server is running dns, so it is doing some routing, and the server sends requests it doesn't know about to the outside world. One thing though, in DNS, do you have a host record for the server itself? I reckon it will be something fairly simple, whatever it is... <edit> Actually having a bit more of a read of it all again, it appears to be using dhcp. But is it getting the lease off your server or your modem? If you have dhcp on your modem, turn it off. The way we want the network setup is that your modem is to become the gateway, and your server can handle dns, dhcp and all that for your internal network, and forward all requests to the modem/outside world. Last edited by q97 : November 30th, 2006 at 05:16 PM.
|
|
#11
November 30th, 2006, 05:45 PM
|
||||
|
||||
|
Okay, I'll give that a go in a second. Just out of curiosity, how will the workstations know to use the Windows Server as the DHCP server? Do the workstations automatically presume that the DNS server is the DHCP server aswell?
My main problem at the moment is that I cannot establish a connection with the windows server what-so-ever. The server is not accepting any inbound connections at all (that includes inbound connections to the DNS server). There are various processes on the server which are listening for connections, but I cant connect to any of them from the workstation. Does Windows Server 2003 block inbound connections by default? If so, how can I disable this? Thanks!
|
|
#12
November 30th, 2006, 06:42 PM
|
|||
|
|||
|
DHCP servers will answer client requests automatically so you don't need to do anything on the client end. The client will just find the first dhcp server that answers its request.
Did you configure a server role after you installed W2k3? I suppose it is possible that there is a firewall service running, but I would have thought that sort of thing would be preconfigured to allow dns, dhcp and that type of thing. It is a server afterall. On our server here Windows firewall service is disabled...maybe see if it is running and stop it if it is, and see what happens.
|
|
#13
November 30th, 2006, 07:04 PM
|
||||
|
||||
|
So the client machine will scan the whole network untill it finds a DHCP server? Does the workstation just start at 192.168.0.0 and keep on counting up untill it finds one? Seems a bit inefficient. I tried opening up Windows Firewall on the server, but it returned some error saying that another service was using one of the system files required to run the firewall - so I imagine that Windows Firewall isnt running. Its really odd; I can connect to all of the services locally on the server. I have IIS running on the server too and I can connect to that when Im sat at the server |
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
