yet another newbie question "domain name???" 3

[Kadanis]

yet another question from the current resident network newbie ;-)

how do i find out the domain name of the network. i need to set a new client desktop pc up. i created the add new computer disk from the server pc but the client keeps saying the domain name is incorrect.

any help much appreciated....

thanks in advance

 

[smsg]

If you are adding a new workstation to an existing windows network, check the properties of another computer that belongs to the domain (server or workstation). That is, right click on my computer (in desktop)and select properties. I will be in one of those tabs. It will show name of machine and the domain.

make sure your ip settings are OK. test by pinging any other machine on network. Also, make sure client for microsoft network is enabled else you will not be able to join domain.

SMSG

 

[Kadanis]

right i tried all that. got the domain name and still getting the error. tried pinging the new client pc from the server and it comes up with a "host not found" error.

the new client is on the list in active directory users and computers though.

any ideas?

thanks again

 

[d1onysus]

Did you try to pinging the other computers by name? How about by FQDN (thatcomputer.thisdomain.biz)?

 

[Kadanis]

yup. tried pinging other pcs on network and they come back fine. just this one new pc doesnt want to play ball.

its picking up the lan fine just not seeing the server domain or any other pc's. it keeps defaulting to its own workgroup and when i type the domain name in says it doesnt exist. any ideas?

 

[MasterofNone]

You say its picking up the lan but the other pc's cannot see it. How do you know it picking up the lan if it cannot see any of the pc's. Also as this is the server forum and you are adding a client pc, what OS?

Are you using DHCP or stitic address's. On the new pc goto command prompt and try pinging another address (ipaddress not hostname).

If your using DHCP try the following: command prompt. ipconfig
ake note of your ip address.
ipconfig /release
ipconfig /renew
Did it renew successfully and if so has it changed address. Had pc's not been on domain for a while when lease expires and this get reallocated (win98 was a git for holding it's IP)

 

[Kadanis]

Right ok. Basically I assumed it was getting the LAN ok because a connection icon appears in the sys tray with a "LAN Connected 100 MPBS" pop up. The server is W2K SBS with the client on W2K Pro

i think we are running dhcp but not 100%. i tried the ipconfig thing on a different client and it worked fine. ip didnt change. on the one i'm having problems with it said it couldn't release the client as adapters bound to dhcp had been auto configured?? what does this mean...

thanks for the help so far.

 

[Hondy]

check your DNS and gateway settings, Active directory is based on DNS so if the PC isn't set up with this it won't find the domain.

Do "ipconfig /all" in a cmd box, check what the DNS server is on a working machine then on the faulty machine.

 

[Kadanis]

ok done that theres quite a difference. the last 5 options on the working client are ip address; subnet mask; default gateway; dhcp server; dns servers (this has 3 ip addresses next to it);
the faulty machine stops at ip address (although it says autoconfiguration ip address not just ip address).

I suppose the question now is how do i set up the dns stuff....

thanks for all the help so far you've all been great.

 

[Hondy]

well, if you've got a dchp server this should be allocated automatically because you will have set these options on the dhcp server. I'm guessing you haven't so you'll needd to set the DNS info manually, you can leave the dhcp on auto if it has an address just click on the dns radio button and copy the dns IP address info in. (this is found on the properties of TCP/IP in the network properties)

You should ultimately add these into your DHCP Scope options, this way when the machine gets it's IP address it will also get the DNS info.

 

[Kadanis]

set up all the ip and dns manually but still not finding the domain or seeing any of the server files.

may have to approach this from another angle.

thanks for all the help

 

[Hondy]

it's not something simple like you are typing .com onto the domain name? try both "domain" and "domain.com".

Also make sure you can ping your sever, it has to be something fairly fundamental i think

 

[MasterofNone]

Right my thoughts on the matter are you are still not getting a DHCP address.If you had DHCP, you will be able to release/renew as this is sometimes required. The message you received when you tried this on the client machine is normally generated when the NIC has been configured with a static address, or has received no address from dhcp to release.

Check your network card properties. Is this configured for DHCP? If not change.

if it is, goto command prompt and do ipconfig. What is your ipaddress and is this within the scope of your network. Always remember, a client does not have to be a member of the domain or have permissions just to receive an address. It's only requirement is being able to talk to the DHCP server.

 

[Kadanis]

i just looked at the net card properties on a working computer and it has a couple of protocols that aren't showing on the new one. could it be that these need to be installed.

appletalk and netbeui?????

 

[Hondy]

it shouldn't use netbeui(it's not TCP/IP and therefor DNS) but it won't harm to try it. AppleTalk is for macs, you don't need it.

You never mentioned if you can ping your domain controller from the fauly machine, this is quite important.

my money is on a bad subnet mask, wrong ip range or something, cut and paste the results of your ipconfig /all and your ping for both the working and non-working.

 

[MasterofNone]

Only install appletalk if you have a mixed enviroment. As Hondy pointed out, this is for macs.

Netbeui is a different kettle of fish. This was the main protocol under windows networking, and allowed easy sharing of files (it's even a quicker protocol than TCP/IP).Unfortunately, if I remember my ptotocols correctly this is not routable so has become almost redundent in corporate enviroments. Infact Netbeui is no longer a supported protocol under XP and server 2003 (although you can manaual install from their cd's). Bit of a history lesson but shouldn't have any impact by not installing on a full tcp/ip network.

 

[Kadanis]

ping the server from working maching just gets 4 replies and says "4 packets sent, 4 recieved, round trip 0milliseconds"

ping from the new client 4 rows of "destination host unreachable."

maybe a bit of a dumb question but are there any security issues about posting server domains, dns and ip's on an open forum. Like I said complete newbie to networks here ;o)

 

[MasterofNone]

Shouldn't be an issue. Not as if you are giving us your web address, passwords to an account an defining open ports for us to gain access to your network. The address's you supply will be your internal network address i.e. 192.168, and these are used by numerous companies.

The fact you have received destination host unreachable is a good point as we are sticking to the IP allocation, and this does appears to be your problem. As this claims destination host unreachable you are either not in receipt of a valid IP address, or as Hondy pointed out earlier, you might have a subnet masking issue. Without the information requested earlier there probably isn't much more we can state with any certainty.

 

[Kadanis]

ok. here you go. one is the ipconfig all of the working client and one of the broken one. i guess, from what you said there is an issue somewhere with the new client ip. it doesnt start 192.168???? is that right?

working.
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : pc36
Primary DNS Suffix . . . . . . . : carelinksrv.carelink
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : carelinksrv.carelink

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card 10/100 (SMC1211TX)
Physical Address. . . . . . . . . : 00-10-B5-FB-65-7C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.85
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.3
DHCP Server . . . . . . . . . . . : 192.168.0.3
DNS Servers . . . . . . . . . . . : 192.168.0.3
-----------------------------------------

not working
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : alpha
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : RealTek RTL8139(A) PCI Fast Ethernet Adapter
Physical Address. . . . . . . . . : 00-02-44-65-47-CC
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.75.220
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

 

[lgarner]

The DHCP server is not delivering an address to the non-working client. This may be a connection problem or a server problem. I'd suggest finding an unused IP address, preferably out of the range that the dhcp server should be issuing, and manually assinging it to the client. Then try to ping other devices.