RE: Remote DNS Issue

Hi lfheb,

Thanks for posting back.

to simply clarify your comprehension of FQDN, servername.yourdomain.local
is FQDN,A FQDN is a complete DNS name,Fully qualified domain name .

you can ping servername.yourdomain.local(using your own),or nslookup,enter
FQDN,view the result,can it be resolved to correct IP address?

Please disjoin and rejoin the domain on clinet 1 in office C, can it join
the domain successfully? that's important to troubleshoot the issue.if the
client 1 can join the domain and receive or send email normally, It should
have problem on client 2 and client 3 in office C. if client 1 fail to join
the domain,you should go to office B and join one computer to domain for
test purpose.

1.please capture the screenshot of the error message when you join the
client to domain. save as jpg file and send to me at v-jaluo@xxxxxxxxxxxxx

2.as you mentioned,you created a static DNS, pointing to the SBS in Office
A, do you mean you add an entry in hosts file?

3.can you ping FQDN name of the SBS server on office B and office C? what
is the result?


I appreciate your time. I am happy to be of assistance and look forward to
your reply.

Have a nice day!

Best regards,

Jacky Luo (MSFT)
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security
====================================================
PLEASE NOTE: The partner managed newsgroups are provided to
assist with break/fix issues and simple how to questions.
We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
====================================================
When responding to posts, please "Reply to Group" via your newsreader
so that others may learn and benefit from this issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
====================================================

.

Relevant Pages

  • Re: Win2K server and XP pro w/ SP2
    ... >>From the server, nslookup says "cannot find server name for address 192.168.1. ... nslookup yields the IP address of the DC and lists the DNS ... ping the problem workstation FQDN from DNS server. ...
    (microsoft.public.win2000.networking)
  • Re: Problem establishing 2 way trust on Windows 2003 Domain Contro
    ... > Domain B from Domain A. I can only ping the netbios name of the DC on ... DNS resoluton is not happening. ... other domain using it's fqdn. ... >I installed WINS on both DCs and am able to do netbios resolution. ...
    (microsoft.public.win2000.networking)
  • Re: All System Collections Not Updating
    ... No we cannot ping by FQDN. ... >> We are using DNS and WINS, but we are facing some issues with our DNS ... >> Checking configuration information for server: ...
    (microsoft.public.sms.admin)
  • Re: Cannot resolve ecx.images-amazon.com. Options
    ... While pinging from a Windows 2003 box, I get a host not found echo. ... On both servers in forwarders tab, DNS domain has All other DNS domains as ... When you ping those hostnames do you get an IP address returned in reply? ... Here's information on Usenet and using a newsreader: ...
    (microsoft.public.windows.server.networking)
  • Re: Error Joining Domain - Service Not Responding in Timely Fashio
    ... Make sure that the servers are able to ping ... > problem with your DNS or your DNS search scope. ... FQDN and NetBIOS name. ...
    (microsoft.public.win2000.active_directory)
Loading