Re: Sudden Issues with DHCP & Remote Access

Please post teh results of an ipconfig /all for the SBS server.

--
Merv Porter [SBS-MVP]
============================

"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:33E645B9-F8C9-4D44-B59A-CB5145C6D916@xxxxxxxxxxxxxxxx
I applied the Dependonservice values to both the workstation and server and
restarted, removed the workstation, restarted and tried rejoin, did not
work.
No DNS Servers configured for local system.
After assigning IP Addresses to the workstation I could rejoin the domain
without any issues.

The said workstation had all of the services , like RRAS, disabled, as it
is
on all other workstations.

Microsoft Update had nothing available and the BPA was clean. It did state
that the network drivers were more than 1 year old.

Broadcom Netxtrem Gigabit on Server. There are 2 but only one is
configured/enabled. We use an external firewall/router.

"Merv Porter [SBS-MVP]" wrote:

Are you running Gigabit network cards?

Event ID 5719 is logged when you start a computer on a domain, and the
computer is running Windows Server 2003, Windows XP, or Windows 2000
http://support.microsoft.com/kb/938449

After reinstalling SBS SP1, did you go to Windows up and download any
available updates, then re-run a scan with the SBS 2003 BPA to see if
there
were any issues that needed to be fixed?

You may want to unjoin/rejoin a workstation to the domain to see if that
corrects the problem.

--
Merv Porter [SBS-MVP]
============================

"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:43AF871B-482F-4A1B-9C4C-AAD7FF575188@xxxxxxxxxxxxxxxx
After completing the SBS SP1 Re-Install, correcting the Registry and
successfully running the wizards for RRAS and Internet, I tested a
workstation to see if they can connect using DHCP. They can no longer
find
the domain controller.

Event ID: 5719 Source: NETLOGON
No domain controller is available for domain DOMAINNAME due to the
following.
There are currently no logon servers available to service the logon
request.

BPA States that all is well

Current other known issues:
Suitehelp.dll problem after SBS SP1 install.
Bad RRAS Server shows up upon rebuild in RRAS.



"Merv Porter [SBS-MVP]" wrote:

In RRAS | Server Status, if you right click on the 'workstation' in
the
list
and choose "Remove from Directory", does this get rid of it?

--
Merv Porter [SBS-MVP]
============================


"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BDD27D71-8306-42BE-BE7B-BCAC20977889@xxxxxxxxxxxxxxxx
Merv,

You have been very helpful and I thank you very much.
I created the key and values as shown on the link you sent and the
RAS
wizard did it's job.

But, if I do a Rebuild Server List in RRAS, the workstation where I
disabled
and deleted everything still shows up in the list. If I delete it,
it
comes
back again when I do a rebuild. How do I get rid of it all together?


"Merv Porter [SBS-MVP]" wrote:

For ClientApps...

How to install Service Pack 1 for SBS 2003
(See section titled: Things that can happen during the
installation
of
Small Business Server Service Pack)
http://www.smallbizserver.net/Default.aspx?tabid=266&articleType=ArticleView&articleId=68

--
Merv Porter [SBS-MVP]
============================

"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C012C4B8-DF73-4EE0-A598-B80AEEFE65BA@xxxxxxxxxxxxxxxx
Hi again,

I downloaded and re-installed the SBS-SP1 and I get the same
error
as
before
when running the RRAS wizard from the server management console.
From other posts dealing with these messages it states that the
path
for
the
Clientapps folder is wrong in the registry, with instructions to
change
it. I
do not have the key or field described, which is supposed to
contain
the
path. I'm thinking about creating it, but don't know what it's
supposed
to
look like.

Extract of errors:

Running IExpress to build the package file returned OK
*** ERROR Cannot find the client setup key specifying the
destination
folder.

Specifying Error location (in CMAK) returned OK

*** CRRASCommit::CommitCMAK returned Error 80004005
*** CRRASCommit::CommitEX returned Error 80004005



"Merv Porter [SBS-MVP]" wrote:

You should be able to just reinstall SBS 2003 SP1 without doing
all
the
prelimary patching. Then re-run CEICW.

--
Merv Porter [SBS-MVP]
============================

"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7831B61B-787F-4174-8946-0396EF387C34@xxxxxxxxxxxxxxxx
Hi Merv,

I ran the BPA and it states that all is well, including the
install
of
SBS
SP1, I am in the process of re-downloading SP1 and will do
another
install,
see what happens.

As far as the symptons go, the workstations are looking
'elsewhere'
for
the
DHCP server, because they were somehow notified by the
workstation
that
it
was the new service provider, through Netbeui or something
other.
I
disabled
and deleted all of the services and protocols on the
workstation,
it's
just
getting the workstations to go back to looking in the correct
location,
the
SBS server.

The incompatibility statement was made after reading many of
the
bulletins,
noting that my SBS was suffering from many of them, but was
still
functional
because i didn't need to make any changes, etc. In my install
work
sheets
from my last rebuild a couple of years back, I have the SBS
SP1
as
the
final
update, so do not know why the issues were not resolved, or
maybe
a
recent
update undid one or the other SBS SP1 patches? We'll see?

I have all of the latest sharepoint and exchange service packs
installed.
Will I need to re-install those as well, or just the SBS SP1?



"Merv Porter [SBS-MVP]" wrote:

Hi Steve,

On the SBS server, install the SBS 2003 BPA and run a scan.
Fix
any
problems it finds. Then disable the DHCP service and RRAS and
re-run
CEICW.

Microsoft Windows Small Business Server 2003 Best Practices
Analyzer
http://www.microsoft.com/downloads/details.aspx?familyid=3874527A-DE19-49BB-800F-352F3B6F2922&displaylang=en

Now I have done a bunch of reading and find that the
server
2003
SP1&2
were
incompatible with sbs2003...

Not sure where you read this. WIndows 2003 SP1 adn SP2 are
compatible
with
SBS, but they cannot be installed on the SBS Server without
alos
installing
SBS 2003 SP1.

How to install Service Pack 1 for SBS 2003
http://www.smallbizserver.net/tabid/266/articleType/ArticleView/articleId/68/How-to-install-Service-Pack-1-for-SBS-2003.aspx

In the procedures, you can substitute:

Windows 2003 SP2 for SP1
Exchange 2003 SP2 for SP1
Windows Sharepoint Services SP3 for SP1

On the workstation that is now a 'server'... did she install
DHCP
on
the
workstation. I'd unplug that workstation until you've got
the
SBS
2003
server up and running again and then troubleshoot the
workstation
offline.

--
Merv Porter [SBS-MVP]
============================


"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72CCA905-D30F-47DF-9A58-748466F0D68C@xxxxxxxxxxxxxxxx
I think that I have found what may have caused the problem,
but
still
do
not
have a fix. One of the new users decided to turn her
workstation
a
server
for
connecting other computers, installed old netbeui protocols
and a
slew
of
other old stuff into a network connection. This somehow
corrupted
the
sbs
function and when i went to run the wizard, found that the
server
could
not
run it.

How do I get RRAS wizard to run again, and how do I get the
workstations
to
recognize the DCHP function on it? I'm worried that the
older
fixes
that
applied may cause damage if applied today.

In one fix there were instructions to change the path of
the
clientapps
folder in the registry. The registry entry describing where
the
ClientApps
folder is, is not even there. I did not want to create it
because
there
was
no documention stating that I should, only to change it.




"Merv Porter [SBS-MVP]" wrote:

Something to try... Stop the DHCP service, disable RRAS
(from
within
the
RRAS console), then re-run CEICW and reboot the
workstations.

--
Merv Porter [SBS-MVP]
============================


"Steve" <Steve@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6041C8E6-0547-4426-9F8C-3FD47A4AAC00@xxxxxxxxxxxxxxxx
Event ID: 20169 Source: RemoteAccess

Unable to contact a DHCP Server, The Automatic IP
Address
169.254.45.156
will be assigned to dial in clients. Clients may not be
able
to
access


.

Loading