Re: Exchange SP2 not receiving DNS email
- From: Mike H <mkREMOVEhuskeyALL@xxxxxxxxxxxxxxxxxxx>
- Date: Tue, 22 May 2007 12:59:24 -0700
It's what, a month-and-a-half later? I finally found the problem last
week.
What happened was when I rebuilt my connections after the NIC driver
update fiasco I mistakenly entered our public IP address with a one off
error, .65 instead of .66 in the last octet. It was only while I was
browsing somewhere in services and applications and saw my pulic IP
while at the same time looking at my MX records at GoDaddy on another
monitor. They didn't match. I had given a bad IP address to the server.
On Thu, 5 Apr 2007 01:10:00 -0700, Keith Lawrence MCP wrote:
You might want to check which IP your smtp virtual server is bound to. Drill[snip]
down to the smtp protocol in ESM to verify this. Also check to see if smtp
service is running.
Also try some basic telnet tests from the wan side to determine if the smtp
server is responding - telnet <myserverexternalwan> 25 - you should get the
standard esmtp banner response. Also try manually sending an email via telnet.
Another place to look is the network connections window. Click Advanced >
Advanced settings. There you can check the connection order (make sure LAN is
highest) and the relevant bindings). This would determine which NIC answers
dhcp/dns requests etc.
Sounds like a messy one. The drivers for the cards shouldnt have that kind
of major effect unless the static IP information was removed when they were
upgraded. In that case, simply running ceicw would have let you re-enter the
relevant addresses and determine your wan/lan onterfaces. It would also
rebuild the standard ISA SBS rules.
"Mike H" wrote:[snip]
I'm not receiving e-mail addressed to anybody@xxxxxxxxxxxx
A little background:
SBS 2003 SP1 + SP2
Exchange Server SP1 + SP2
Uninstalled ISA Server 2004 SP1 + SP2
Trouble began when upgrading NIC drivers. Installation program deleted my
network connections during its install. SBS, detecting this, established a
couple of new default connections. It incorrectly determined which connection
went to the LAN and which went to the WAN.
Other problems were a total loss of all entries in DNS Server and DHCP
server, loss of Companyweb, and Active Directory invalidating a workstation.
Since then, I've rebuilt DHCP Server and DNS Server. DHCP is correctly
updating DNS, the proper records are in DNS, workstations properly get an IP
address and scope settings from DHCP, and utilities such as IPCONFIG
/registerdns properly interact with DNS Server (a test case was where I
deleted both (A) and PTR records for a workstation and saw them replaced with
REGISTERDNS. Similarly, deleting those same records, doing an IPCONFIG
/release, then an IPCONFIG /renew also rebuilt the DNS records. So far, so
good.
Although I was able to "approve" the untrusted workstation in AD,
ultimately, I had to put the workstation in a workgroup and then rejoin the
domain.
Finally, I could not get ISA Server 2004 SP2 to begin working again. It
seemed to be in default "Block All" mode and I couldn't get it sync'd up with
the proper NIC. That's why I uninstalled it.
It should go without saying that, in addition to rebuilding the network
connections (with the same names and on the same NICs I might add), I reran
CEICW multiple times, as well as the "Change Server IP Address" function -
both followed by multiple reboots.
There's a little background. I'm also running the POP3 connector on
exchange. It began working when ISA Server was uninstalled. The MSDE,
Sharepoint, and companyweb are back up.
What's left is that I don't get DNS e-mail. I can send from my domain, but
not receive.
I have VERY nice event logs. Just two early-on errors that have always been
there (dsrestore and sharepoint) in Applications. There are NO errors in any
other event logs. Likewise, I didn't get any errors listed in exchdump. I've
even totally disabled all router security and let RRAS Firewall pick up the
slack. (I have 1-1 IP routing through the router-I'm on a 5-address public
subnet, so the Server IP is truly a public IP)
Where might I look for other problems? For instance, is their anything
"NIC-centric" in the properties of Exchange Server anywhere? Any IP addresses
(as opposed to names) in the Exchange properties? Someplace else to look in
AD? Maybe the Intelligent Message Filter which came with Exchange SP2 (and
which I have never had time to configure.)?
.
- Follow-Ups:
- Re: Exchange SP2 not receiving DNS email
- From: Keith Lawrence MCP
- Re: Exchange SP2 not receiving DNS email
- Prev by Date: Re: ISA error in event logs
- Next by Date: Re: SBS RWW Vista and Client drive mapping
- Previous by thread: Re: DHCP updates to DNS question
- Next by thread: Re: Exchange SP2 not receiving DNS email
- Index(es):
Relevant Pages
|
