windows2003 lab -cant find host prob

[legend_018]

Hello. I'm creating a windows2003 lab. I have created windows2000 labs before.
I'm having a problem. I created an active directory windows2003 server. The fully qualified domain name is something1.redwood.treehouse.com. If I ping it while on that machine it works. When I say ping - I mean ping something1 or ping something1.redwood.treehouse.com

Now I build another windows2003 machine. I join and loginto the domain I created. If you go to the properties it says something2.redwood.treehouse.com. On that machine I can ping something2.redwood.treehouse.com and I can ping something2.

NOW on something2 I ping something1 and the correct ip address appears.
I than try to ping something1.redwood.treehouse.com and it doesn't work : (.

Same thing vice versa. On something1 I can ping something2 and it works. but I can't ping something2.redwood.treehouse.com. I says can't find host.

I'm not sure if I get it.

[Ob1]

so you can ping by the netbios names for each server but not by the FQDN correct?

[legend_018]

yes

[Ob1]

go to system properties of each server and click on the computer name tab. click change and the click the more button.

are you seeing the redwood.treehouse.com listed in the primary dns suffix? if not add it, i believe you will have to restart and try again

[legend_018]

I do have that. i'll have to continue tomorrow. I have to go.

one problem taht might be occurring -"maybe" is I also have 2 computers that has the workgroup of treehouse. it's not part of the domain it's just in it's own worksgroup. just so happens the workgroup name is treehouse. not sure if that matters.

[faulkner132]

Originally Posted by legend_018 NOW on something2 I ping something1 and the correct ip address appears. I than try to ping something1.redwood.treehouse.com and it doesn't work : (. Same thing vice versa. On something1 I can ping something2 and it works. but I can't ping something2.redwood.treehouse.com. I says can't find host.

Sounds like a DNS issue.
Do you have the DNS server service running on your test machine? If so, you will need to set up a DNS forward to the domain controller so it can resolve all FQDN's on your network.

[Ob1]

legend

i was messing around with my test lab and this is what i came up with.

on my workstation which is joined to the domain, i reconfigured my lan connection and set it up with a static ip, but this time i changed the dns server info and put in my isp dns servers. now i saved the changes opened a command prompt. when i pinged my server by the netbios name i was still able to get replies, but when i tried with FQDN i got the error below:

Z:\>ping server1

Pinging server1 [192.168.16.2] with 32 bytes of data:

Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128
Reply from 192.168.16.2: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.16.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

Z:\>ping server1.helpdesk.office
Ping request could not find host server1.helpdesk.office. Please check the name
and try again.

if thats the same error that you are getting and you have static ip's setup on your servers then you need to make sure that the dns server ip addresses are pointing to your DNS server which im guessing is your Domain Controllers ip address. for example if you look above where i got the replies, you would need to enter the ip address 192.168.16.2 in the dns info on both servers, then try pinging each of them by there FQDN again.

[legend_018]

I'm using dhcp on both servers. I have a smoothwall machine that is the dhcp server which is connected to the internet. both 2003 machines have access to the internet and the dhcp server properly allocated ip addresses to it. If I do ipconfig /all I can see the firewall machine listed for the dns server which is should. now I'm not sure what to do.

For "make sure that the dns server ip addresses are pointing to your DNS server"
it is - it's pointing to the smoothwall machine which is the dhcp server. no one ever said your windows2003 server/domain had to be a dns server.

[legend_018]

I just did a nslookup and it said:

can't find server name for the address that is the smoothwall machine
it showed the ip address of the dhcp server.

hmm I have to go check some settings over there and if I can't find anything i'll have to go to the smoothwall forums maybe.

[legend_018]

nslookup finds machine hosting dhcp. I added treehouse.com to the suffix on that machine and rebooted so now from every machine I can do a nslookup and it shows both name and ipaddress.

but still SAME problem

[legend_018]

ahh ok I demoted my domain controller because wanted to change the name. Than i promoted it back to domain controller and installed DNS. I'll do the forwarders to the smoothwall machine.
well see what happens. i'm almost done with setting it up.

[glc]

I was gonna say that I think for FQDN to work on a local domain, the DC has to be providing DNS. You may want to use a static IP on the DC.

[faulkner132]

Your Domain Controller must be a DNS server. You will have to add a domain forward to your smoothwall DNS server to point to the internal IP of your Domain Controller machine.

[legend_018]

ok build dns on the domain controller. setup forwarder. setup static ip.
setup static ip on 2nd 2003 server and put the DNSSERVER that I setup "first windows2003 server" as the dns server ip address.

from server2: I can ping fully qualified domain name of server1 "dns server"
from server1 "dns server" I can't ping fully qualified domain name of server2.

I did ipconfig /all and looked at settings and I'm trying to compare everything and can't find any differences. except dns server for server1 points to smoothwall machine and dns server for server2 points to server1. I can ping it by host name though.

[legend_018]

ok finally can ping both by fully qualified domain name. on 1st server forgot to put itself as the dns server address in the tcpip settings. now the reason why I got into this in the first place is because I wanted to build an exchange2003 server and it wouldn't let me and than I found this fqdn problem.

[glc]

What I usually do is make the DC that's running DNS the primary DNS and the ISP's DNS the secondary when I'm using static IP's - just in case something goes screwy with the forwarding.