Made a big mistake - VPN and RPC over HTTP (SBS 2003 Prem.)
|
Prev: Lose Internet after Rebooting SBS2008.
Next: Unable to use third-party cert after Exch Sp2 update on SBS200
From: Mike in Nebraska on 10 Jan 2010 18:08 WMI Diag finished after 87 minutes. A few errors, but reported as functional. Fixed a few using wmimgmt.msc, but left most alone as I didn't fully understand them. Restarted WMI service and ran the CEICW. Sent a test message to the admin account from outside using my hotmail account; not received. Will do some further checking.
From: Ace Fekay [MVP-DS, MCT] on 10 Jan 2010 19:06 "Mike in Nebraska" <Mike_in_Nebraska(a)newsgroup.nospam> wrote in message news:u745P7jkKHA.2188(a)TK2MSFTNGP04.phx.gbl... > UPDATE > > On a hunch, I re-registered the WMI components (I remoted in to do it) > using these at a command line: > > cd /d %windir%\system32\wbem > for %i in (*.dll) do RegSvr32 -s %i > for %i in (*.exe) do %i /RegServer > > It appeared to work - no errors while each ran. I then ran SBS BPA and > Exchange BPA and saw no inhibiting errors. > > As a further check, I am ~45 minutes into running the WMI Diagnostic tool. > It is on this step: > (0) ** - NT Event Log information > > Should be done in another 10 minutes or so. > > I'm concerned with the lack of incoming emails, though. I ran reports at > DNSStuff.com and the incoming connection can't be made. I downloaded and > installed the SMTP Diagnostic tool on my server and it found that outgoing > email works just fine. > > Am anxious to see what the WMI Diagnostic comes up with. I may have to > reinstall Exchange 2003 SP2 again to reinstall the WMI repository - I > downloaded it and am ready to run it remotely. > > I will also re-run the CEICW. > > Mike A simple test to establish if incoming smtp requests are being listened to is using telnet. Test it internally and from an external source. From internal: CMD prompt telnet open servername 25 If you see the SMTP banner popup, you know it responded. If the above responds, then you know it's working. Now from your machine at home, (make sure your antivirus and firewall is allowing this traffic), do the same but using the external MX record, such as: CMD prompt telnet open mail.yourExternalDomainName.com 25 If you see the SMTP banner popup, you know it responded. If not, then it is being blocked at your firewall at the office, or the port remap or NAT rule is not correctly configured. Ace
From: Mike in Nebraska on 10 Jan 2010 19:35 It worked as it should from internal, but fails to connect from external. From your post, I suspect it's ISA 2004. ISA does NOT show up as an installed service; the management console fails to connect to the local server. However, CEICW runs fine (now), and no errors about it in SBS or Exchange BPA's. I'll remote back in and see if I can find an ISA install/setup log; plus run the ISA BPA and see what happens. A few days ago I had done a complete uninstall of ISA then a reinstall with the same result as above, so I don't really know what to do since I don't know why that happened. I used Revo Uninstaller to take it out so it'd catch any stray registry entries and files/folders. Must have missed something. Mike
From: Mike in Nebraska on 10 Jan 2010 20:32 Before my last post, I had started the install for Exchange 2003 SP2 - in part to re-install IMF 2, and to "fix" the Exchange WMI problems. Not long after I got the install going, my remote session quit. I sort-of expected that. However, it's now been 30+ minutes and I still can't get in. Is this expected? Mike
From: Ace Fekay [MVP-DS, MCT] on 10 Jan 2010 21:28
"Mike in Nebraska" <Mike_in_Nebraska(a)newsgroup.nospam> wrote in message news:eVnfS3lkKHA.2468(a)TK2MSFTNGP04.phx.gbl... > Before my last post, I had started the install for Exchange 2003 SP2 - in > part to re-install IMF 2, and to "fix" the Exchange WMI problems. Not > long after I got the install going, my remote session quit. I sort-of > expected that. > > However, it's now been 30+ minutes and I still can't get in. Is this > expected? > > Mike It depends, not sure. I don;t know exactly what you were doing, other than what you posted. You may have *inadvertently* clicked on or opted something else. Anytime you work on something like this remotely, expect and make time in case you have to go in, or just wait until you can go in. Ace |