E-Mail servers IP address keeps changing in the DNS???

[Tanquen]

We have an Exchange server that is configured with a static IP address
but every few days or so, its IP address changes in the DNS. So all of
the sudden no one can connect to the Exchange server as the DNS is
giving out an incorrect IP address while the sever still has its
static IP address. Any ideas?

 

[Danny Sanders]

What is the bad IP address?

Does the exchange server have 2 network cards?


hth
DDS

 

[Tanquen]

What is the bad IP address?

The bad address is in our network and looks like it's coming from a
DHCP assignment. Even though we have the server set to a static IP.

Does the exchange server have 2 network cards?

We only ever had one network connection to the server and we even
disabled the other card and still have the issue. We even tried
replacing the network card.

 

[Ace Fekay [MVP]]

In

The bad address is in our network and looks like it's coming from a
DHCP assignment. Even though we have the server set to a static IP.


We only ever had one network connection to the server and we even
disabled the other card and still have the issue. We even tried
replacing the network card.

Is there a VPN connection in the Exchange server? RRAS running on it
possibly?


--
Ace
Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Quitting smoking is easy. I've done it a thousand times." - Mark Twain

 

[Herb Martin]

We have an Exchange server that is configured with a static IP address
but every few days or so, its IP address changes in the DNS. So all of
the sudden no one can connect to the Exchange server as the DNS is
giving out an incorrect IP address while the sever still has its
static IP address. Any ideas?

These things come from two place (both the same really but seemingly
different): An unused Network Interface, either a real NIC or an RRAS
VPN interface.

When a network interface doesn't have an address it attempts (by default)
to obtain one from DHCP. Failing that (no DHCP server etc) it use
APIPA addressing, in the range 169.254.x.y -- so such addresses appearing
in DNS are a direct tipoff.

Disable any unused NICs or VPNs, or else assign them correct addresses
and perhaps disable them being automatically registered in DNS.

 

[Guest]

I have a very similar issue with the IP address of our Exchange Server.

There are some users who get disconnected from Exchange. When I ping the
mail server, it shows as our external IP address, not the internal address.
This is not network wide, but limited to various users at seperate times.

Any help??

Jeff

 

[Herb Martin]

I have a very similar issue with the IP address of our Exchange Server.

There are some users who get disconnected from Exchange. When I ping the
mail server, it shows as our external IP address, not the internal
address.
This is not network wide, but limited to various users at seperate times.

Any help??

Yes, remove the additional addresses for any such servers by one of
several methods:

1) Disable unneeded NICs
2) Give "outside NICs" and artificially different "suffix" for
registration
( I use "Cable" and "DSL" for my various external NICs on the
router), e.g., Server.cable.domain.com,
Server.dsl.domain.com
as opposed to the servers "real" internal NIC,
server.domain.com)
3) Uncheck the "register this connection"
4) Delete any such (existing) registration

#2 and 3 can be done even on RAS/VPN interfaces if you look in the
Advanced settings.