changing server name

I recently got a new sbs 2003 server and XP workstations. After the I setup the server and logged in with the XP workstations I noticed that the login was very slow about 2-3 minutes to complete. I changed the name of the server and when I did that the login was almost instant. But after that I received event errors about sharepoint services.... I am guessing it was just because I change the server name. My questions is could changing the computer name really speed up the login process that much, and was just changing it by going to my computer then properties and network id the right way to change it? Because I changed it back to get the errors to go away but now the login is very slow again. Thanks for the help.

Javier
Tue Apr 13 21:07:49 CDT 2004

How/what server name you changed? You shouldn't be able to do that (without
major surgery to your server!).

I would guess that you issue had to do with DNS. Where your workstations
obtaining a DHCP lease from the server? If so, are the DNS on the
workstation pointing ONLY to your SBS box?

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"sbs" <anonymous@discussions.microsoft.com> wrote in message
news:6E1355D7-B654-48F5-A4CC-2AE31AD68C2A@microsoft.com...
> I recently got a new sbs 2003 server and XP workstations. After the I
setup the server and logged in with the XP workstations I noticed that the
login was very slow about 2-3 minutes to complete. I changed the name of
the server and when I did that the login was almost instant. But after that
I received event errors about sharepoint services.... I am guessing it was
just because I change the server name. My questions is could changing the
computer name really speed up the login process that much, and was just
changing it by going to my computer then properties and network id the right
way to change it? Because I changed it back to get the errors to go away
but now the login is very slow again. Thanks for the help.

anonymous
Tue Apr 13 21:51:02 CDT 2004

The name that I changed was just the computer name. We had an old server, and then got a new one. I had both of the servers with the same name but they were never up at the same time. But of course I needed them up together at one time, so I changed the computer name of the new server SERVER1. When I did that the login to the new server was very speedy, but when I changed the computer name back to SERVER. It slowed back down again to a 2-3 minute login. If I change the computer name back to SERVER1. Is there other stuff that I need to change for everything to be happy again?

SuperGumby
Tue Apr 13 22:32:05 CDT 2004

without putting too sharp a point on it, we're wondering just how you
managed to access the server at all after the change.

Rule Number 1. You cannot easily change the name of a domain controller.

There is a renaming tool which can be used on Win2003 DC's, but cannot be
used if the DC is also an Exchange server.

STRONG SUGGESTION(s)
backup any data on the box, flatten it and re-install.
If you have any data in Exchange and can access the mailboxes, pull the data
into .pst files because I suspect you will be renaming certain aspects of
the network and will not be able to either directly mount the store nor
restore it from backup.

When creating your AD you were asked to supply a DNS name for the AD. Did
you use your public fully qualified domain name (eg. company.com), if so
this is wrong.

You might think about doing a couple of practice runs, install, discuss the
setup, flatten and do it again.

As the system is SBS2003, the conversation would be better if moved to
microsoft.public.windows.server.sbs, which is the SBS2003 group.

--
Mick Malloy
http://www.micropol.com.au

"sbs" <anonymous@discussions.microsoft.com> wrote in message
news:4B8105A6-6B9E-470A-930E-9D689FF42C86@microsoft.com...
> The name that I changed was just the computer name. We had an old server,
and then got a new one. I had both of the servers with the same name but
they were never up at the same time. But of course I needed them up
together at one time, so I changed the computer name of the new server
SERVER1. When I did that the login to the new server was very speedy, but
when I changed the computer name back to SERVER. It slowed back down again
to a 2-3 minute login. If I change the computer name back to SERVER1. Is
there other stuff that I need to change for everything to be happy again?

Chad
Tue Apr 13 22:39:17 CDT 2004

I second SuperGumby's STRONG SUGGESTION(s) . . .

--

Chad A. Gross - SBS MVP
SBS ROCKS!

SuperGumby [SBS MVP] wrote:
> without putting too sharp a point on it, we're wondering just how you
> managed to access the server at all after the change.
>
> Rule Number 1. You cannot easily change the name of a domain
> controller.
>
> There is a renaming tool which can be used on Win2003 DC's, but
> cannot be used if the DC is also an Exchange server.
>
> STRONG SUGGESTION(s)
> backup any data on the box, flatten it and re-install.
> If you have any data in Exchange and can access the mailboxes, pull
> the data into .pst files because I suspect you will be renaming
> certain aspects of the network and will not be able to either
> directly mount the store nor restore it from backup.
>
> When creating your AD you were asked to supply a DNS name for the AD.
> Did you use your public fully qualified domain name (eg.
> company.com), if so this is wrong.
>
> You might think about doing a couple of practice runs, install,
> discuss the setup, flatten and do it again.
>
> As the system is SBS2003, the conversation would be better if moved to
> microsoft.public.windows.server.sbs, which is the SBS2003 group.
>
>
> "sbs" <anonymous@discussions.microsoft.com> wrote in message
> news:4B8105A6-6B9E-470A-930E-9D689FF42C86@microsoft.com...
>> The name that I changed was just the computer name. We had an old
>> server,
> and then got a new one. I had both of the servers with the same name
> but they were never up at the same time. But of course I needed them
> up together at one time, so I changed the computer name of the new
> server SERVER1. When I did that the login to the new server was very
> speedy, but when I changed the computer name back to SERVER. It
> slowed back down again to a 2-3 minute login. If I change the
> computer name back to SERVER1. Is there other stuff that I need to
> change for everything to be happy again?

anonymous
Wed Apr 14 20:21:03 CDT 2004

Ok my last question is before I rebuild the server. Is when I am asked what the computer name, and the DNS name is what should I name it, because I am also buying the domain name so I don't want things to interfere with each other. So if I want www.domain.com when naming the server and the DNS name what should I name them. Thanks for the help I just don't want to have to rebuild the server yet again. Thanks

Chad
Wed Apr 14 20:23:55 CDT 2004

Standard convention is to use domain.local for your internal domain . . .

--

Chad A. Gross - SBS MVP
SBS ROCKS!

sbs wrote:
> Ok my last question is before I rebuild the server. Is when I am
> asked what the computer name, and the DNS name is what should I name
> it, because I am also buying the domain name so I don't want things
> to interfere with each other. So if I want www.domain.com when
> naming the server and the DNS name what should I name them. Thanks
> for the help I just don't want to have to rebuild the server yet
> again. Thanks

Javier
Wed Apr 14 20:41:10 CDT 2004

What Chad said... and if you plan to have Macs on your network at some point
then use .corp or .something-else that is not a tld.

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"Chad A. Gross [SBS MVP]" <chad.gross@laytonflower.nospam.com> wrote in
message news:OxU4ThoIEHA.3040@TK2MSFTNGP09.phx.gbl...
> Standard convention is to use domain.local for your internal domain . . .
>
> --
>
> Chad A. Gross - SBS MVP
> SBS ROCKS!
>
> sbs wrote:
> > Ok my last question is before I rebuild the server. Is when I am
> > asked what the computer name, and the DNS name is what should I name
> > it, because I am also buying the domain name so I don't want things
> > to interfere with each other. So if I want www.domain.com when
> > naming the server and the DNS name what should I name them. Thanks
> > for the help I just don't want to have to rebuild the server yet
> > again. Thanks
>
>

anonymous
Wed Apr 14 21:06:05 CDT 2004

Ok just to make sure. When running setup and SBS asks me what the computer name is. I can name it domain, and when AD asks me what the DNS name is I call is domain.local. So when I get my domain name www.domain.com and I use RWW or mail everything will work fine. Thanks

Javier
Wed Apr 14 21:42:28 CDT 2004

I actually don't think you should name the server "domain" (not even sure if
you could) there is really no need for that (and might create confusion).
Name the server something meaningful like "server" or "sbs". The AD domain
should be domain.local.

Just so we are clear-> when you get domain.com you still need to do a couple
of things (create the A and MX records at your ISP) in order to access
RWW/OWA/Mail/ect using something.yourdomain.com (or even www.domain.com...
if you really want that one, which most people don't).

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"sbs" <anonymous@discussions.microsoft.com> wrote in message
news:A9970537-BB8A-463E-9C41-8F06BE341519@microsoft.com...
> Ok just to make sure. When running setup and SBS asks me what the
computer name is. I can name it domain, and when AD asks me what the DNS
name is I call is domain.local. So when I get my domain name www.domain.com
and I use RWW or mail everything will work fine. Thanks

SuperGumby
Thu Apr 15 06:32:13 CDT 2004

using a server name of, ummmm, 'server' works for me.
using a DNS domain name of anything BUT your FQDN or any other top level or
subsidiary domain satisfies my criteria.

As has been mentioned, certain mac OS's have a problem with .local being
supplied by a windows DNS server. Mac OS programmers took a while to
implement a workaround. To compensate for their inadequacy you could
legitimately name your AD DNS domain .dog or .cat for all I care.

Either way, as Javier alludes, the internal AD DNS has little if any
significance to your access to the server from outside the AD DNS domain.


"Javier Gomez [SBS MVP]" <javier_gomez@remove.this.engineer.com> wrote in
message news:Og6oMNpIEHA.3240@TK2MSFTNGP12.phx.gbl...
> I actually don't think you should name the server "domain" (not even sure
if
> you could) there is really no need for that (and might create confusion).
> Name the server something meaningful like "server" or "sbs". The AD domain
> should be domain.local.
>
> Just so we are clear-> when you get domain.com you still need to do a
couple
> of things (create the A and MX records at your ISP) in order to access
> RWW/OWA/Mail/ect using something.yourdomain.com (or even www.domain.com...
> if you really want that one, which most people don't).
>
> --
> Javier [SBS MVP]
>
> << SBS ROCKS !!! >>
>
> "sbs" <anonymous@discussions.microsoft.com> wrote in message
> news:A9970537-BB8A-463E-9C41-8F06BE341519@microsoft.com...
> > Ok just to make sure. When running setup and SBS asks me what the
> computer name is. I can name it domain, and when AD asks me what the DNS
> name is I call is domain.local. So when I get my domain name
www.domain.com
> and I use RWW or mail everything will work fine. Thanks
>
>

anonymous
Thu Apr 15 07:11:08 CDT 2004

Thanks you thank you for all the help. I understand everything now I think, as far as creating the A and MX records at my ISP, how would I do that if I don't have a static ip. I was just going to use DynDNS or something like that on the server so I could use RWW and Mail. Is it still possible? I guess I just don't understand what the A and MX records would point to since my ip would be changing. Sorry again for all the questions.

Javier
Thu Apr 15 07:27:36 CDT 2004

When you setup your free account in dyndns you will get something like
yourdomain.dyndns.org. Ask your ISP to create an MX record that points to
yourdomain.dyndns.org.

If you want to have something like mail.yourdomain.com (or
remote.yourdomain.com, ect.)... then ask your ISP to create a CNAME record
for the hostname that you want to yourdomain.dyndns.org.

FYI-

1) MX records should always point to hostnames (not IP addresses)
2) A records point to IP addresses
3) CNAME records point to another hostnames.

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"sbs" <anonymous@discussions.microsoft.com> wrote in message
news:90DF3897-F91E-4F08-A181-25C02A73A92B@microsoft.com...
> Thanks you thank you for all the help. I understand everything now I
think, as far as creating the A and MX records at my ISP, how would I do
that if I don't have a static ip. I was just going to use DynDNS or
something like that on the server so I could use RWW and Mail. Is it still
possible? I guess I just don't understand what the A and MX records would
point to since my ip would be changing. Sorry again for all the questions.

Javier
Thu Apr 15 08:28:50 CDT 2004

All the records should be pointing to whatever.dyndns.org. The MX record
shouldn't point to mydomain.com. Although I assume that what you really
meant was that the MX record for mydomain.com will point to
whatever.dyndns.org... which is correct.

Just in case it wasn't that clear-> there is nothing forcing you create
mail.mydomain.com and remote.mydomain.com. You could use whatever.dyndns.org
(or even the IP address)... but is nicer to have everything under
mydomain.com.

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"sbs" <anonymous@discussions.microsoft.com> wrote in message
news:4E7F51E0-0A47-4F81-BECD-97F787E16717@microsoft.com...
> Ok so if I just want mail and remote on my server. Then I create have my
> ISP create cname that points to both mail.mydomain.com and
> remote.mydomain.com and then a mx record that just points to mydomain.com.
> Hopefully that is correct

anonymous
Thu Apr 15 11:31:04 CDT 2004

If I just get a static ip from my ISP would that be easier. Then would I not have to use DynDNS. That way I would just need the mx record and A record at my ISP pointing to my static ip. Thanks

Javier
Thu Apr 15 11:39:11 CDT 2004

Static IPs ara good... however just so we are clear:

The MX record should NOT point to an IP address... only to an A record. So,
even if you got a static IP you would need to create the A record
(mail.yourdomain.com) and then point the MX record to that A record.

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"sbs" <anonymous@discussions.microsoft.com> wrote in message
news:B4D0C425-813F-4DB8-B1E3-315C6F635096@microsoft.com...
> If I just get a static ip from my ISP would that be easier. Then would I
> not have to use DynDNS. That way I would just need the mx record and A
> record at my ISP pointing to my static ip. Thanks

Javier
Thu Apr 15 20:10:49 CDT 2004

I'm not sure what you just said. Could you please rephrase your question?

You shouldn't host your public DNS if that's what you are asking.

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"sbs" <anonymous@discussions.microsoft.com> wrote in message
news:24FC78AA-CD25-4C18-A3F8-7AAC77F4E121@microsoft.com...
> Perfect, so then I would setup DNS in windows, and that is how stuff going
to my static ip would no where to go after that since, I will be using a
public address on the server? Thanks

anonymous
Fri Apr 16 07:56:03 CDT 2004

What my question is, we are gettings DSL, and a static ip. My server's dns server's will be that of my ISP and the workstations of my server? We just have never used DNS before and now with sbs we are trying to use it to make mail and remote web work.

Javier
Fri Apr 16 08:25:36 CDT 2004

You SBS box has to run its own DNS. You put your ISP's DNS server as
forwarders in the server's DNS (this is all done when you run CEICW). Both
your server and the workstations point to the server for DNS. In any event
you don't have to worry much about this because DHCP will take care of the
workstations. You will be using 2 NICs? right?

This is what it should look like:
http://www.smallbizserver.net/DesktopDefault.aspx?tabid=52

--
Javier [SBS MVP]

<< SBS ROCKS !!! >>

"sbs" <anonymous@discussions.microsoft.com> wrote in message
news:5539ABCA-F19B-43E8-8D97-65A237F59F78@microsoft.com...
> What my question is, we are gettings DSL, and a static ip. My server's
> dns server's will be that of my ISP and the workstations of my server? We
> just have never used DNS before and now with sbs we are trying to use it
> to make mail and remote web work.