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
resources on the network.
The issue here is that these are not Dial In clients, these are LAN attached
Domain member workstations, and they're getting private IP address.
DHCP server is up and running. Remote Access services are up and running.
ALL default wizard results.
Windows Small Business Server 2003 Standard. Windows XP Professional
workstations, all with latest service packs and patches.
We did have an electrical outage and the batteries did not hold long enough
to allow a proper shutdown, but doubt that may have anything to do with it.
I need a quick fix for this. Thanks for any assistance.
When I restart DHCP, it says it needs to be authorized, when I right-click,
my options are to unauthorize, and when I click that, it states The Parameter
is incorrect. After a few minutes it goes into green.
--
Merv Porter [SBS-MVP]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:6041C8E6-0547-4426...@microsoft.com...
I re-booted one of the workstations after doing an ipconfig /release, and it
still had the private address upon re-boot. When i did another release, and
then attempted a renew, it states that it cannot find a dhcp server and fails.
RRAS is now disabled and DHCP is running and active. I'll run the RRAS
wizard and try again.
If I use the Remote Access wizard from with the MMC, it does what it should
to create the service, but does not fix the issues.
If I use configure remote access from the server console, I get an error
message:
An error occurred while creating the Connection Manager configuration
package file. See Rraslog.txt, then rerun the Remote Access wizard.
Re-running the wizard after I saw the text did not help, unless I was
supposed to do something else besides seeing the file.
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
The only workaround I have now is to go around and assign IP Addresses to
30+ computers, 7 hours til 7am.
or does MS have a current patch, for all of the past issues, which we are
confronted with years later? Or does the re-install of SBS SP1 leave newer
files alone, and does it fix my current issue?
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.
Thank you for posting here.
According to your description, I understand that:
The domain computers cannot get the IP address lease properly.
If I have misunderstood the problem, please don't hesitate to let me know.
You can collect the MPS report on the SBS server for the analyzing. The MPS
Reporting Tool is utilized to gather detailed information regarding a
systems current configuration including event log. To collect the MPS log:
a. Please download MPS Reporting Tool from the following link:
(http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F
-88B7-F9C79B7306C0&displaylang=en)
b. Double click mpsreports_XXX.exe, and you will see a Command Window start
up.
c. Please type Y with the message of <Include the MSINFO32 report?
(defaults to Y in 15 seconds)[Y,N]?
d. When the tool is done you will see an Explorer Window opening up the
%systemroot%\MPSReports\Setup\Reports\cab folder and containing a
<Computername>MPSReports.cab file. Then send the package to me at
v-mi...@microsoft.com for further investigation.
If you have any questions or concerns, please do not hesitate to let me
know.
Best regards,
Miles Li
Microsoft Online Newsgroup Support
==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect
website:
https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx
Please post your EBS related questions to the EBS newsgroup on Connect
website:
https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx
If you want to use a newsreader other than a web forum to access these
newsgroups,
please refer to the following blog to apply NNTP password and configure a
newsreader:
http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-20
08-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================
Reinstall SBS 2003 SP1. Then download and run the SBS BPA.
--
Regards,
Marina Roos
Microsoft SBS-MVP
One of the Magical M&M's
www.smallbizserver.net
Take part in SBS forum: http://www.smallbizserver.net/Default.aspx?tabid=53
"Steve" <St...@discussions.microsoft.com> wrote in message
news:334A97BE-AAEF-4609...@microsoft.com...
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" <St...@discussions.microsoft.com> wrote in message
news:72CCA905-D30F-47DF...@microsoft.com...
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]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:7831B61B-787F-4174...@microsoft.com...
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
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" <St...@discussions.microsoft.com> wrote in message
news:C012C4B8-DF73-4EE0...@microsoft.com...
Shortened:
HKLM/SW/MS/SBS/ClientSetup
Also, The SBS SP1 stated that it installed successfully, then after re-boot
a message pops up, stating that there was an error that needed to be reported
to MS
szAppName: setup.exe szAppVer: 5.2.2893.0 szModName: SuiteHelp.dll szModVer:
5.2.2893.0 Offset: 0004ae45
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]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:BDD27D71-8306-42BE...@microsoft.com...
When I click on properties it prompts me that I do not have the required
permissions, then prompts me for username and password. The Administrator
credentials do not work. If I use the users name and password, it pauses,
then states: Multiple Connections to a server or shared resource by the same
user, using more than one user name, are not allowed. Disconnect all previous
connections to the server or shared resource and try again.
This tells me absolutely nothing.
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.
Did you re-run CEICW (not just the RAS Wizard)?
--
Merv Porter [SBS-MVP]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:F10051B1-EA3E-4820...@microsoft.com...
After I check to ensure that the services are all turned off on the
workstation, I will remove the test-client from the domain and try to re-join.
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" <St...@discussions.microsoft.com> wrote in message
news:43AF871B-482F-4A1B...@microsoft.com...
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]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:33E645B9-F8C9-4D44...@microsoft.com...
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\administrator.DomainName>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : ServerName
Primary Dns Suffix . . . . . . . : DomainName.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : DomainName.local
Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-1A-92-28-6E-F7
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.10.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.10.1.1
DNS Servers . . . . . . . . . . . : 10.10.1.2
Primary WINS Server . . . . . . . : 10.10.1.2
C:\Documents and Settings\administrator.DomainName>
--
Merv Porter [SBS-MVP]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:33E645B9-F8C9-4D44...@microsoft.com...
Flush and reset a client resolver cache using the ipconfig command
http://technet.microsoft.com/en-us/library/cc781949(WS.10).aspx
--
Merv Porter [SBS-MVP]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:1C110911-6E15-4764...@microsoft.com...
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5774
Date: 9/16/2009
Time: 2:50:57 PM
User: N/A
Computer: ServerName
Description:
The dynamic registration of the DNS record '_ldap._tcp.DomainName.local. 600
IN SRV 0 100 389 HostName.DomainName.local.' failed on the following DNS
server:
DNS server IP address: <UNAVAILABLE>
Returned Response Code (RCODE): 0
Returned Status Code: 0
For computers and users to locate this domain controller, this record must
be registered in DNS.
USER ACTION
Determine what might have caused this failure, resolve the problem, and
initiate registration of the DNS records by the domain controller. To
determine what might have caused this failure, run DCDiag.exe. You can find
this program on the Windows Server 2003 installation CD in
Support\Tools\support.cab. To learn more about DCDiag.exe, see Help and
Support Center. To initiate registration of the DNS records by this domain
controller, run 'nltest.exe /dsregdns' from the command prompt on the domain
controller or restart Net Logon service. Nltest.exe is available in the
Microsoft Windows Server Resource Kit CD.
Or, you can manually add this record to DNS, but it is not recommended.
ADDITIONAL DATA
Error Value: A socket operation was attempted to an unreachable host.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 ..
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5775
Date: 9/16/2009
Time: 2:50:58 PM
User: N/A
Computer: ServerName
Description:
The dynamic deletion of the DNS record 'DomainDnsZones.DomainName.local. 600
IN A 10.10.1.2' failed on the following DNS server:
DNS server IP address: <UNAVAILABLE>
Returned Response Code (RCODE): 0
Returned Status Code: 0
USER ACTION
To prevent remote computers from connecting unnecessarily to the domain
controller, delete the record manually or troubleshoot the failure to
dynamically delete the record. To learn more about debugging DNS, see Help
and Support Center.
ADDITIONAL DATA
Error Value: A socket operation was attempted to an unreachable host.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 ..
Event Type: Error
Event Source: WLBS
Event Category: None
Event ID: 35
Date: 9/16/2009
Time: 2:51:02 PM
User: N/A
Computer: ServerName
Description:
NLB Cluster 0.0.0.0 : Cluster mode cannot be enabled due to parameter
errors. All traffic will be passed through to TCP/IP. Restart cluster
operations after fixing the problem by running 'wlbs reload' followed by
'wlbs start'.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 0c 00 04 00 5a 00 ......Z.
0008: 00 00 00 00 23 00 07 c0 ....#..À
0010: 00 00 00 00 00 00 00 00 ........
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 12 02 04 00 00 00 00 00 ........
0030: 00 00 00 00 ....
Event Type: Information
Event Source: HHCTRL
Event Category: None
Event ID: 1904
Date: 9/16/2009
Time: 3:25:24 PM
User: N/A
Computer: ServerName
Description:
The description for Event ID ( 1904 ) in Source ( HHCTRL ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event:
ms-its:C:\WINDOWS\Help\rrasconcepts.chm::/sag_RRAStopnode.htm,
http://go.microsoft.com/fwlink?LinkID=45840.
I have been working with someone else on this and have yet to resolve this
issue.
I tried running this program and it states that 'Windows cannot access the
specified device, path, or file. You may not have the appropiate permissions
to access the item.'
It does not state what it is looking for.
--
Merv Porter [SBS-MVP]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:B7CE9566-CA6A-40EB...@microsoft.com...
I also deleted RRAS, DHCP and DNS and re-created them using the wizards,
without errors, re-ran the ICW, re-booted, and have no errors in the event
logs after booting.
I re-booted a test workstation, after doing a ipconfig/release and DNS
flush, and could not get an IP Address, because the domain controller/logon
service could not be found.
Everything else seems to work including RWW, email, etc. when IP addresses
are manually entered on the workstations.
This same issue was around back in 2006, after installing Windows 2003/SP2
on SBS 2003/Premium with the ISA 2004 service. The techs/blogger blamed it on
faulty ISA settings. This is a Standard version that does not include ISA
2004. Are the settings hidden somewhere in the IIS?
Do you have any Symantec products installed on the server (in particular
SEP)?
--
Merv Porter [SBS-MVP]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:410EDE75-0AEA-4113...@microsoft.com...
--
Merv Porter [SBS-MVP]
============================
"Merv Porter [SBS-MVP]" <mwport@no_spam_hotmail.com> wrote in message
news:Ol3HUMzN...@TK2MSFTNGP05.phx.gbl...
Doublecheck the Windows 2000 server (maybe turn it off) to make sure it's
not interfering.
Remove any hidden NICs
http://support.microsoft.com/kb/315539
--
Merv Porter [SBS-MVP]
============================
"Steve" <St...@discussions.microsoft.com> wrote in message
news:F25C4F7E-1436-477A...@microsoft.com...