|
From the above, I can only guess that corporate intends to remove the individual NAT routers, as all the hospitals are connected by a leased line to corporate, and corporate office is the only connection to the outside world.
On to the networking stuff. Our original network guy flew by the seat of
his pants. My original email address was something ungodly containing
slashes and probably 30 characters.
Now all internal address in all locations in all countries begin with 10
dot, unless, they are in our dmz. In a format of 10 dot x dot y dot z the
dot x will normally signify a city.
Let's take relying upon NAT for example... Let's say you have an internal
address you use of 173.45.161.122. Well, instead of your browser going to
that internal site let's say it mozies on out to the external site with
that IP address. Don't you think your personnel director would be quite
shocked? (If you value your employment I would NOT suggest you try
pointing your browser to it while at work. Trust me, I took an offensive
site, simply pinged it and put that IP address in there.)
We actually had cases of people trying to reach internal sites but getting
external ones instead.
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "John McKee" <jmmckee@xxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 09/02/2011 03:44 PM
Subject: DBU oddity
Sent by: midrange-l-bounces@xxxxxxxxxxxx
The system has an exit point program installed to associate an IP adress
with a specific device. My involvement is to maintain the datafile.
When networking was started, there weren't a lot of devices, and the
addresses were assigned to 172.16.x.x. The corporate office wants all the
hospitals in the system to convert to a 10.x.x.x addressing method. Since
all the locations use NAT to connect to the private network and then
through the corporate office to the outside world, that doesn't make sense
to me. Is there any rationale for changing addressing behind a NAT
firewall?
The above is to explain my second question. I was told that an IP address
for a device needed to be changed from 172.16.x.x to 10.0.x.x - I can't
recall the exact addresses.
The file used for device assignment is keyed by IP address.
Using DBU, I found the old IP address and updated it to the new one.
Except that it didn't update. I had seen this before and wondered about
it. This IP address change was needed rather quickly, so I tried SQL, a
simple UPDATE. That worked.
Is there anything that would explain why DBU would act like it changed the
key field, but didn't - after at least two attempts, but SQL did,
immediately? Only a guess, but is an object lock involved.
John McKee
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
