[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1113
  • Last Modified:

My windows 2003 server - exchange 2003 is not receiving emails

I have a Watchguard Firewall X500 Connected to my DSL Modem.  I have plugged in my laptop using the following Static Settings: Ip Address: 10.0.0.5  
255.255.255.0
10.0.0.1
DNS: 4.2.2.2.2   DNS2 4.2.2.2.3  So, when I plug in my laptop to the trusted port on the firewall I get connected to the internet with no problem.  Now, my internal network has a windows 2003 server with Exchnage 2003 and serving as a DHCP to distribute Ip Addresses.   Now, when I plug in a 25-Port Dlink switch to distribute Internet to everyone in the company my connection to the Net drops.  My server has a ip address of 10.0.0.4     Connection-specific DNS Suffix  . :
 Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network Connection
 Physical Address. . . . . . . . . : 00-0F-1F-65-1B-D2
 DHCP Enabled. . . . . . . . . . . : No
 IP Address. . . . . . . . . . . . : 10.0.0.4
 Subnet Mask . . . . . . . . . . . : 255.255.255.0
 Default Gateway . . . . . . . . . : 10.0.0.1
 DNS Servers . . . . . . . . . . . : 10.0.0.4

So, What I did to give my server internet access was to plug in a regular 5-port dlink switch going to my server.  I have internet access to the server and I am able to send emails but Not receive them.  I am going nut over this stuff so can anyone help me with this issue.  Could it be my server configuration?  Or my firewall internal config that might be blocking something somewhere??  Your help/comments are greatly appreciate since busines is not operating fully.

Manny
0
acamanny
Asked:
acamanny
  • 4
  • 3
1 Solution
 
Kevin HaysIT AnalystCommented:
You shouldn't be using the 4.2.2.2 / 3 for your DNS.  You should either have your dhcp service handing out the correct DNS IP of your server or manually key in the IP of your DNS server in the tcp/ip properties.

Do you have an mx record to point to your exchange (internal IP of the server).  Are you allowing ports 25 and 443 to the inside of your network to the exchange servers IP ?

0
 
acamannyAuthor Commented:
I am only using that on my laptop but other computer including the server has the usual settings.  My 2003 server is configured as my dhcp yes AND I AM getting internet connection on that desktop.  Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\mbarrera>ipconfig /all

Windows IP Configuration

        Host Name . . . . . . . . . . . . : testserver
        Primary Dns Suffix  . . . . . . . : meadfluid.meadfluiddynamics.com
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : meadfluid.meadfluiddynamics.com
                                            meadfluid.meadfluiddynamics.com
                                            meadfluiddynamics.com

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : meadfluid.meadfluiddynamics.com
        Description . . . . . . . . . . . : 3Com 3CSOHO Fast Ethernet Adapter
        Physical Address. . . . . . . . . : 00-50-DA-0F-CA-93
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 10.0.0.48
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.0.0.1
        DHCP Server . . . . . . . . . . . : 10.0.0.4                    This is my email server.
        DNS Servers . . . . . . . . . . . : 10.0.0.4
        Primary WINS Server . . . . . . . : 10.0.0.4
        Lease Obtained. . . . . . . . . . : Tuesday, July 31, 2007 7:19:11 AM
        Lease Expires . . . . . . . . . . : Wednesday, August 08, 2007 7:19:11 Am


I AM ABLE TO SEND EMAILS OUT BUT NOT RECEIVE!
0
 
Kevin HaysIT AnalystCommented:
Ok, it sounds like either you don't have the proper mx record for the dns set or you are not allowing smtp port (25) in to your network.

For instance our dns for our domain was setup at everydns.net and it's got a public mx record for the mail server there.  Can you watch the traffic as it's generated to see if you are getting anything blocked by incoming traffic?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
acamannyAuthor Commented:
07/31/07 14:02  firewalld[127]:  deny in eth0 39 udp 20 116 71.14.119.100 68.254.201.217 62477 32839 (default)
07/31/07 14:02  firewalld[127]:  deny in eth0 39 udp 20 116 81.165.35.4 68.254.201.217 52059 32845 (default)
07/31/07 14:02  chat-ttyS0[158]:  Failed
07/31/07 14:02  pppd[132]:  Connect script failed
07/31/07 14:02  firewalld[127]:  deny in eth0 39 udp 20 116 82.48.67.167 68.254.201.217 13230 32818 (default)
07/31/07 14:02  firewalld[127]:  deny in eth0 47 udp 20 116 82.48.67.167 68.254.201.217 13230 32818 (default)
07/31/07 14:02  firewalld[127]:  deny in eth0 39 udp 20 116 71.14.119.100 68.254.201.217 62477 32839 (default)
07/31/07 14:02  firewalld[127]:  deny in eth0 39 udp 20 116 81.165.35.4 68.254.201.217 52059 32845 (default)
07/31/07 14:02  validator[125]:  Validator: accepted client connection, fd=9
07/31/07 14:02  validator[125]:  Validator: got 3 command messages
07/31/07 14:02  validator[125]:  request ip is 10.0.0.37
07/31/07 14:02  validator[125]:  command is verify_cert
07/31/07 14:02  validator[125]:  verifying firebox credentials
07/31/07 14:02  validator[125]:  Created and set certificate context successfully
07/31/07 14:02  validator[125]:  failed to get subject name. 3028 Failed to read file
07/31/07 14:02  validator[125]:  No data available, clearing client socket 9
07/31/07 14:02  fwcheck[139]:  fwcheck v7.5.0.B2068 (C) 1996-2007 WGTI
07/31/07 14:02  firewalld[127]:  deny in eth0 52 udp 20 49 68.254.201.222 68.254.201.223 520 520 (default)
07/31/07 14:02  chat-ttyS0[161]:  Failed
07/31/07 14:02  pppd[132]:  Connect script failed
07/31/07 14:02  validator[125]:  Validator: accepted client connection, fd=9
07/31/07 14:02  validator[125]:  Validator: got 3 command messages
07/31/07 14:02  validator[125]:  request ip is 10.0.0.37
07/31/07 14:02  validator[125]:  command is verify_cert
07/31/07 14:02  validator[125]:  verifying firebox credentials
07/31/07 14:02  validator[125]:  Created and set certificate context successfully
07/31/07 14:02  validator[125]:  failed to get subject name. 3028 Failed to read file
07/31/07 14:02  validator[125]:  No data available, clearing client socket 9
07/31/07 14:03  firewalld[127]:  deny in eth0 52 udp 20 49 68.254.201.222 68.254.201.223 520 520 (default)
07/31/07 14:03  firewalld[127]:  deny in eth0 32 igmp 24 1 68.254.201.222 224.0.0.1 unknown ? (ip options)
07/31/07 14:03  validator[125]:  Validator: accepted client connection, fd=9
07/31/07 14:03  validator[125]:  Validator: got 3 command messages
07/31/07 14:03  validator[125]:  request ip is 10.0.0.37
07/31/07 14:03  validator[125]:  command is verify_cert
07/31/07 14:03  validator[125]:  verifying firebox credentials
07/31/07 14:03  validator[125]:  Created and set certificate context successfully
07/31/07 14:03  validator[125]:  failed to get subject name. 3028 Failed to read file
07/31/07 14:03  validator[125]:  No data available, clearing client socket 9
07/31/07 14:03  chat-ttyS0[164]:  Failed
07/31/07 14:03  pppd[132]:  Connect script failed
07/31/07 14:03  pppd[132]:  Discontinuing attempts to initialize modem on [/dev/ttyS0]; Maximum # of attempts [3] exceeded
07/31/07 14:03  init[1]:  Pid 132: exit 1
07/31/07 14:03  firewalld[127]:  deny in eth0 52 udp 20 49 68.254.201.222 68.254.201.223 520 520 (default)
07/31/07 14:04  validator[125]:  Validator: accepted client connection, fd=9
07/31/07 14:04  validator[125]:  Validator: got 3 command messages
07/31/07 14:04  validator[125]:  request ip is 10.0.0.37
07/31/07 14:04  validator[125]:  command is verify_cert
07/31/07 14:04  validator[125]:  verifying firebox credentials
07/31/07 14:04  validator[125]:  Created and set certificate context successfully
07/31/07 14:04  validator[125]:  failed to get subject name. 3028 Failed to read file
07/31/07 14:04  validator[125]:  No data available, clearing client socket 9
07/31/07 14:04  firewalld[127]:  deny out eth1 240 udp 20 64 192.168.11.150 192.168.11.255 138 138 (spoofed source address)
07/31/07 14:04  chat-ttyS2[169]:  Can't get terminal parameters: Input/output error
07/31/07 14:04  pppd[133]:  Connect script failed
07/31/07 14:04  firewalld[127]:  deny in eth0 52 udp 20 49 68.254.201.222 68.254.201.223 520 520 (default)
07/31/07 14:04  firewalld[127]:  deny in eth0 133 icmp 20 236 212.42.181.120 68.254.201.217 3 1 (default)
07/31/07 14:04  firewalld[127]:  deny in eth0 133 icmp 20 236 212.42.181.120 68.254.201.217 3 1 (default)
07/31/07 14:04  init[1]:  Pid 93: exit 0
07/31/07 14:04  init[1]:  Pid 109: exit 0
07/31/07 14:04  init[1]:  Pid 111: exit 0
07/31/07 14:04  firewalld[127]:  Begin sending of wg.cfg to 10.0.0.37
07/31/07 14:04  firewalld[127]:  End sending of wg.cfg to 10.0.0.37
07/31/07 14:04  validator[125]:  Validator: accepted client connection, fd=9
07/31/07 14:04  validator[125]:  Validator: got 3 command messages
07/31/07 14:04  validator[125]:  request ip is 10.0.0.37
07/31/07 14:04  validator[125]:  command is verify_cert
07/31/07 14:04  validator[125]:  verifying firebox credentials
07/31/07 14:04  validator[125]:  Created and set certificate context successfully
07/31/07 14:04  validator[125]:  failed to get subject name. 3028 Failed to read file
07/31/07 14:04  validator[125]:  No data available, clearing client socket 9
07/31/07 14:04  dvcpsv[146]:  Rcvd status command from 10.0.0.37
07/31/07 14:04  validator[125]:  Validator: accepted client connection, fd=9
07/31/07 14:04  validator[125]:  Validator: got 3 command messages
07/31/07 14:04  validator[125]:  request ip is 10.0.0.37
07/31/07 14:04  validator[125]:  command is verify_cert
07/31/07 14:04  validator[125]:  verifying firebox credentials
07/31/07 14:04  validator[125]:  Created and set certificate context successfully
07/31/07 14:04  validator[125]:  failed to get subject name. 3028 Failed to read file
07/31/07 14:04  validator[125]:  No data available, clearing client socket 9
07/31/07 14:04  firewalld[127]:  deny in eth0 52 udp 20 49 68.254.201.222 68.254.201.223 520 520 (default)
07/31/07 14:05  validator[125]:  Validator: accepted client connection, fd=9
07/31/07 14:05  validator[125]:  Validator: got 3 command messages
07/31/07 14:05  validator[125]:  request ip is 10.0.0.37
07/31/07 14:05  validator[125]:  command is verify_cert
07/31/07 14:05  validator[125]:  verifying firebox credentials
07/31/07 14:05  validator[125]:  Created and set certificate context successfully
07/31/07 14:05  validator[125]:  failed to get subject name. 3028 Failed to read file
07/31/07 14:05  validator[125]:  No data available, clearing client socket 9
0
 
Kevin HaysIT AnalystCommented:
Did you get everything resolved and working correctly now?

Kevin
0
 
acamannyAuthor Commented:
Kevin I did get it resolved yes.  First, one switch out in the plant was bad. also it seems that a Patch panel probably 8 years old is not communicating any data through it so I had to eliminated and instead plug by pass it by running a wire from aother switch inside the plant.  So, things are going well so far.  Thanks for your help and if there is any other thing I need to do to close this question please let me know.
0
 
Kevin HaysIT AnalystCommented:
Great.  It does sound like you really had your worked cut out considering a switch went out and then the patch panel.  Wheh.  Anyway, you are welcome and you don't have to do anything else to the question :)

Have a wonderful day.

Kevin
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now