Hi, I just started with a new company and they have been having an issue for quite some time. Although Friday was my first day, I recognized that they were using an internal 128.x.x.x ip scheme throughout the company. They recently installed a sonicwall firewall appliance and prior to that they had a "firewall" BUT from what I hear it was never defined, so it acted pretty much like a gateway allowing traffic in and out freely. Since the implementation of the SonicWall device, they have not been able to send mail to any AT&T and its subsidiaries due to being blacklisted. Another thing I looked at was in their DNS...they have no MX record. So, 3 things I found in a hour that might have everything to do with it, or maybe nothing at all, but I would like another opinion from a peer out there who might recognize something here. I want to add an MX record to their DNS, BUT I don't want to foul anything up on my second day there. I also want to propose changing the IP scheme within the organization to a 10.x.x.x scheme....but again, I want to make sure of what I propose is factual. Any ideas?

I apologize, they are using Exchange as well. Nancy DeCrescenzo

Hi Rich, Thank you for replying. I explained to them the same thing you stated above (as far as the 128.x.x.x going outside the router and hitting the real network), so I will propose an IP change solution, which might fix a few more hiccups in the environment. I will have to see exactly what the DNS is holding and where its pointing when I get there Monday morning, and will have to check the inbound connection. The last Exchange I administered was 5.5, that was back in 2001....its not like riding a bike! I will have to take a crash course again on it....but I at least know where to look up some answers, and of course come to this board for some real life situations and answers :) Thanks again!Nancy DeCrescenzo