SCOM 2007R2 Gateway Issue.

We always facing issue on one of the gateway which are to communicate with SCOM master server. In the event log, we only found the event 21023 and error 2000 as below. Everytime this issue occur, we have to restart the SCOM serivces on the SCOM master server
which causing the monitoring outage. Anyway to fix it permanently without have to restart the SCOM serivces on the SCOM master server?

please try this
1.Stopped the System Center Management Service
2.Deleted the Health Service Stated folder
3.Started the System Center Management Service
http://blogs.technet.com/b/thomase/archive/2010/10/29/event-id-21023-management-server-not-downloading-configuration-files.aspx
Roger
tried them before but no luck by perform the those steps. we never try to reboot the gateway servers but we only can solve them by restarted the SCOM services on the SCOM master server which will cause the monitoring stopped for period of time

Similar Messages

Data Warehouse issue after deploaying Server 2012 MP in SCOM 2007R2

Hi all,
I have recently installed Server 2012 MP in SCOM 2007R2. But now I get DataWarehouse warnings that the specified schema name "sdk" either does not exist or I do not have permission to use it.
It's event 31565 with source Operations Manager Health Service Modules
Can anyone help me?
Failed to perform Data Warehouse component deployment operation:Install; Component: Script, Id: '79c157e5-9aa8-7045-d0b8-19e2d713d6c7',Management Pack Version-dependent Id: '01f04523-ee6c-1f3e-08a1-a108dda43507';Target: Database, Server name: 'SQL\SCOM,10100', Database name: 'OperationsManagerDW'. Batch ordinal: 0; Exception: The specified schema name "sdk" either does not exist or you do not have permission to use it.
Best regards,
Oliver
Gruss Oliver Scholl

Hi Gruss,
Was there any resent permission change on the SQL server or the Data warehouse ?
Has your Data reader and writer account Sys admin permissions on the SQL application ?
Also is the reporting tab working and are the reports related to this and other management packs working ?
Gautam.75801

Migration from SCOM 2007R2 to SCOM 2012R2

   Hello to all. I have a SCOM 2007R2 environment with 3 servers:
   1- SRV #1 has RMS and WebConsole roles.
   2- SRV #2 has Gateway role.
   3- SRV #3 is Shared SQL Server with SCOM DB + Reporting roles.
   This deplyoment monitors ~600 and I´m planning to take it to SCOM 2012 R2.
   Question 1:
   I already read several articles but for me is not clear if I can just insert SCOM 2012 R2 Management Server and Gateway on a existing 2007R2 Management Group (of course that it already has a RMS), begin migrating agents to it
and at the end decomission SCOM 2007 R2 Servers. All articles that I read mention just two options:
a) Side-by-Side migration (install SCOM 2012R2 on a NEW Management Group and begin agent migration to this NEW Management Group) and
b) Upgrade (run in-place upgrade to SCOM 2012 R2 if current SCOM 2007R2 attend SCOM 2012 R2 requirements - if not, install new SCOM 2007R2 servers with supported requirements and run upgrade in-place). Considering this info.,
is it possible to run SCOM 2007 R2 --> 2012 R2 migration as I previously mentioned?
   Question 2:
   Does SCOM 2007R2 agent reports to SCOM 2012R2 Management Servers?
   Question 3:
   Is it possible to run direct migration (not pass through SCOM 2012 - withouy R2) using the path SCOM 2007 R2 --> SCOM 2012 R2 path?
   Regards, EEOC.

Hi,
Q1:
It is suggested to do side by side migration, and for upgrading from System Center Operations Manager 2007 R2, please refer to the below link:
http://technet.microsoft.com/en-us/library/hh476934.aspx
Q2:
You can multi-home the clients to both SCOM 2007R2 & 2012, but 2007 agent can’t communicate with a SCOM2012 MS.
Q3:
If we use side by side migration, then we don't need to pass through SCOM 2012, but if we use in-place-upgrade, then we must follow the below path:
SCOM 2007R2 CU4+ >
SCOM 2012 RTM > SCOM 2012 SP1 > SCOM 2012 R2
More details:
http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx
Regards,
Yan Li
Regards, Yan Li

IPv4 Gateway Issue? - HP LaserJet 400 M401dn / 400 MFP M425dn

Hello,
I work in healthcare and in our environment we have mostly HP LaserJet printers. Within the last 6 - 12 months we have started using some HP LaserJet 400 M401dn and HP LaserJet 400 MFP M425dn printers. They all have been updated with the latest firmware (20 printers) and connect to the network via ethernet using IPv4. We are having an issue when trying to print to them from a specific application. It's only happening on these particular models. All other HP LaserJet printers DO NOT have this problem (HP LaserJet 2015dn, 2055dn, P4015dn, 600 M602dn). The application is a telnet client using SSL that connects to a server. This server is on a different subnet (128.1.x.x) than the printers (10.92.x.x) that the clients print to.
It is possible to 'ping' the printer within the application using the printer hostname or IP address. The problem is, there are times when the printer status says 'Ready', and we can ping the printer from within the Windows operating system (Win7 Pro), but we cannot ping it via telnet SSL client. There is no response. The result is, we cannot print from the application to these printers. This problem isn't consistent either. There are times when it does work!
If we assign the printer to the same subnet as the application server, the issue appears to go away. Unfortuantely this is not a feasible permanent fix for us as the printers need to remain in their current subnet.
Sleep Mode is disabled on all of these printers. IPv4 settings are all correct and have been verified by various IT staff.
We believe there is an IPv4 gateway issue within the NICs on these printers. Has anyone ever had a similar issue? Are there any other additional details that I should provide which might help resolve this issue?
Regards.

To start off, the issue you are having may be caused by the softare you are using or the HP software. I am gonig ot to do some investigating to find out. I will want to to make sure that the softare is the most current version, follow the link below and reinstall if necessary (do not rely upon the CD-ROM):
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?prodNameId=5096244&lang=en&cc=us...
Then if it is the same or you are still having issues I would recommend trying to use the PCL6 drivers for this. They offere a broader support to some of the more code specific programs :
http://h20000.www2.hp.com/bizsupport/TechSupport/ProductList.jsp?locale=en_US&taskId=135&prodTypeId=...
Run through that and let me know how it goes, I'll get right back in touch with you!
-Spencer
PS :: Can you print to this printer from other programs? Have a wonderful day!

SCOM 2012 Gateway fails to communicate - Certificate Problem?

Hello SCOM Guru's
I wonder if someone out there may be able to help.
I have two (non-trusted) domains - both hosted in
Azure. See graphic below (a picture paints a thousand words!)
Just to put some context around the diagram - I have a two domains, the left-hand side contains the SCOM MS and the right-hand side is a non-trusted domain hosting the SCOM GW. The idea is that I want computers (agents) from the right-hand side domain to
be able to talk back to the SCOM MS vai the SCOM GW.
In a nutshell I have followed some great 'how to' guides - for instance:
http://blogs.technet.com/b/pfesweplat/archive/2012/10/15/step-by-step-walkthrough-installing-an-operations-manager-2012-gateway.aspx
After hours of messing around I still cannot get my Gateway Server to talk successfully back to the SCOM Management Server in the other domain. I have deployed my own Certificate Authority and followed documentation to put the relevant Certs on both
servers. I have checked all Certs and they report 'The certificate is OK'.
Also I can confirm that the MOMCertImport tool was run on both the SCOM MS and SCOM GW server (I did the MS 1st and GW 2nd) - both returned a 'Success' cmd prompt. I have also rebooted both servers - to restart all relevant SCOM Services.
On the Azure VMs I have allowed TCP 5723 on both servers. Additionally, the SCOM MS can resolve the SCOM GW server in the other domain via a HOSTS file entry (and vice-versa). I have tested connectivity using
telnet <FQDN> 5723 (both ends seem to connect). No internal Windows Firewalls are enabled on any servers.
The cluster of errors reported by the
SCOM Gateway server are (first to last):
20057: Failed to initialize security context for target MSOMHSvc/SCOM-01.DOMAIN.local The error returned is 0x80090303(The specified target is unknown or unreachable). This error can apply to either the Kerberos or the SChannel package.
21001: The OpsMgr Connector could not connect to MSOMHSvc/SCOM-01.DOMAIN.local because mutual authentication failed. Verify the SPN is properly registered on the server and that, if the server is in a separate domain, there is a full-trust
relationship between the two domains
20071: The OpsMgr Connector connected to SCOM-01.DOMAIN.local, but the connection was closed immediately without authentication taking place. The most likely cause of this error is a failure to authenticate either this agent or the
server . Check the event log on the server and on the agent for events which indicate a failure to authenticate.
The same events repeat every 15 mins in the Operations Manager event log - and thus the SCOM Gateway remains 'Not Monitored'.
I don't get any relevant Events logged from the SCOM MS side - I guess cos it's not even got that far / authenticated?
I'm sure this is a Certificate type of problem but I'm really not sure where I go from here - any suggestions?
Many thanks
Darren

Hi,
Check this post:
Solving the Gateway 20071 event
http://michelkamp.wordpress.com/2012/01/05/solving-the-gateway-20071-event/
and this: Event ID 21001 and 20057 on SCOM agents - duplicate SPN:
http://blogs.technet.com/b/kevinholman/archive/2011/08/08/opsmgr-2012-what-should-the-spn-s-look-like.aspx
Similar answer has been provided by DKTOA Here:
https://social.technet.microsoft.com/forums/systemcenter/en-US/05019b70-73a3-4a37-993b-66b607f3c222/scom-2012-gateway-server-isses-20057-21001-20071-ids
Did it solve your problem?
Regards
Jure
Jure Labrovic | Blog

I get 2 error's when i install scom 2007r2 in my lab servers.

I get 2 error's when i install SCOM 2007r2 in my lab servers.Many people have got a similar error like this but not the exact one which i got. I also RAN this setup provided by MS to check SCOM traces and it removes and the application says no traces were
found.
Can any one suggest me what can i do to over come this error.
Errors:
2nd:
Tool i used for finding traces:
System Center Operations Manager R2 Admin Resource Kit
Result: No product data was found.

Hi,
Did you use domain admin to login the server to install SCOM 2007? And we may also need to login as domain admin on the SQL server, give its SA permission.
Please go through the below two links and follow them to install and configure your SCOM:
Operations Manager 2007 Deployment Guide
http://technet.microsoft.com/en-us/library/bb419281.aspx
Operations Manager 2007 R2 Installation and Configuration (step by step) – Part 1 “Pre-Build”
http://blogs.technet.com/b/meamcs/archive/2011/01/09/operations-manager-2007-r2-installation-and-configuration-part1-pre-build.aspx
Hope this helps.
Regards,
Yan Li
Regards, Yan Li

Difference between Scom 2007 and Scom 2012 Gateway server setup.

Hi All,
Greetings!!
I would like to know the differences for gateway server setup in Scom 2007 and 2012 versions..
Are there any changes in the data collection or in the configuration? and also the prerequisites for it.
Please let me know these info..
Regards,
Gokul

There is no great different in settng up gateway server in SCOM 2007 R2 and SCOM 2012. As summary, it requires
1.Request certificates.
2. Import those certificates into the target computers by using the MOMCertImport.exe tool.
3. Distribute the Microsoft.EnterpriseManagement.GatewayApprovalTool.exe to the management server.
4. Run the Microsoft.EnterpriseManagement.GatewayApprovalTool.exe tool to initiate communication between the management server and the gateway
5. Install the gateway server.
However, the prerequisites has different between SCOM 2007 R2 and SCOM 2012
SCOM 2007 R2 gateway server support folloiwng OS
Windows Server 2003 Standard Edition with Service Pack 1 (SP1)
Windows Server 2003 Standard Edition with Service Pack 2 (SP2)
Windows Server 2003 Standard x64 Edition with SP1 or SP2
Windows Server 2003 Enterprise Edition with SP1
Windows Server 2003 Enterprise Edition with SP2
Windows Server 2003 Enterprise x64 Edition with SP1 or SP2
Windows Server 2003 R2 Standard Edition with SP1 or SP2
Windows Server 2003 R2 Standard x64 Edition with SP1 or SP2
Windows Server 2003 R2 Enterprise Edition with SP1 or SP2
Windows Server 2003 R2 Enterprise x64 Edition with SP1 or SP2
Windows Server 2008 Standard 32-Bit with SP1 or SP2
The 64-bit edition of Windows Server 2008 Standard with SP1 or SP2
Windows Server 2008 Enterprise 32-Bit with SP1 or SP2
The 64-bit edition of Windows Server 2008 Enterprise with SP1 or SP2
Windows Server 2008 Datacenter 32-Bit with SP1 or SP2
The 64-bit edition of Windows Server 2008 Datacenter with SP1 or SP2
Windows Server 2008 R2
Windows Server 2008 R2 with SP1
SCOM 2007 R2 gateway server
CPU :2.8 GHz or faster
Memory: 2 GB of RAM or more
available Space: 20 GB of available hard disk space
NET Framework 2.0
Microsoft Core XML Services (MSXML) 6.0
SCOM 2012 Gateway server
Disk space: %SYSTEMDRIVE% requires at least 1024 MB free hard disk space.
Server Operating System: must be Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 Core Installation or Windows Server® 2012 R2.
Processor Architecture: must be x64.
Windows PowerShell version: Windows PowerShell version 2.0, or Windows PowerShell version 3.0.
Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 is required for the management server.
.NET Framework 4 is required if the Gateway server manages UNIX/Linux agents or network devices.
Roger

SCOM 2007R2 unix/linux service monitor setup - cannot discover service under /etc/init.d

SCOM 2007R2 unix/linux service monitor setup - cannot discover service under /etc/init.d

Can you give a few more details on what you have tried, and what didn't work for you? Were you stepping through the wizard to monitor a Linux/UNIX service and something went wrong? Or did you successfully create the service monitor in the wizard, but it
didn't trigger if the monitored process terminated?
Michael Kelley, Lead Program Manager, Open Source Technology Center

SCOM Certificates / Gateway servers

I recently worked an issues with a Gateway server having errors ids 20057, 21001 and 20071. The problem seems to always be related to certificates used to authenticate.
My general question is about these certificates since I cant seem to find a clear answer in the MS documentation.
What kinds of certificates are needed?
Should they be Server authentication certificates, Workstation, Operations Manager Certificates (probably the same as server certs)?
Do they need to be created from the same template?
does the Management server and Gateway or agent need the same kind of certificate and should these be in the personal store always?
Thanks Lance

First of all, SCOM communication is based on Kerberos authentication and gateway machine is installed on the domain which has no two-way trust to management server domain. As a result, a certificate is deployed to gateway server. In order to obtain a certificate,
you need a CA and then apply a computer certificate. For detail on how to deploy certificate, pls. refer to Jim Moldenhauer's Blog:
http://jimmoldenhauer.blogspot.hk/2012/11/scom-2012-install-and-configure-gateway.html
Roger

RDS and Gateway issues: Cannot get remoteapps to run without opening port 3389 on firewall

I am testing the setup of a small RDweb server to host QuickBooks for some remote sales users (4 users). For the most part, I have everything installed on one virtual server (using 2012r2 "Quick Start" session host deployment with the additional
Licensing and Gateway server roles added to the same server).
Everything works excellent with one exception. External clients cannot launch published apps without having port 3389 open on the firewall, even with the gateway role installed and the 'Deployment Properties' set to use the gateway. They can properly connect
to the RDweb site and view the published apps. The only way it works is open the firewall port (at which time I can disable the gateway or leave it configured and it works either way). Internally, everything works accordingly. I have followed the steps outlined
on many sites and have combed though the forum here to no avail.
Error received (summarized but is a well documented error):
remote desktop can't connect to the remote computer: 1- Your user account is not listed (it actually is) or 2- You might have specified the remote computer in NetBios format . . etc.
This is an existing SBS 2011 environment with additional virtual servers setup to host QuickBooks as outlined below:
Current setup:
Used Quick Start to install Remote Desktop Services in hosted sessions mode
Installed the additional roles for Licensing and Gateway server on same server
Configured wild card public certificates on all four services (Connection Broker(2), Web Access and Gateway)
Configured internal DNS to properly lookup our external FQDN of this server (ex. quickbooks.contoso.com points to quickbooks.contoso.local
One thing I noticed (just now) when I launch a published app and the firewall has port 3389 closed, a dialog box pops up directly after launching the app that warns about running a RemoteApp program and mentions the Remote Computer and the Gateway Server
as both the same (which it is); however, I would have assumed one would have listed the internal server's name while, instead, both are listed as the external FQDN. Either way, internal DNS should still allow it to properly route . . no? I don't know . . I'm
sure I am just missing something in a routing configurations somewhere. The gateway service is not properly looking up the RDweb service and then seeming not routing the encapsulated RDP session through HTTPS. . .. is my guess . .
I was reading about the "set published name" commandlet; however, I am not experiencing a certificate name mismatch; however, the certificate name does show up as *.contoso.com versus the actual name. I may just be grasping as straws now . . :)

Ok, while I was in the server and looking over the BPA scans: "The Remote Desktop Gateway (RD Gateway) server Secure Sockets Layer (SSL) certificate may not have a valid certificate subject name." This may be due to it showing up as *.companyname.com
versus quickbooks.companyname.com. Anyhow. .. on to the list of actions above:
Changed RD RAP from "Select Active Directory" group to "Allow any network resource" and tested with port 3389 closed on firewall:
Worked. Initially it did not as I had used a custom shortcut created from earlier; however, after logging into the RDweb site again, the application loaded fine now (after the RD RAP change)
No error message appeared; however, I did notice that for a split second, the word Error did appear in the browser's tab title, but only very shortly. The app launch does take a bit longer too now (about 10-15 seconds, up from about 4 seconds with the port
open). This, I could care less about so long as we are properly forwarding the traffic through the gateway.
As for log entries, I had spend quite a bit of time in there and only had minor issues with loading user profile setting taking too long and policy settings preventing the redirection of USB devices. Looking again, no issues still. Just a bunch of informational
entries where I would connect before (and disconnect) but only with the port on the firewall open; otherwise, there was not an entry corrolating to when I would receive an error before. Now though, I am connecting after the RD RAP change and logs are showing
connections even with the port closed. These are in "operational", the "admin" log only shows the update to the RD RAP configuration.
Yes, the LAN's DNS server does relay the lookup information for my public FQDN as the local LAN address. No need for a local host record.
I have now added a new rule in our firewall to allow and forward UDP port 3391 traffic to the internal server hosting remote services
Thank you very much for your assistance on this matter. The RD RAP rule was default built during the creation of this services. Why is the resource not cross-referencing AD security groups? I could have sworn I created a group for that . . .

SCVMM and SCOM 2012 Integration Issues

Hello, I have integrated SCOM 2012 RTM and SCVMM 2012 RTM and am having lots of issues that were not present with 2007/2008 family integration. For starters, my SCOM environment manages multiple untrusted domains, etc. When enabling VMM integration
I now get hundreds of alerts about "Unable to verify Run As Account", stating that is cannot login as the VMM service account for all clients that don't live in same domain as SCVMM server. For starters why do my physical servers, and all VMs need
to be distributed with this account? The alert is also expected logically, because this is impossible to distribute a Run As account to every agent in a multi-domain untrusted environment. Also according to this configuration, the Virtual
Machine Manager Connection Account created in SCOM is set to less secure (distributed to all agents), which is why the alert is coming up; additionally less secure setting is typically bad practice. Why does SCVMM do this by default? Can it be
changed? What are options here? It seems to me only the SCOM management server should need this Run As account, not every agent? Thoughts on this? Thanks!

I'm running SCVMM 2012 R2 and OpsMgr 2012 R2. I have the integration setup and have had the same issue with the RunAs account logging on to workgroup computers.
I tried changing the account distribution to More secure and only targeting my two management servers and the VMM server. I also changed the profile so that it targeted only the Windows Computer object for the same three servers. I came in this
morning and I do not have the "Run As Account Could Not Log On" message anymore on the workgroup computer, but now I have an alert "VMM Agent Not Monitored By Operations Manager" for the VMM server. I look at the Health Explorer and see that the agent
is reachable but its not being monitored.
I tried changing the RunAs profile back to "All Targeted Objects" but monitoring still didn't restart. Then I tried restarting the OpsMgr agent and then the VMM agent, but still the status did not change. Now, I have just set the account back
to Less secure and have again received the warning from the workgroup computer about not being able to log on. I'll wait a little longer to see if the VMM server begins to be managed.
Any experience with this?

OWSM gateway issue

Hi,
Oracle SOA suite version: 10.1.3.1.0
I started the OWSM with the quick start tutorial. Instead of using the time service I used another service deployed. When I started I had created a gateway which I then deleted.
Then I created a new gateway and done the steps specified by the tutorial.
The problem is occuring when I try to access the proxy wsdl url.
It giving an error :-
Oracle Web Services Manager Gateway C0003001: Cannot find WSDL for service "SID0003006"
The component ID of the Gateway is C0003001 (which I had deleted), the component ID for the gateway should be C003002..
What can I do to fix this issue?
Thanks and Regards,
Sashwat

Hi Mathias ,
Oracle SOA suite version: 10.1.3.1.0
I started the OWSM with the quick start tutorial. Instead of using the time service I used another service deployed. When I started I had created a gateway which I then deleted.
Then I created a new gateway and done the steps specified by the tutorial.
The problem is occuring when I try to access the proxy wsdl url.
It giving an error :-
Oracle Web Services Manager Gateway C0003001: Cannot find WSDL for service "SID0003006"
I have updated the gateway.component.id with C0003007 the next possible component ID in gateway-config-installer.properties located in OH/owsm/config/gateway and then redeployed the gateway successfully.Now I am getting a little bit different error :
Oracle Web Services Manager Gateway : Cannot find WSDL for service "SID0003007"
I deleted all other gateways and this is the only gateway remaining.
Please tell me another way to fix this.
Thanks and Regards,
Vargab Pathak
Message was edited by:
Vargab

Lion Server Gateway Issues

Hello,
I have a perplexing issue with both my own server and a client's server. In both cases I am trying to configure a Lion server as a gateway (Firewall, DNS, DHCP, NAT) and I am unable to get the services working consistently. If I am able to get my server(s) functioning as gateways I lose DHCP any time the service restarts.
I have been able to reproduce this issue on two separate networks in two different locations on two separate static IPs with both a Mac Pro and a Mac Mini.
1. I setup reverse DNS with both ISPs.
2. I began with a fresh 10.7.0 server installation from the recovery partition, the I configured my static IP address and FQDN during the Setup Assistant, rDNS checked out fine, and after the assistant was done I immediately ran updates.
3. After restarting I configured my DNS. I setup a machine address for the server and linked my FCDN to my static IP address.
4. I downloaded Server Admin Tools 10.7.2 from http://support.apple.com/kb/DL1457 and installed them. I ran Software Update again to make sure the system was completely up to date.
5. Using Server Admin I enabled NAT and ran the Gateway Setup Assistant.
6. After running Gateway Setup Assistant the LAN was unable to obtain IP addresses via DHCP. Devices connected to the LAN had self-assigned IP addresses.
7. I opened the Firewall for both "any" and "192.168.1.1-net" by allowing both IP address groups to allow all traffic.
Still no luck. A little Googling and I found http://support.apple.com/kb/TS3887 - "Unable to connect to the Internet after running NAT Gateway Setup Assistant".
8. I follwed the instructions in TS3887 and my LAN was still unable to obtain an IP address via DHCP.
After 3 days of trial and error I have found that my DHCP settings are being reset whenever I start/stop/start DHCP services. Whenever I restart the DHCP service I get one of the following error message sequences in /var/system.log:
Jan 25 16:19:43 server servermgrd[71]: servermgr_dhcp:bootp config:Error:Unable to read configuration file - error 2 (No such file or directory)
Jan 25 16:19:43 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created default configuration file
Jan 25 16:19:43 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created 2 default subnet records
or
Jan 25 16:15:50 server serveradmin[4843]: servermgr_dhcp:bootp config:Error:Unable to read configuration file - error 2 (No such file or directory)
Jan 25 16:15:50 server serveradmin[4843]: servermgr_dhcp:bootp config:Notice:Created default configuration file
Jan 25 16:15:50 server serveradmin[4843]: servermgr_dhcp:bootp config:Notice:Created 1 default subnet records
As it turns out, something is overwriting /etc/bootpd.plist:
sh-3.2# ls -al /etc/bootpd.plist
-rw-r--r-- 1 root wheel 1536 Jan 25 16:20 /etc/bootpd.plist
sh-3.2# serveradmin stop dhcp
dhcp:state = "STOPPED"
sh-3.2# ls -al /etc/bootpd.plist
-rw-r--r-- 1 root wheel 1132 Jan 25 16:47 /etc/bootpd.plist
I have no idea why Server Manager believes that /etc/bootpd.plist does not exist but I began to notice some strang behavior while working on the problem.
- While DHCP was turned off in Server Admin devices on my LAN were often able to obtain IP addresses through BootP.
1. I could use Server Admin to start DHCP but it would fail and create two new subnets, one for my WAN and one for my LAN. Although no subnets were enabled decices on my LAN would obtain IP addresses through BootP. I could then start DHCP with none of the subnets enabled.
2. If I enabled the LAN subnet and restarted DHCP Server Admin would fail to start DHCP. I could try again and DHCP would start with no subnets enabled.
3. If I stopped DHCP the system would again reset my /etc/bootpd.plist and I woudl be left with one subnet for my LAN. This subnet was enabled by default.
4. If I stopped DHCP the system woudl once again reset my /etc/bootpd.plist and I would have one subnet for my WAN. This subnet was disabled by default.
And then this loop would continue in slightly different variations indefinately. Here is what my log looks like while this is happening:
Jan 25 17:09:04 server servermgrd[71]: servermgr_dhcp:bootp config:Error:Unable to read configuration file - error 2 (No such file or directory)
Jan 25 17:09:04 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created default configuration file
Jan 25 17:09:04 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created 1 default subnet records
Jan 25 17:09:13 server servermgrd[71]: servermgr_dhcp:bootp config:Error:Unable to read configuration file - error 2 (No such file or directory)
Jan 25 17:09:13 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created default configuration file
Jan 25 17:09:13 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created 2 default subnet records
Jan 25 17:09:25 server bootpd[5726]: server name server.perfecteden.com
Jan 25 17:09:25 server bootpd[5726]: interface en0: ip 192.168.2.1 mask 255.255.255.0
Jan 25 17:09:25 server bootpd[5726]: interface en2: ip 173.160.121.37 mask 255.255.255.252
Jan 25 17:09:25 server bootpd[5726]: DHCP REQUEST [en0]: 1,d0:23:db:a6:77:d <iPhone>
Jan 25 17:09:25 server bootpd[5726]: ACK sent iPhone 192.168.2.9 pktsize 300
Jan 25 17:09:25 server bootpd[5726]: service time 0.001889 seconds
Jan 25 17:09:25 server bootpd[5726]: DHCP REQUEST [en0]: 1,d0:23:db:a6:77:d <iPhone>
Jan 25 17:09:25 server bootpd[5726]: ACK sent iPhone 192.168.2.9 pktsize 300
Jan 25 17:09:25 server bootpd[5726]: service time 0.000943 seconds
Jan 25 17:09:27 server servermgrd[71]: servermgr_dhcp:bootp config:Error:Unable to read configuration file - error 2 (No such file or directory)
Jan 25 17:09:27 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created default configuration file
Jan 25 17:09:27 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created 2 default subnet records
Jan 25 17:09:37 server servermgrd[71]: servermgr_dhcp:bootp config:Error:Unable to read configuration file - error 2 (No such file or directory)
Jan 25 17:09:37 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created default configuration file
Jan 25 17:09:37 server servermgrd[71]: servermgr_dhcp:bootp config:Notice:Created 2 default subnet records
The only times it seems that DHCP is working is when it is off... which does not make any sense.
Here are some screenshots:

I don't know if it's directly related, but your setup is wrong. That could be why the config is resetting.
On your 'internal' interface you're manually setting the IP address to 192.168.2.1/255.255.255.0, and that's fine, but this interface should have NO router address specified. In your case you've set the router address to the server itself, which is never going to be accurate.
Secondly, the DHCP settings don't have a router address set. This means that your DHCP server will hand out addresses to clients, but won't tell them how to get to the outside world. Hardly seems appropriate to me.
In your DHCP settings you should set the router address to the address of your NAT server (in this case 192.168.2.1).
Try those fixes and see if it makes any difference.

Remote Web Access (remote desktop gateway) issue with WHS2011

I have been using Remote Web Access on my Windows Home Server 2011 for several years with no problems. Over the past several weeks, though, I have been receiving an error when I try to connect to a computer through WHS's Remote Web Access:
"...the Remote Desktop Gateway is temporarily unavailable." Interestingly, when I try to connect from a Windows 8.1 computer, I just get a dialog box that says "Initiating connection," but the connection is never established. I cannot
find any relevant errors in any of the event logs.
I have read numerous articles relating to WHS configuration and port forwarding, but these do not have any information that addresses my situation. I have ports 4125, 80, and 443 forwarded to my Home Server. As I said, everything has been working fine with
this configuration until several weeks ago -- I suspect it might have something to do with a .NET Framework 4.5 update that was recently installed (and that has now been uninstalled), but that is the only change I can think of.
Any help would be greatly appreciated! Thanks!

Hi,
As you have commented that after installing .Net framework you are facing this issue. So after uninstalling still you are facing the same issue. Apart from installing .Net framework 4.5, have you installed or done any other change on your server?
Here you can check that “Remote Gateway Service” is running. Please check and restart the service if it’s stop. Apart you can check below 2 article for more detail step.
1. Can’t connect to the remote computer because the Remote Desktop Gateway server is temporarily unavailable error via SBS 2011
2. This computer can't connect to the remote computer because the Terminal Services Gateway server is temporarily unavailable (Try to perform the steps as suggested for
WHS 2011)
Hope it helps!
Thanks,
Dharmesh

JES4 Gateway issues

I'm having a gateway,rewriter proxy for my portal server 6.3. All the copmonenst are JES4 version. When I try to access the portal desktop, I get the following error:
Unable to connect to host - Session: Unable to connect to host: xyz.abc.com
The message in /var/opt/SUNWps/debug/srapGateway.empl is:
Response
HTTP/1.0 502 Bad Gateway
Date: Thu, 05 Oct 2006 19:22:04 CDT
Pragma: no-cache
Server: sun.net
Allow: GET
Content-Length: 193
Content-Type: text/html;charset=ISO-8859-1
Connection: close
If I restart the gateway and rewriter proxy, I get the login screen for the first time only. Upon subsequent requests the same error message repeats. All the certificates are valid. If anybody happened to come across this problem, pleease let me know how it can be resolved. Is it something to do with the portal patches? Appreciate your response.
Thanks in advance,
--laks

We got it working. It was due to a security patch 119213-09. We backed it out and rebooted the box that resolved the issue.

SCOM 2007R2 Gateway Issue.

Similar Messages

Maybe you are looking for