HP3000-L Archives

August 2012, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Mark Sprowls <[log in to unmask]>
Reply To:
Mark Sprowls <[log in to unmask]>
Date:
Thu, 23 Aug 2012 17:20:21 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (7 lines)
When we moved our datacenter a few years ago, servers at that location were put into a class C subnet that starts with "10.", and our A-class seemed to work fine.  Now it needs to access a mail server in a different "10." subnet, but we are having difficulties.  It appears that "10." is or at some time was intended for class A subnets, and NMMGR forces the server's IP address to class A by putting the A in front of the IP address and moving the space between the first two numbers.  The result is that this server thinks the other "10." server is on the same subnet, and broadcasts locally instead of using the default gateway.  Is there some way in NMMGR to force the address to be class C?  Any other ideas?  I tried creating a static route to the other subnet, but MPE doesn't seem to even want to route.  

We are running version C.75.04.  I don't claim to be a networking expert, so please excuse any inconsistencies.  Any help would be much appreciated!

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2