DHCP Lease Advise

[talksr]

Hi there,

 

I have changed our subnet so we can accommodate more devices on the network.

 

It was: 10.75.44.10/24 (available host addresses:254)

It is now: 10.75.44.10/22 (available host addresses:1022)

 

I am in the process of changing the DHCP scope in DHCP on our server following the following guide.

 

Our existing pool is: 10.75.44.20-219.

Now we have additional available addresses, I would like to extend the range but I am unsure how as we have a static range of 10.75.44.220-249 for telephones managed by an external company.

 

How can I make use of the additional host addresses without having to get the telephone company in to change the IPs on their phones? Would I just create a bigger pool and then add in an exclusion range?

Edited June 23, 2016 by talksr

[sted]

just create an exclusion zone so that those (and a fre above.below) cant be given out by the dhcp server

[talksr]

just create an exclusion zone so that those (and a fre above.below) cant be given out by the dhcp server

 

Thanks, worked a dream.

[talksr]

Quick update....

Everything running well apart from our secondary server. This is connected as a member to the AD of our FRDC which runs Ranger ( a cheaper version of RM, bit like CC4 but far more basic). The secondary server which is playing up is on the network perfectly, no issues at all other than, WSUS is no longer working.

 

Backup working well, av working well from this server - both of which use the network to store backups or protect systems.

 

This is the WSUS error, any ideas?:

The WSUS administration console was unable to connect to the WSUS Server via the remote API.

 

Verify that the Update Services service, IIS and SQL are running on the server. If the problem persists, try restarting IIS, SQL, and the Update Services Service.

 

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

 

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

 

 

System.IO.IOException -- The handshake failed due to an unexpected packet format.

 

Source

System

 

Stack Trace:

at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)

at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)

at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at System.Net.ConnectStream.WriteHeaders(Boolean async)

** this exception was nested inside of the following exception **

 

 

System.Net.WebException -- The underlying connection was closed: An unexpected error occurred on a send.

 

Source

Microsoft.UpdateServices.Administration

 

Stack Trace:

at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()

at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()

 

 

 

... I forgot to say, all I have done to this secondary server is change the subnet from 255.255.255.0 to 255.255.252.0 - it has a statically assigned IP.

 

I have bounced the server three times and flushed dns, but no change in the WSUS.

Edited June 24, 2016 by talksr

[TriggerHappyUK]

Just an idea...

 

Have you checked the WSUS GPO settings?

 

C

[Oaktech]

Is it possible that this is to do with the update to wsus?

 

https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

[talksr]

Just an idea...

 

Have you checked the WSUS GPO settings?

 

C

 

No, but what would that have to do with a subnet change? It was working well before hand. Is there anything in particular I should be looking for?

[TriggerHappyUK]

Just remember there being lots of GPO setting for WSUS. There may be one that could help.

[talksr]

Just remember there being lots of GPO setting for WSUS. There may be one that could help.

 

Couldn't see anything that looked out of place. Starting to get worried now as both workstations and servers are unable to get any updates.

[sted]

with wsus if it goes wrong personally id just remove and reinstall its often the easiest and quickest way and you will probably find your updates folder is smaller afterwards as even cleanup dosent seem to do as good a job as starting from scratch

[TriggerHappyUK]

Couldn't see anything that looked out of place. Starting to get worried now as both workstations and servers are unable to get any updates.

 

Try a reinstall of WSUS

 

Edit - Sted got there before me

[Oaktech]

Is it possible that this is to do with the update to wsus?

 

https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/

 

Couldn't see anything that looked out of place. Starting to get worried now as both workstations and servers are unable to get any updates.

 

Did you check out my link? The behaviour you're describing is exactly what will happen if you have installed kb3148812 and not run the post install servicing task.

[talksr]

Did you check out my link? The behaviour you're describing is exactly what will happen if you have installed kb3148812 and not run the post install servicing task.

 

 

Hi, sorry think I missed your original post. Have taken a look but kb3148812 was not installed and this fault happened at exactly the same time as when I made the subnet change. Will try removing and re-installing WSUS as advised on here. See if that resolves the problem.

[talksr]

Things are not working out all that well.

I removed WSUS from Server Manager, bounced and then re-installed. It reinstalled without any issues, however when I opened it for the first time, I now get the following error box:

 

Post-installation Notifications

The post-installation task failed. Please see below for details:

Log file is located at C:\Users\Administrator.STM-SR-002\AppData\Local\Temp\2\tmp35BE.tmp

Post install is starting

Fatal Error: Changes to the state or options of database 'SUSDB' cannot be made at this time. The database is in single-user mode, and a user is currently connected to it.

ALTER DATABASE statement failed.

[sted]

Things are not working out all that well.

I removed WSUS from Server Manager, bounced and then re-installed. It reinstalled without any issues, however when I opened it for the first time, I now get the following error box:

 

Post-installation Notifications

The post-installation task failed. Please see below for details:

are you using sql or wid for the database?

[talksr]

are you using sql or wid for the database?

 

It didn't give me an option to chose, so not sure. Where could I check this?

 

Have re-booted and attempted to open WSUS again and it seems to be stuck on this screen:

 

Edited June 30, 2016 by talksr

[talksr]

After another reboot, it seems to have worked. Thanks for your help.

[TriggerHappyUK]

Glad it's all working

[fiberoptics]

creating an exclusion zone