Windows Server

2BPR · Guest

I have installed SBS 2003 several times now trying to get all the wizards
'right' and have noticed that early in the process I can display the
'companyweb' website pages without a problem ... I think this is true after
all the setup sets complete.

But, when I run Windows update and apply the 'critical updates' I can no
longer access the companyweb pages ... I have looked at the DNS table and do
see an 'alias' entry for companyweb ... not at Type A record.

I was able to ping companyweb from local PCs before running Windows update,
but am unable to ping companyweb after the Updates are completed.

The problem looks to me like the SBS2003 DNS server is no longer resolving
the companyweb entry ... local computers that ping the server using the
server name resolve the correct IP and get a response ... but fail to resolve
the name when using the name 'companyweb'.

I can get the companyweb to work properly again by adding an entry in the
local client PC 'hosts' file ... so, I'm pretty sure the root problem is a
DNS failure to resolve the name 'companyweb'.

I think the Windows Updates 'broke' the DNS service ... has anyone else seen
this and have an idea of how to 'fix' the problem?

Is there a 'fix'?

Marina Roos [SBS-MVP] · Guest

Hi,

Did you run CEICW? Can you post the ipconfig/all from the server and one
from a client?

--
Regards,

Marina
Microsoft SBS-MVP
One of the Magical M&M's

"2BPR" <2BPR@discussions.microsoft.com> schreef in bericht
news:40000FA5-5231-42E2-BA6B-5392DD47EA3A@microsoft.com...

BPR · Guest

Hi Marina! ... I've already 'fixed it', at least I think I did.

re:
Did you run CEICW? ... Yes, several times. This did not make a difference.

It works now. I edited the Server DNS settings myself and that seems to
have fixed it.

I opened the DNS link from the Administrative Tools menu.
In the DNS Tool I found only one CNAME entry for 'companyweb' in the highest
level folder for the server name ... it appeared to be correct to me. I
deleted that entry and re-added it at the same place, then I added another
CNAME entry in the subfolder with the server name. I then went to a client
PC and did a ping of the server with the name 'companyweb' ... it still
failed on that attempt.

I re-booted both the server and the client PC ... then pinged 'compnayweb'
from the client PC again, and it worked. There were no changes made to the
client PC. The only change that was made was to the DNS settings in the
Server.

Thanks for the offer to help, but I think I will leave it as is for a few
days.

I have other minor problems to work out too. I think the way to find out
what really happened is to pay attention to the 'granular' changes in the
behaviour of the 'companyweb' website as each of the setup, todo list, and
Windows update changes occurs. I think the problem was introduced by one of
the Windows Updates ... but cannot be certain. I do know it worked properly
after the 'setup' completed, before I started on the 'todo list' and before
I ran ( all, except DirectX & Media Player ) Windows updates.

I hope that someone at Microsoft will run through the steps too ... it will
probably be easier for them to find the problem than for me.

"Marina Roos [SBS-MVP]" <marina@roos.nodontwantspam.nl.com> wrote in message
news:O1cet00%23EHA.208@TK2MSFTNGP12.phx.gbl...

	Windows Server Forum Index -> Small Business Server 2003	All times are GMT
Page 1 of 1