Strange problem here.
SBS running SVR2003 with Exchange.
Suddenly the other day, we have been unable to send OR receive email from anyone with a Comcast.net email address. To add to the weirdness, Off site folks cannot connect in through RDP if they are using a Comcast IP (say, there provider is comcast) Everyone and everything else functions as normal, no settings have been changed in the last year and this issue didn't exisit! It just started last week. Any ideas? I've pretty much pulled all of my hair out...note: When looking at the virtual SMTP connectors, anything from comcast "hangs" won't unfreeze, etc. Message claims an SMTP protocol error but, nothing's changed from when it was working normally! <gack>
Have you already tried to restart the mail services?
I sure did. Was x-ing my fingers hoping that would resolve it but no such luck. Very strange deal as it has been working fine for the last 5 years or so with no problem and "out of the blue" last week, Presto, not accepting or sending email related to comcast.net and won't let offsite folks log RDP if they are on a comcast IP. Never seen anything like it in my 10 years of IT service... Crazy...
Sounds like a ban on the comcast ip range referred to as blacklisted. Check your firewalls. Talk to your isp.
Thanks. Check that. Not on any blacklists and no known issues, firewalls ok. :sigh:
can you do a nslookup from the server to comcast.net or comcast.com?
Wow, nice call. I somehow overlooked that....
and the system sez.... sbs-server-.xxxxx.local (xx sub my name) "can't find nslookup: non-existent domain" I get the same result when I check by xxxxx.tv and if I check by ip 192.168.x.x it times out timeout is 2 seconds. I get the same timeout result if I do the lookup for comcast.net or com or any other (i.e aol.com)What the heck? and I can still send and recieve email from every place known to man EXCEPT comcast.net addresses?
Crazy! Geez, what now leuitenent? I'm at a loss. either that or, I'been been on it too long and my brain is fried....
Thanks so much for your help wanderer...
Check the hosts file for suspicious entries.
Check the ipconfig /all.
How many network cards are in that server.
Can you e.g. tracert google.com and maybe tracert comcast.com.
well, the tracert seems to work, meaning, I get the ip addys but it then times out with a 2 sec count. the ip config looks correct,
what's seems odd is that it's claiming the dhcp is not enabled but, all of the other gear attached to it (pc,s editing equip, etc) are functioning fine. 2 cards, one disabled. but, this cow has a sister that acts as a file server and RDP connection only. Wonder if THATS where the issue is and not really in exchange at all? :sigh: I'll be bald soon...
sounds more like a dns issue. In your ms dns server do you have your isps dns server listed in the forwarders tab?
can you ping the isps dns servers so you know they are alive?how about a post of an ipconfig /all from the server?
How weird is this.
I noted an error in the logfiles with MSSQLxxxx unable to start.
I went into the reg file, deleted the GUID entry, restarted and now it all seems to work?! What the duece? :lol:
| « windows 2003 server | Low disk Space » |