WSUS 3.0 Multiple Segments

I have a lab environment that is very segmented. I upgraded to WSUS 3.0 and
first off it removed my existing setup and I had to start over.

All of my routing is setup to go through several W2K3 servers that have
persistant routes configured.

For some reason from the segments other than the one the WSUS server resides
on I am unable to ping the server. I can ping all other nodes in the same
segment that WSUS server resides.

I have several routes from different segments and get the same results
through out the environment. I know my routing is working to all other
server except this one. I turned off the Firewall but it still is not
responding.

Here is my configuration:
WSUS server: 192.168.207.37 mask 255.255.255.192 no gateway on internal NIC
Route Print shows the 192.168.207.0 network going to 192.168.207.37

Other side server:
Server: 192.168.208.11 mask 255.255.255.192 gateway 192.168.208.3

Router server:
Route print 192.168.207.0 mask 255.255.255.192 route through 192.168.207.59
which is a NIC defined on the server for access to the segment where WSUS
resides

I can pint the SWUS server from the router machine (192.168.208.3) but am
unable to from the 192.168.208.11 server. From the .11 server I can ping
every other server in the 192.168.207.0 network.

I cannot figure out what the heck is going on…
Any thoughts would be appreciated.

Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_services
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

Marcy Daeffler wrote:
> I have a lab environment that is very segmented. I upgraded to WSUS 3.0
> and
> first off it removed my existing setup and I had to start over.
>
> All of my routing is setup to go through several W2K3 servers that have
> persistant routes configured.
>
> For some reason from the segments other than the one the WSUS server
> resides
> on I am unable to ping the server. I can ping all other nodes in the same
> segment that WSUS server resides.
>
> I have several routes from different segments and get the same results
> through out the environment. I know my routing is working to all other
> server except this one. I turned off the Firewall but it still is not
> responding.
>
> Here is my configuration:
> WSUS server: 192.168.207.37 mask 255.255.255.192 no gateway on internal
> NIC
> Route Print shows the 192.168.207.0 network going to 192.168.207.37
>
> Other side server:
> Server: 192.168.208.11 mask 255.255.255.192 gateway 192.168.208.3
>
> Router server:
> Route print 192.168.207.0 mask 255.255.255.192 route through
> 192.168.207.59
> which is a NIC defined on the server for access to the segment where WSUS
> resides
>
> I can pint the SWUS server from the router machine (192.168.208.3) but am
> unable to from the 192.168.208.11 server. From the .11 server I can ping
> every other server in the 192.168.207.0 network.
>
> I cannot figure out what the heck is going on…
> Any thoughts would be appreciated.

"PA Bear [MS MVP]" <> wrote in message
news:...

> Marcy Daeffler wrote:

>> I have a lab environment that is very segmented. I upgraded to WSUS 3.0
>> and
>> first off it removed my existing setup and I had to start over.
>>
>> All of my routing is setup to go through several W2K3 servers that have
>> persistant routes configured.

>> I cannot figure out what the heck is going on…
>> Any thoughts would be appreciated.

As you've noted, you have a very complex, non-standard routing arrangement,
and no doubt the issue resides somewhere in the routing configuration.

You may well be better off discussing this in a networking forum or the
Win2003 Server forum.

Routing is really beyond the scope of this group,
and trying to troubleshoot a complex server-based routing scenario is
near impossible to do without hands on in real-time.

However... I would offer one suggestion....

Consider enabling RIP and do away with the persistent routing
definitions.

If your solution is that complex that things are not working, then it's too
complex to be using static/persistent routes.

Routing Information Protocol is your friend!

--
Lawrence Garvin, M.S., MCBMSP, MCTS(x4), MCP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin