Unable to Connect to Name Server

Question

I am attempting to add a CIFS server to the domain, but am not having any luck. This is a new Celerra and I'm thinking the network is not configured correctly. I get the following error in the server_log:

2008-09-04 20:48:39: SMB: 3: W2KgetInitialDC(1): No DC found domain=domain.com
2008-09-04 20:48:39: SMB: 3: dns_DCLookup::process:: Unable to get any DC from DNS for domain domain.com
2008-09-04 20:48:39: SMB: 3: DomainJoin::findServer: Unable to locate a Domain Controller in domain domain.com
2008-09-04 20:48:39: SMB: 3: DomainJoin::findServer: Unable to contact any domain controller in domain domain.com
2008-09-04 20:48:39: SMB: 3: DomainJoin::execute: cannot find DC for compname=naslab02
2008-09-04 20:48:39: ADMIN: 3: Command failed: domjoin compname=naslab02 domain=domain.com admin=admin password=********************** ou="ou=Computers,ou=EMC Celerra" init
2008-09-04 20:48:39: SMB: 3: getServerGUID failed for naslab01@DOMAIN.COM

I am also seeing the following message in the log on a consistent basis:

DNS: 3: 1: The DNS client is unable to connect to name server xxx.xxx.xxx.xxx : Connection timed out

I can ping the xxx.xxx.xxx.xxx server IP address with the control station but cannot ping it with server_ping.

Any ideas on how to narrow this down to an incorrect celerra or network configuration?

Chris

nandas · Accepted Answer

This is a time synchronization issue now. The time on the data mover differs by the time on AD too much exceeding the allowable clock skew.

Are you not using NTP? Please check that the data movers are configured with NTP server and the time on the data mover is correct.

You can also manually set the time on the data mover for the time being to check whether that helps.

You can do it from GUI or from command line using server_date command

Also note - server_date server_x timesvc will allow you to NTP configuration -
server_date server_x timesvc stats ntp command will show you the current status.

Hope this helps,
cheers,
Sandip

dynamox · Answer

have you tried server_ping command to ping your DNS server using the interface on your datamover ..same interface you are using for your CIFS server ?

Peter_EMC · Answer

You should check the network connectivity of the datamover.
Used interfaces (f.e. cge0)
Assigned IP-Addresses (are they on the expected interface)
connected network cables.
maybe routing
switch configuration, especially if you are using trunks
....

as long as server_ping is unable to connect your DNS server, you will not be able to join the compname.

nandas · Answer

Dynamox and Peter had already provided you the detailed information which might have helped you to resolve this.

However, few things from my end - may be repetitive one as already mentioned by Peter,
1) Ensure Routing is done properly - if you are using GUI - go to Network -> Route and add the proper routing entry - for default gateway add destination as 0.0.0.0 with proper Gateway IP Address
2) Ensure server_ping returns the Gateway IP Address as alive. Run the command server_ping server_x - you may also use the GUI ping tool. Once you confirm that the gateway is reachable from the data mover - ensure that DNS server is also available from the data mover.
Running a ping command on Control station uses the control station interface to reach the destination - but using server_ping command you use the data mover Interface.
3) If step 2 fails - check the physical connectivity - speed and duplex settings on the NAS devices and the switch ports where they are connected. Both end should match the configuration
4) If you have any logical configuration like trunking using Etherchannel or LACP and/or Fail safe Network - ensure that the configuration is done properly. You may consider deleting the logical configuration for troubleshooting purpose - instead use only one port on the data mover say cge0 (if the switch ports are configured in a port-channel - you have to remove that configuration on the switch end) and configure the IP Address on cge0 and check. This will help in eliminating any port-channel or trunking or fail safe network configuration issue.

Hope this issue will be resolved soon if not already solved

Thanks,
Sandip

nandas · Answer

What's that???? Is that only for Nick

dynamox · Answer

now Sandip ..do you really want a visit from a KGB agent ?

nandas · Answer

Good point Nick - I was sure that I missed something while posting my message

Thanks for compensating my mistake

On this VLAN issue - please ensure that while creating the Interfaces on the NAS end - you don't mention the VLAN ID in the VLAN Tag field. One of my customer recently did this mistake and they were having the network issue for days. The VLAN ID will be configured on the NAS end only when you use multiple VLANs on the same physical ports and use VLAN Tag with different IP Addresses (Interfaces) created on the same device. In that case the switch ports will be configured as VLAN Trunk port.
But in normal VLAN configuration - the switch port will have the VLAN membership only - no VLAN ID to be specified on the NAS.
Cheers,
Sandip

dynamox · Answer

nikolay as in Николаи ?sorry for off topic

nikolayp · Answer

Also, in case of using VLANs in your network, make sure you are using proper VLAN configuration on the switch port connected to the DMNick

pittperson · Answer

Ok, the initial problem is solved. It helps to have a default gateway configured! This message board is great for on the job training.

I am still unable to join the CIFS server to the domain. I'm getting the following errors in the log:

SMB: 6: No site defined for domain "lowes.com". Ensure that the Active Directory Site configuration includes the data mover's attached network.

KERBEROS: 5: Warning: send_as_request: Realm LOWES.COM - KDC 172.26.145.36 returned error: Clock skew too great (37)

Thanks,
Chris

nandas · Answer

That's great Chris. Thanks for the update and our absolute pleasure to be able to help you. Thanks to all.Cheers,Sandip

pittperson · Answer

Bingo, I've got a fully functional NAS lab! Thanks to everyone.Chris

Celerra

Unable to Connect to Name Server

Was this post helpful?