Need some help with an email i received

Here it is. Let me know what you guys think. I just dont know everything about windows networking, but why is sms.local not a valid domain? There is a lot of info in this email that I dont really understand, but I think a lot is bogus from what I have read here and other places on the net.

Thanks all.

Start email:

First, you have to design you Domain name space correctly. sms.local is
not a valid DNS name. You have to have a valid DNS name. The best way to
do is to setup and internal DNS server and external. The internal will
host your internal zone record and run zone transfer from the external.
Users will use query your internal DNS and your internal DNS will query
the external if it need to. The back drew is users will have to use 2
different logins to log to the active directory and to their email.

The other design is to use one Domain Name Space both externally and
internally. This can create problem because you have to open your
network to people to access your resource from the outside. If you don’t
do that, people will not be able to access your resource from the
outside and that what you are having now.

With win2003, you can rename the domain. To make your life easer,
uninstall the win2003SBS and install either win2000 or 2003, join the
domain, retain the FSMO server and a copy of the active directory.
Remove the projected win2003SBS from the domain and upgrade it to
win2003SBS. Rename the win2003SBS domain using domain renaming tool from
Microsoft.com.

As for the rest, use SSM console to create sites. The first site will be
created by default. Create a second site for insuractive. That should
take place after we establish the connection. Create OU for insuractive
and delegate the administration to me and give me the right to add
server to the domain. I will setup a win2000 server and promote it to DC
and join your domain. I will also have to create DNS to point to your
domain. You can then create separate policy for us. As for the proxy
server, that is another issue.

This is just a nutshell, we have to do much more research and tests
before we can actually do that.

I don't see anything bogus in there. The only thing that is not clear is what you and an apparent partner are trying to accomplish. Not sure I understand why he/she recommends switching from 2003SBS unless more than 50 ACL's will be required. It looks like you are attempting to set up some sort of WAN with a trusted site, but you just haven't given much to go on yet.

So, sms.local is not a valid DNS name? How am I logging on to my domain, because it is sms.local?

What is SSM console?

More explaination would be great.

No, sms.local is not a valid DNS name. It's sorta like requesting things internally. For example, Internally I can access my server by typing the http://myservername or http://www.mydomainname.com since internally either way gets me to the server. However, externally I can only get there from http://www.mydomainname.com

SMS is System Management Server:
http://www.microsoft.com/smserver/evalu ... efault.asp

I think the email was probably refering to the SMS console, not SSM console. (probably a typo)

//I think you still need to try to tell us a little more about what you are trying to accomplish.

Heres what we are trying to do. We have 2 locations and want to have one domain between the both. We have a direct t1 between the 2 locations. WE already have windows 2003sbs in place at one location. Considering that we can not have multiple domains on 2k3sbs, we just want to have another site connect to our site and be on our domain.


What you think?

Then I think you need to study up on trust relationships:
http://techrepublic.com.com/5100-6268-5169218.html

At least as best as I can tell from the email and your last post that is where I think you are headed.