DNS / AD domain problem 1

[Anarax]

Hello! This has to be easy, so easy that I am missing it.
I am running a tiny 2 node LAN, Server 2003 and and XP Pro box. I have installed AD on the server, along with DHCP and WINS. Network connectivity is no problem; I can contact each box from the other (ping, pathping, tracert), I can send net send messages, but they do not see each other whan I browse the network.
Also:
I cannot map network drives;
When I set up new users in the users OU, they cannot log onto the network, because the XP box cannot join the domain.
Specs:
Server:medusa
Node:tron
Network:skynet.net (I know, but I had to think of one;-)
Static IP for server(DHCP,DNS,WINS):10.0.0.1
XP box is set to obtain ip from DHCP.
When I ping tron from medusa, name resolves to ip, as it should. When I ping medusa from tron, name does not resolve, but I can ping the ip (10.0.0.1).
After working on this for 4 hours on my day off, I am ready to slam my head against the closest flat and heavy object that I can find!
Thanks in advance for your help.
Tim

 

[Anarax]

Thanks Jeff, I'll try that when I get home today. I do remember trying that, and received an error, but cannot remember the specifics.
No Linux (yet) on the network, but thanks for the heads up. I won't trash the network, because I am picking up a lot of experience putting out these fires. By the way, this is the best forum I have ever been on (well, next to Cross-Dressing Penguins and the eskimos that love them); so informative. Also, in the IT world, there tends to be a great deal of "my kung-fu is better than your kung-fu" posturing; I have not noticed that at all here. I always strive to help anybody I can, and truely you all are an inspiration.....not that I want to pick out curtins with you or anything.. ;-)

Thanks again,
Tim

 

[GlenJohnson]

Thanks. Dave and Doug have always strived to keep the site professional. Keep us informed on what is going on. (Browsing can be found in services if my memory serves me correctly. There is also a registry entry for it.) Good luck.

Glen A. Johnson
If you're from Northern Illinois/Southern Wisconsin check out Tek-Tips in Chicago, Illinois Forum.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[Anarax]

It is in services, and at the risk of sounding like a quitter, I am not going to focus on network browsing since I only have 1 node, I will keep trying once in awhile though. I can access both boxes via thre UNC paths.
So now, I am getting used to AD; within such a small network, I am limited to what I can do (no replication, multiple DC's, Member Servers, etc.) but I am learning a great deal anyway.

I'm off now to check on any AD forums; I already have a question that I have not been able to find in any of the books that I have (or perhaps it was answered just not in way that clearified for me), thanks again!

Tim

 

[Anarax]

Wins prob again...
Hmmmm....that problem might be naming; the server name is medusa, but it also appears that the dhcp, dns, and wins server are also named medusa (or am I just looking at this too long and am instead looking at the actual DC's name?), because when I launch nslookup, I get the same mmessage:
DNS request timed out.
timeout was 2 seconds.
***Can't find server name for address 10.0.0.1: timed out
default server:unknown
address:10.0.0.1
UNC is ok, all clients can now see each other via ping name and ip.
I'm guessing that this has to be a dns problem, because when I check FQDN, neither the ip of 10.0.0.1 or the skynet.net domain exists, so I added it, ran nslookup and it says that domain cannot be found. From medusa and tron, I can ping skynet.net, and it resolves with the ip 10.0.0.1.
I'm quite sure that I misconfigured dns; although, ad is working fine. I can ping tron and medusa from each other, and their names resolve the correct ip's.

Since nslookup is not resolving, any suggestions? I will keep reading this weekend; thanks again

tim

 

[westmount]

Error Message: The procedure entry point DnsGetPrimaryDomainName_UTF8 could not be located in the dynamic link library DNSAPI.dll.

It looks like you may need to register this .dll by running this command form the command prompt.

regsvr32.exe dnsapi.dll

If this doesn't work

Go to the windows\config folder and rename netlogon.dnb to netlogon.old. After doing this, restart the netlogon service.

 

[Anarax]

westmount:
Are you sure that you replied to the correct post?

 

[westmount]

Anarax,

DNS request timed out.
timeout was 2 seconds.
***Can't find server name for address 10.0.0.1: timed out
default server:unknown

1. Make sure you have a rev look up zone for 10.0.0.1
2. Go to the windows\config folder and rename netlogon.dnb to netlogon.old. After doing this, restart the netlogon service.

See if this helps

Michael

 

[Anarax]

Westmount: Thanks, I have a rev lookup Zone, and I tried running nslookup and the output is correct now.
Not entirely sure what happened, but it appears all is well.
Thanks again for you reply.
Tim