Networking Forums

Networking Forums > Computer Networking > Windows Networking > Global Catalog / Domain Controller loses connection to Exchange

Reply
Thread Tools Display Modes

Global Catalog / Domain Controller loses connection to Exchange

 
 
Chris Baldassano
Guest
Posts: n/a

 
      05-01-2006, 06:09 AM
I have a server called File2k3. It's a Win2k3 server standard. Global
Catalog and Domain Controller.

My exchange server is called Mail2k3.

When the systems come up, they see eachother just fine... after about an
hour, the Mail2k3 box can not ping the file2k3 box, and Outlook/exchange gets
awfully slow. I ran a netstat and see a TON of ports to file2k3 in a
CLOSE_WAIT state. If i reboot file2k3 (which is also our DNS Server), when
it comes up its fine again.

File2k3, can ping mail2k3 PERFECTLY everytime (even when Mail2k3 cant ping
it)..

Both are up to latest service packs and hotfixes...

Has anyone seen this before? I am forced to reboot the server 20x a day!
--
Network Administrator
Simon Paston & Sons Agency
 
Reply With Quote
 
 
 
 
Miha Pihler [MVP]
Guest
Posts: n/a

 
      05-01-2006, 09:04 AM
Hi,

When you try to ping the File2k3 server do you use name or IP address? Does
it work if you use IP address?

Can you check the event logs on both servers (specially Application and
System Event logs) and see if there are any errors. Post back with these
errors...

Can you also post here the results of command

ipconifg /all

from both servers?

--
Mike
Microsoft MVP - Windows Security


"Chris Baldassano" <(E-Mail Removed)> wrote in
message news:6876826E-549E-4E4F-80DE-(E-Mail Removed)...
>I have a server called File2k3. It's a Win2k3 server standard. Global
> Catalog and Domain Controller.
>
> My exchange server is called Mail2k3.
>
> When the systems come up, they see eachother just fine... after about an
> hour, the Mail2k3 box can not ping the file2k3 box, and Outlook/exchange
> gets
> awfully slow. I ran a netstat and see a TON of ports to file2k3 in a
> CLOSE_WAIT state. If i reboot file2k3 (which is also our DNS Server),
> when
> it comes up its fine again.
>
> File2k3, can ping mail2k3 PERFECTLY everytime (even when Mail2k3 cant ping
> it)..
>
> Both are up to latest service packs and hotfixes...
>
> Has anyone seen this before? I am forced to reboot the server 20x a day!
> --
> Network Administrator
> Simon Paston & Sons Agency



 
Reply With Quote
 
Chris Baldassano
Guest
Posts: n/a

 
      05-01-2006, 02:16 PM
I can not ping by IP, Or by Name from mail2k3 to File2k3... But the other way
around it works perfectally fine (ip or name)...

Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
secondary one is just not connected... I am gonna hook them up today to see
if it is a NIC issue.. (I doubt it, there would be other factors)...

Little more background:

-File2k3 is our DNS server with the proper ISP DNS's forwarded...
-File2k3 is our Global Catalog, and Domain Controller

-Mail2k3 WAS a domain controller, that was taken down by 2 microsoft tech's
about 5 days ago on a $245 Support Call.. They did all the proper steps to
make it Just an exchange server and not anything else.



Here is the IP config for each machine..

FILE2K3:

Windows IP Configuration

Host Name . . . . . . . . . . . . : file2k3
Primary Dns Suffix . . . . . . . : pastongroup.com
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : pastongroup.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : pastongroup.com
Description . . . . . . . . . . . : 3Com Gigabit NIC
Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.3

MAIL2K3:



Windows IP Configuration



Host Name . . . . . . . . . . . . : mail2k3
Primary Dns Suffix . . . . . . . : pastongroup.com
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : pastongroup.com



PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.114
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com Gigabit NIC
Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.30
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.3

***

Here is the ping from Mail2k3 to File2k3:

Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.3:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

And here is From FILE2k3 to MAIL2k3:

Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:

Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
Reply from 192.168.1.30: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.30:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

***

Now here is what I notice when I do a NETSTAT -A on mail2k3... there are a
ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
getting thru and the LDAP etc is failing...

FROM MAIL2K3 (Netstat -a) spit to a txt file.

Active Connections

Proto Local Address Foreign Address State
TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3ptp mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:http ten11.bwc.na.blackberry.net:34159 TIME_WAIT
TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
TCP mail2k3:691 mail2k3.pastongroup.com:48987 ESTABLISHED
TCP mail2k3:691 mail2k3.pastongroup.com:48997 ESTABLISHED
TCP mail2k3:691 mail2k3.pastongroup.com:49052 ESTABLISHED
TCP mail2k3:691 mail2k3.pastongroup.com:49055 ESTABLISHED
TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3ptp ool-457251fd.dyn.optonline.net:1151
ESTABLISHED
TCP mail2k3ptp ool-457b9bc5.dyn.optonline.net:2912
ESTABLISHED
TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:3916 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3918 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3929 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3930 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3935 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3936 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3937 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3938 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3939 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3940 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3942 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:4459 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:4908 file2k3.pastongroup.com:3268 ESTABLISHED
TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5325 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5771 file2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
ESTABLISHED
TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn TIME_WAIT
TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
TCP mail2k3:5934 file2k3.pastongroup.com:domain TIME_WAIT
TCP mail2k3:5935 file2k3.pastongroup.com:domain TIME_WAIT
TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
ESTABLISHED
TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
TCP mail2k3:48998 EXT285:2018 ESTABLISHED
TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED
TCP mail2k3:48998 ext240.pastongroup.com:1275 ESTABLISHED
TCP mail2k3:48998 ext292.pastongroup.com:3766 ESTABLISHED
TCP mail2k3:48998 ext227.pastongroup.com:3811 ESTABLISHED
TCP mail2k3:48998 ext275.pastongroup.com:1119 ESTABLISHED
TCP mail2k3:48998 ext297.pastongroup.com:2418 ESTABLISHED
TCP mail2k3:48998 ext200.pastongroup.com:1251 ESTABLISHED
TCP mail2k3:48998 ext209.pastongroup.com:1096 ESTABLISHED
TCP mail2k3:48998 ext299.pastongroup.com:1653 ESTABLISHED
TCP mail2k3:48998 ext206.pastongroup.com:3831 ESTABLISHED
TCP mail2k3:48998 ext273.pastongroup.com:3103 ESTABLISHED
TCP mail2k3:48998 ext236.pastongroup.com:1127 ESTABLISHED
TCP mail2k3:48998 ext211.pastongroup.com:1266 ESTABLISHED
TCP mail2k3:48998 ext269.pastongroup.com:1154 ESTABLISHED
TCP mail2k3:48998 ext217.pastongroup.com:3694 ESTABLISHED
TCP mail2k3:48998 ext233.pastongroup.com:2778 ESTABLISHED
TCP mail2k3:48998 ext293.pastongroup.com:2177 ESTABLISHED
TCP mail2k3:48998 ext276.pastongroup.com:1755 ESTABLISHED
TCP mail2k3:48998 192.168.1.105:1629 ESTABLISHED
TCP mail2k3:48998 ext269.pastongroup.com:3829 ESTABLISHED
TCP mail2k3:48998 ext282.pastongroup.com:2949 ESTABLISHED
TCP mail2k3:48998 ext282.pastongroup.com:2952 ESTABLISHED
TCP mail2k3:48998 ira.pastongroup.com:1638 ESTABLISHED
TCP mail2k3:48998 EXT272:1103 ESTABLISHED
TCP mail2k3:48998 ext279.pastongroup.com:4178 ESTABLISHED
TCP mail2k3:48998 ext277.pastongroup.com:4431 ESTABLISHED
TCP mail2k3:48998 ext248.pastongroup.com:1114 ESTABLISHED
TCP mail2k3:48998 ext234.pastongroup.com:4836 ESTABLISHED
TCP mail2k3:48998 ext288.pastongroup.com:2854 ESTABLISHED
TCP mail2k3:48998 scottxp.pastongroup.com:3144 ESTABLISHED
TCP mail2k3:49052 mail2k3.pastongroup.com:691 ESTABLISHED
TCP mail2k3:49055 mail2k3.pastongroup.com:691 ESTABLISHED
TCP mail2k3:50087 file2k3.pastongroup.com:1025 ESTABLISHED
TCP mail2k3:50094 file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:50095 file2k3.pastongroup.com:ldap CLOSE_WAIT
TCP mail2k3:50098 file2k3.pastongroup.com:3268 CLOSE_WAIT
TCP mail2k3:50099 file2k3.pastongroup.com:3268 CLOSE_WAIT
TCP mail2k3:53777 file2k3.pastongroup.com:1025 ESTABLISHED
TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
UDP mail2k3:epmap *:*
UDP mail2k3:microsoft-ds *:*
UDP mail2k3:isakmp *:*
UDP mail2k3:1025 *:*
UDP mail2k3:1026 *:*
UDP mail2k3:1027 *:*
UDP mail2k3:1028 *:*
UDP mail2k3:1030 *:*
UDP mail2k3:1032 *:*
UDP mail2k3:1034 *:*
UDP mail2k3:1035 *:*
UDP mail2k3hone *:*
UDP mail2k3:1184 *:*
UDP mail2k3:1241 *:*
UDP mail2k3:1242 *:*
UDP mail2k3:l2tp *:*
UDP mail2k3:3456 *:*
UDP mail2k3:3457 *:*
UDP mail2k3:4500 *:*
UDP mail2k3:38037 *:*
UDP mail2k3:38293 *:*
UDP mail2k3:48982 *:*
UDP mail2k3:49001 *:*
UDP mail2k3:ntp *:*
UDP mail2k3:1047 *:*
UDP mail2k3:1057 *:*
UDP mail2k3:1069 *:*
UDP mail2k3:1078 *:*
UDP mail2k3:1100 *:*
UDP mail2k3:1161 *:*
UDP mail2k3:1173 *:*
UDP mail2k3:1182 *:*
UDP mail2k3:1183 *:*
UDP mail2k3:1219 *:*
UDP mail2k3:1631 *:*
UDP mail2k3:1670 *:*
UDP mail2k3:3456 *:*
UDP mail2k3:3457 *:*
UDP mail2k3:5297 *:*
UDP mail2k3:48984 *:*
UDP mail2k3:48991 *:*
UDP mail2k3:49036 *:*
UDP mail2k3:49039 *:*
UDP mail2k3:bootps *:*
UDP mail2k3:bootpc *:*
UDP mail2k3:ntp *:*
UDP mail2k3:netbios-ns *:*
UDP mail2k3:netbios-dgm *:*
UDP mail2k3:2535 *:*
UDP mail2k3:bootps *:*
UDP mail2k3:ntp *:*
UDP mail2k3:netbios-ns *:*
UDP mail2k3:netbios-dgm *:*




--
Network Administrator
Simon Paston & Sons Agency


"Miha Pihler [MVP]" wrote:

> Hi,
>
> When you try to ping the File2k3 server do you use name or IP address? Does
> it work if you use IP address?
>
> Can you check the event logs on both servers (specially Application and
> System Event logs) and see if there are any errors. Post back with these
> errors...
>
> Can you also post here the results of command
>
> ipconifg /all
>
> from both servers?
>
> --
> Mike
> Microsoft MVP - Windows Security
>
>
> "Chris Baldassano" <(E-Mail Removed)> wrote in
> message news:6876826E-549E-4E4F-80DE-(E-Mail Removed)...
> >I have a server called File2k3. It's a Win2k3 server standard. Global
> > Catalog and Domain Controller.
> >
> > My exchange server is called Mail2k3.
> >
> > When the systems come up, they see eachother just fine... after about an
> > hour, the Mail2k3 box can not ping the file2k3 box, and Outlook/exchange
> > gets
> > awfully slow. I ran a netstat and see a TON of ports to file2k3 in a
> > CLOSE_WAIT state. If i reboot file2k3 (which is also our DNS Server),
> > when
> > it comes up its fine again.
> >
> > File2k3, can ping mail2k3 PERFECTLY everytime (even when Mail2k3 cant ping
> > it)..
> >
> > Both are up to latest service packs and hotfixes...
> >
> > Has anyone seen this before? I am forced to reboot the server 20x a day!
> > --
> > Network Administrator
> > Simon Paston & Sons Agency

>
>
>

 
Reply With Quote
 
Miha Pihler [MVP]
Guest
Posts: n/a

 
      05-01-2006, 03:13 PM
Why do you have IP Routing enabled on both your servers? This is not the
default nor usual setting.

After you try and ping the server and it fails -- can you run the following
command

arp -a

What is the output of the arp command?

--
Mike
Microsoft MVP - Windows Security


"Chris Baldassano" <(E-Mail Removed)> wrote in
message news:FF4AACD6-E0DD-4017-9CE3-(E-Mail Removed)...
>I can not ping by IP, Or by Name from mail2k3 to File2k3... But the other
>way
> around it works perfectally fine (ip or name)...
>
> Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
> secondary one is just not connected... I am gonna hook them up today to
> see
> if it is a NIC issue.. (I doubt it, there would be other factors)...
>
> Little more background:
>
> -File2k3 is our DNS server with the proper ISP DNS's forwarded...
> -File2k3 is our Global Catalog, and Domain Controller
>
> -Mail2k3 WAS a domain controller, that was taken down by 2 microsoft
> tech's
> about 5 days ago on a $245 Support Call.. They did all the proper steps to
> make it Just an exchange server and not anything else.
>
>
>
> Here is the IP config for each machine..
>
> FILE2K3:
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : file2k3
> Primary Dns Suffix . . . . . . . : pastongroup.com
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : pastongroup.com
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : pastongroup.com
> Description . . . . . . . . . . . : 3Com Gigabit NIC
> Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.3
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.3
>
> MAIL2K3:
>
>
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : mail2k3
> Primary Dns Suffix . . . . . . . : pastongroup.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : pastongroup.com
>
>
>
> PPP adapter RAS Server (Dial In) Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.114
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 3Com Gigabit NIC
> Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.30
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.3
>
> ***
>
> Here is the ping from Mail2k3 to File2k3:
>
> Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Ping statistics for 192.168.1.3:
>
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
> And here is From FILE2k3 to MAIL2k3:
>
> Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:
>
> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>
> Ping statistics for 192.168.1.30:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> ***
>
> Now here is what I notice when I do a NETSTAT -A on mail2k3... there are a
> ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
> getting thru and the LDAP etc is failing...
>
> FROM MAIL2K3 (Netstat -a) spit to a txt file.
>
> Active Connections
>
> Proto Local Address Foreign Address State
> TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3ptp mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:http ten11.bwc.na.blackberry.net:34159
> TIME_WAIT
> TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
> TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
> TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
> TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
> TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
> TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
> TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
> TCP mail2k3:691 mail2k3.pastongroup.com:48987 ESTABLISHED
> TCP mail2k3:691 mail2k3.pastongroup.com:48997 ESTABLISHED
> TCP mail2k3:691 mail2k3.pastongroup.com:49052 ESTABLISHED
> TCP mail2k3:691 mail2k3.pastongroup.com:49055 ESTABLISHED
> TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3ptp ool-457251fd.dyn.optonline.net:1151
> ESTABLISHED
> TCP mail2k3ptp ool-457b9bc5.dyn.optonline.net:2912
> ESTABLISHED
> TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
> TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:3916 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3918 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3929 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3930 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3935 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3936 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3937 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3938 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3939 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3940 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3942 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:4459 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:4908 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5325 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5771 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
> ESTABLISHED
> TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn
> TIME_WAIT
> TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
> TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
> TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
> TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
> TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
> TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
> TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
> TCP mail2k3:5934 file2k3.pastongroup.com:domain TIME_WAIT
> TCP mail2k3:5935 file2k3.pastongroup.com:domain TIME_WAIT
> TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
> TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
> TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
> TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
> TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
> TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
> TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
> TCP mail2k3:48998 EXT285:2018 ESTABLISHED
> TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
> TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
> TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED
> TCP mail2k3:48998 ext240.pastongroup.com:1275 ESTABLISHED
> TCP mail2k3:48998 ext292.pastongroup.com:3766 ESTABLISHED
> TCP mail2k3:48998 ext227.pastongroup.com:3811 ESTABLISHED
> TCP mail2k3:48998 ext275.pastongroup.com:1119 ESTABLISHED
> TCP mail2k3:48998 ext297.pastongroup.com:2418 ESTABLISHED
> TCP mail2k3:48998 ext200.pastongroup.com:1251 ESTABLISHED
> TCP mail2k3:48998 ext209.pastongroup.com:1096 ESTABLISHED
> TCP mail2k3:48998 ext299.pastongroup.com:1653 ESTABLISHED
> TCP mail2k3:48998 ext206.pastongroup.com:3831 ESTABLISHED
> TCP mail2k3:48998 ext273.pastongroup.com:3103 ESTABLISHED
> TCP mail2k3:48998 ext236.pastongroup.com:1127 ESTABLISHED
> TCP mail2k3:48998 ext211.pastongroup.com:1266 ESTABLISHED
> TCP mail2k3:48998 ext269.pastongroup.com:1154 ESTABLISHED
> TCP mail2k3:48998 ext217.pastongroup.com:3694 ESTABLISHED
> TCP mail2k3:48998 ext233.pastongroup.com:2778 ESTABLISHED
> TCP mail2k3:48998 ext293.pastongroup.com:2177 ESTABLISHED
> TCP mail2k3:48998 ext276.pastongroup.com:1755 ESTABLISHED
> TCP mail2k3:48998 192.168.1.105:1629 ESTABLISHED
> TCP mail2k3:48998 ext269.pastongroup.com:3829 ESTABLISHED
> TCP mail2k3:48998 ext282.pastongroup.com:2949 ESTABLISHED
> TCP mail2k3:48998 ext282.pastongroup.com:2952 ESTABLISHED
> TCP mail2k3:48998 ira.pastongroup.com:1638 ESTABLISHED
> TCP mail2k3:48998 EXT272:1103 ESTABLISHED
> TCP mail2k3:48998 ext279.pastongroup.com:4178 ESTABLISHED
> TCP mail2k3:48998 ext277.pastongroup.com:4431 ESTABLISHED
> TCP mail2k3:48998 ext248.pastongroup.com:1114 ESTABLISHED
> TCP mail2k3:48998 ext234.pastongroup.com:4836 ESTABLISHED
> TCP mail2k3:48998 ext288.pastongroup.com:2854 ESTABLISHED
> TCP mail2k3:48998 scottxp.pastongroup.com:3144 ESTABLISHED
> TCP mail2k3:49052 mail2k3.pastongroup.com:691 ESTABLISHED
> TCP mail2k3:49055 mail2k3.pastongroup.com:691 ESTABLISHED
> TCP mail2k3:50087 file2k3.pastongroup.com:1025 ESTABLISHED
> TCP mail2k3:50094 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:50095 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:50098 file2k3.pastongroup.com:3268 CLOSE_WAIT
> TCP mail2k3:50099 file2k3.pastongroup.com:3268 CLOSE_WAIT
> TCP mail2k3:53777 file2k3.pastongroup.com:1025 ESTABLISHED
> TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
> UDP mail2k3:epmap *:*
> UDP mail2k3:microsoft-ds *:*
> UDP mail2k3:isakmp *:*
> UDP mail2k3:1025 *:*
> UDP mail2k3:1026 *:*
> UDP mail2k3:1027 *:*
> UDP mail2k3:1028 *:*
> UDP mail2k3:1030 *:*
> UDP mail2k3:1032 *:*
> UDP mail2k3:1034 *:*
> UDP mail2k3:1035 *:*
> UDP mail2k3hone *:*
> UDP mail2k3:1184 *:*
> UDP mail2k3:1241 *:*
> UDP mail2k3:1242 *:*
> UDP mail2k3:l2tp *:*
> UDP mail2k3:3456 *:*
> UDP mail2k3:3457 *:*
> UDP mail2k3:4500 *:*
> UDP mail2k3:38037 *:*
> UDP mail2k3:38293 *:*
> UDP mail2k3:48982 *:*
> UDP mail2k3:49001 *:*
> UDP mail2k3:ntp *:*
> UDP mail2k3:1047 *:*
> UDP mail2k3:1057 *:*
> UDP mail2k3:1069 *:*
> UDP mail2k3:1078 *:*
> UDP mail2k3:1100 *:*
> UDP mail2k3:1161 *:*
> UDP mail2k3:1173 *:*
> UDP mail2k3:1182 *:*
> UDP mail2k3:1183 *:*
> UDP mail2k3:1219 *:*
> UDP mail2k3:1631 *:*
> UDP mail2k3:1670 *:*
> UDP mail2k3:3456 *:*
> UDP mail2k3:3457 *:*
> UDP mail2k3:5297 *:*
> UDP mail2k3:48984 *:*
> UDP mail2k3:48991 *:*
> UDP mail2k3:49036 *:*
> UDP mail2k3:49039 *:*
> UDP mail2k3:bootps *:*
> UDP mail2k3:bootpc *:*
> UDP mail2k3:ntp *:*
> UDP mail2k3:netbios-ns *:*
> UDP mail2k3:netbios-dgm *:*
> UDP mail2k3:2535 *:*
> UDP mail2k3:bootps *:*
> UDP mail2k3:ntp *:*
> UDP mail2k3:netbios-ns *:*
> UDP mail2k3:netbios-dgm *:*
>
>
>
>
> --
> Network Administrator
> Simon Paston & Sons Agency
>
>
> "Miha Pihler [MVP]" wrote:
>
>> Hi,
>>
>> When you try to ping the File2k3 server do you use name or IP address?
>> Does
>> it work if you use IP address?
>>
>> Can you check the event logs on both servers (specially Application and
>> System Event logs) and see if there are any errors. Post back with these
>> errors...
>>
>> Can you also post here the results of command
>>
>> ipconifg /all
>>
>> from both servers?
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>>
>> "Chris Baldassano" <(E-Mail Removed)> wrote in
>> message news:6876826E-549E-4E4F-80DE-(E-Mail Removed)...
>> >I have a server called File2k3. It's a Win2k3 server standard. Global
>> > Catalog and Domain Controller.
>> >
>> > My exchange server is called Mail2k3.
>> >
>> > When the systems come up, they see eachother just fine... after about
>> > an
>> > hour, the Mail2k3 box can not ping the file2k3 box, and
>> > Outlook/exchange
>> > gets
>> > awfully slow. I ran a netstat and see a TON of ports to file2k3 in a
>> > CLOSE_WAIT state. If i reboot file2k3 (which is also our DNS Server),
>> > when
>> > it comes up its fine again.
>> >
>> > File2k3, can ping mail2k3 PERFECTLY everytime (even when Mail2k3 cant
>> > ping
>> > it)..
>> >
>> > Both are up to latest service packs and hotfixes...
>> >
>> > Has anyone seen this before? I am forced to reboot the server 20x a
>> > day!
>> > --
>> > Network Administrator
>> > Simon Paston & Sons Agency

>>
>>
>>



 
Reply With Quote
 
Chris Baldassano
Guest
Posts: n/a

 
      05-01-2006, 03:18 PM
An Additional note:

I enabled the secondary NIC's (File2k3 @ 192.168.1.20, MAIL2k3 @
192.168.1.21) and Added the DNS Record in the DNS Lookup Zones...

Mail can now ping File Perfectly to 192.168.1.20, but it still times out on
192.168.1.3...

This is not acceptable because the /20 address is also going thru a 100 meg
switch and not the gigabit router.. just an FYI.

I did a ipconfig /flushdns on the mail2k3 server so it would see the DNS
change.

This is VERY Strange.
--
Network Administrator
Simon Paston & Sons Agency


"Chris Baldassano" wrote:

> I can not ping by IP, Or by Name from mail2k3 to File2k3... But the other way
> around it works perfectally fine (ip or name)...
>
> Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
> secondary one is just not connected... I am gonna hook them up today to see
> if it is a NIC issue.. (I doubt it, there would be other factors)...
>
> Little more background:
>
> -File2k3 is our DNS server with the proper ISP DNS's forwarded...
> -File2k3 is our Global Catalog, and Domain Controller
>
> -Mail2k3 WAS a domain controller, that was taken down by 2 microsoft tech's
> about 5 days ago on a $245 Support Call.. They did all the proper steps to
> make it Just an exchange server and not anything else.
>
>
>
> Here is the IP config for each machine..
>
> FILE2K3:
>
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : file2k3
> Primary Dns Suffix . . . . . . . : pastongroup.com
> Node Type . . . . . . . . . . . . : Broadcast
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : pastongroup.com
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . : pastongroup.com
> Description . . . . . . . . . . . : 3Com Gigabit NIC
> Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.3
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.3
>
> MAIL2K3:
>
>
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : mail2k3
> Primary Dns Suffix . . . . . . . : pastongroup.com
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : Yes
> WINS Proxy Enabled. . . . . . . . : Yes
> DNS Suffix Search List. . . . . . : pastongroup.com
>
>
>
> PPP adapter RAS Server (Dial In) Interface:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.114
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> Default Gateway . . . . . . . . . :
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : 3Com Gigabit NIC
> Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.1.30
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.1.1
> DNS Servers . . . . . . . . . . . : 192.168.1.3
>
> ***
>
> Here is the ping from Mail2k3 to File2k3:
>
> Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Ping statistics for 192.168.1.3:
>
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
> And here is From FILE2k3 to MAIL2k3:
>
> Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:
>
> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>
> Ping statistics for 192.168.1.30:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> ***
>
> Now here is what I notice when I do a NETSTAT -A on mail2k3... there are a
> ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
> getting thru and the LDAP etc is failing...
>
> FROM MAIL2K3 (Netstat -a) spit to a txt file.
>
> Active Connections
>
> Proto Local Address Foreign Address State
> TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3ptp mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:http ten11.bwc.na.blackberry.net:34159 TIME_WAIT
> TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
> TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
> TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
> TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
> TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
> TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
> TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
> TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
> TCP mail2k3:691 mail2k3.pastongroup.com:48987 ESTABLISHED
> TCP mail2k3:691 mail2k3.pastongroup.com:48997 ESTABLISHED
> TCP mail2k3:691 mail2k3.pastongroup.com:49052 ESTABLISHED
> TCP mail2k3:691 mail2k3.pastongroup.com:49055 ESTABLISHED
> TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3ptp ool-457251fd.dyn.optonline.net:1151
> ESTABLISHED
> TCP mail2k3ptp ool-457b9bc5.dyn.optonline.net:2912
> ESTABLISHED
> TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
> TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:3916 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3918 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3929 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3930 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3935 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3936 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3937 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3938 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3939 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3940 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3942 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:4459 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:4908 file2k3.pastongroup.com:3268 ESTABLISHED
> TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5325 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5771 file2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
> TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
> ESTABLISHED
> TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn TIME_WAIT
> TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
> TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
> TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
> TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
> TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
> TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
> TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
> TCP mail2k3:5934 file2k3.pastongroup.com:domain TIME_WAIT
> TCP mail2k3:5935 file2k3.pastongroup.com:domain TIME_WAIT
> TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
> TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
> ESTABLISHED
> TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
> TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
> TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
> TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
> TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
> TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
> TCP mail2k3:48998 EXT285:2018 ESTABLISHED
> TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
> TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
> TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED
> TCP mail2k3:48998 ext240.pastongroup.com:1275 ESTABLISHED
> TCP mail2k3:48998 ext292.pastongroup.com:3766 ESTABLISHED
> TCP mail2k3:48998 ext227.pastongroup.com:3811 ESTABLISHED
> TCP mail2k3:48998 ext275.pastongroup.com:1119 ESTABLISHED
> TCP mail2k3:48998 ext297.pastongroup.com:2418 ESTABLISHED
> TCP mail2k3:48998 ext200.pastongroup.com:1251 ESTABLISHED
> TCP mail2k3:48998 ext209.pastongroup.com:1096 ESTABLISHED
> TCP mail2k3:48998 ext299.pastongroup.com:1653 ESTABLISHED
> TCP mail2k3:48998 ext206.pastongroup.com:3831 ESTABLISHED
> TCP mail2k3:48998 ext273.pastongroup.com:3103 ESTABLISHED
> TCP mail2k3:48998 ext236.pastongroup.com:1127 ESTABLISHED
> TCP mail2k3:48998 ext211.pastongroup.com:1266 ESTABLISHED
> TCP mail2k3:48998 ext269.pastongroup.com:1154 ESTABLISHED
> TCP mail2k3:48998 ext217.pastongroup.com:3694 ESTABLISHED
> TCP mail2k3:48998 ext233.pastongroup.com:2778 ESTABLISHED
> TCP mail2k3:48998 ext293.pastongroup.com:2177 ESTABLISHED
> TCP mail2k3:48998 ext276.pastongroup.com:1755 ESTABLISHED
> TCP mail2k3:48998 192.168.1.105:1629 ESTABLISHED
> TCP mail2k3:48998 ext269.pastongroup.com:3829 ESTABLISHED
> TCP mail2k3:48998 ext282.pastongroup.com:2949 ESTABLISHED
> TCP mail2k3:48998 ext282.pastongroup.com:2952 ESTABLISHED
> TCP mail2k3:48998 ira.pastongroup.com:1638 ESTABLISHED
> TCP mail2k3:48998 EXT272:1103 ESTABLISHED
> TCP mail2k3:48998 ext279.pastongroup.com:4178 ESTABLISHED
> TCP mail2k3:48998 ext277.pastongroup.com:4431 ESTABLISHED
> TCP mail2k3:48998 ext248.pastongroup.com:1114 ESTABLISHED
> TCP mail2k3:48998 ext234.pastongroup.com:4836 ESTABLISHED
> TCP mail2k3:48998 ext288.pastongroup.com:2854 ESTABLISHED
> TCP mail2k3:48998 scottxp.pastongroup.com:3144 ESTABLISHED
> TCP mail2k3:49052 mail2k3.pastongroup.com:691 ESTABLISHED
> TCP mail2k3:49055 mail2k3.pastongroup.com:691 ESTABLISHED
> TCP mail2k3:50087 file2k3.pastongroup.com:1025 ESTABLISHED
> TCP mail2k3:50094 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:50095 file2k3.pastongroup.com:ldap CLOSE_WAIT
> TCP mail2k3:50098 file2k3.pastongroup.com:3268 CLOSE_WAIT
> TCP mail2k3:50099 file2k3.pastongroup.com:3268 CLOSE_WAIT
> TCP mail2k3:53777 file2k3.pastongroup.com:1025 ESTABLISHED
> TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
> UDP mail2k3:epmap *:*
> UDP mail2k3:microsoft-ds *:*
> UDP mail2k3:isakmp *:*
> UDP mail2k3:1025 *:*
> UDP mail2k3:1026 *:*
> UDP mail2k3:1027 *:*
> UDP mail2k3:1028 *:*
> UDP mail2k3:1030 *:*
> UDP mail2k3:1032 *:*
> UDP mail2k3:1034 *:*
> UDP mail2k3:1035 *:*
> UDP mail2k3hone *:*
> UDP mail2k3:1184 *:*
> UDP mail2k3:1241 *:*
> UDP mail2k3:1242 *:*
> UDP mail2k3:l2tp *:*
> UDP mail2k3:3456 *:*

 
Reply With Quote
 
Chris Baldassano
Guest
Posts: n/a

 
      05-01-2006, 03:32 PM
I dont know why IP routing is on.. I did not setup these servers, an
outsource company did.. Should I turn that off? We have a simple network
here with no need for specific routes.. We have 1 gateway for our internet
and 3 servers, 50 workstations. No remote offices etc...

Here is the command from both machines:


FILE2K3

Interface: 192.168.1.30 --- 0x10003
Internet Address Physical Address Type
192.168.1.1 00-0f-b5-8c-85-7b dynamic
192.168.1.3 00-0a-5e-1a-01-41 dynamic
192.168.1.7 00-0a-5e-1a-02-f1 dynamic
192.168.1.8 00-14-22-0a-19-9a dynamic
192.168.1.31 00-0a-5e-1a-b9-9b dynamic
192.168.1.43 00-0c-f1-92-cd-46 dynamic
192.168.1.44 00-0c-f1-92-c6-90 dynamic
192.168.1.46 00-0c-f1-92-cc-f0 dynamic
192.168.1.48 00-0c-f1-92-cd-5d dynamic
192.168.1.49 00-0c-f1-92-51-50 dynamic
192.168.1.53 00-0c-f1-92-f7-c8 dynamic
192.168.1.55 00-0c-f1-92-de-fe dynamic
192.168.1.58 00-0c-f1-92-f8-1c dynamic
192.168.1.60 00-0c-f1-92-cd-76 dynamic
192.168.1.63 00-0c-f1-92-df-dd dynamic
192.168.1.64 00-0c-f1-92-f7-ff dynamic
192.168.1.65 00-0c-f1-92-df-30 dynamic
192.168.1.66 00-0c-f1-92-f6-e7 dynamic
192.168.1.67 00-0c-f1-92-c3-07 dynamic
192.168.1.68 00-0c-f1-92-f7-88 dynamic
192.168.1.69 00-0c-f1-92-df-14 dynamic
192.168.1.70 00-0c-f1-92-c7-c3 dynamic
192.168.1.71 00-0c-f1-92-cb-d6 dynamic
192.168.1.72 00-0c-f1-92-cc-fb dynamic
192.168.1.73 00-0c-f1-92-de-1c dynamic
192.168.1.74 00-0c-f1-92-f8-65 dynamic
192.168.1.104 00-10-83-59-d0-f6 dynamic
192.168.1.107 00-60-b0-41-f6-1a dynamic
192.168.1.109 00-01-e6-3b-b4-0b dynamic
192.168.1.125 00-0c-f1-92-ef-0c dynamic
192.168.1.127 00-0c-f1-92-f7-bd dynamic
192.168.1.130 00-0c-f1-92-df-42 dynamic
192.168.1.131 00-0c-f1-92-cc-ae dynamic
192.168.1.146 00-0c-f1-92-f3-a9 dynamic
192.168.1.155 08-00-09-bd-f6-54 dynamic
192.168.1.156 00-0c-f1-92-c6-9a dynamic
192.168.1.159 00-0c-f1-92-de-65 dynamic
192.168.1.191 00-08-0d-90-3c-2a dynamic
192.168.1.200 08-00-09-bd-16-43 dynamic
192.168.1.202 00-01-e6-7e-c3-6b dynamic
192.168.1.223 00-0c-f1-92-f8-26 dynamic
192.168.1.227 00-0c-f1-92-51-93 dynamic
192.168.1.252 00-11-85-fb-26-7b dynamic


Interface: 192.168.1.3 --- 0x10003
Internet Address Physical Address Type
192.168.1.1 00-0f-b5-8c-85-7b dynamic
192.168.1.7 00-0a-5e-1a-02-f1 dynamic
192.168.1.8 00-14-22-0a-19-9a dynamic
192.168.1.30 00-0a-5e-1a-02-c3 dynamic
192.168.1.31 00-0a-5e-1a-b9-9b dynamic
192.168.1.40 00-0c-f1-92-e5-de dynamic
192.168.1.42 00-0c-f1-92-46-d1 dynamic
192.168.1.43 00-0c-f1-92-cd-46 dynamic
192.168.1.44 00-0c-f1-92-c6-90 dynamic
192.168.1.45 00-0c-f1-92-e5-a4 dynamic
192.168.1.46 00-0c-f1-92-cc-f0 dynamic
192.168.1.48 00-0c-f1-92-cd-5d dynamic
192.168.1.49 00-0c-f1-92-51-50 dynamic
192.168.1.53 00-0c-f1-92-f7-c8 dynamic
192.168.1.55 00-0c-f1-92-de-fe dynamic
192.168.1.56 00-0c-f1-92-cd-3b dynamic
192.168.1.58 00-0c-f1-92-f8-1c dynamic
192.168.1.59 00-0c-f1-92-dc-ae dynamic
192.168.1.63 00-0c-f1-92-df-dd dynamic
192.168.1.64 00-0c-f1-92-f7-ff dynamic
192.168.1.65 00-0c-f1-92-df-30 dynamic
192.168.1.66 00-0c-f1-92-f6-e7 dynamic
192.168.1.67 00-0c-f1-92-c3-07 dynamic
192.168.1.68 00-0c-f1-92-f7-88 dynamic
192.168.1.69 00-0c-f1-92-df-14 dynamic
192.168.1.70 00-0c-f1-92-c7-c3 dynamic
192.168.1.71 00-0c-f1-92-cb-d6 dynamic
192.168.1.72 00-0c-f1-92-cc-fb dynamic
192.168.1.73 00-0c-f1-92-de-1c dynamic
192.168.1.74 00-0c-f1-92-f8-65 dynamic
192.168.1.88 00-0c-f1-92-f7-ea dynamic
192.168.1.114 00-0a-5e-1a-02-c3 dynamic
192.168.1.125 00-0c-f1-92-ef-0c dynamic
192.168.1.127 00-0c-f1-92-f7-bd dynamic
192.168.1.130 00-0c-f1-92-df-42 dynamic
192.168.1.131 00-0c-f1-92-cc-ae dynamic
192.168.1.146 00-0c-f1-92-f3-a9 dynamic
192.168.1.156 00-0c-f1-92-c6-9a dynamic
192.168.1.159 00-0c-f1-92-de-65 dynamic
192.168.1.164 00-0c-f1-92-f8-6d dynamic
192.168.1.223 00-0c-f1-92-f8-26 dynamic


MAIL2K3:



--
Network Administrator
Simon Paston & Sons Agency


"Miha Pihler [MVP]" wrote:

> Why do you have IP Routing enabled on both your servers? This is not the
> default nor usual setting.
>
> After you try and ping the server and it fails -- can you run the following
> command
>
> arp -a
>
> What is the output of the arp command?
>
> --
> Mike
> Microsoft MVP - Windows Security
>
>
> "Chris Baldassano" <(E-Mail Removed)> wrote in
> message news:FF4AACD6-E0DD-4017-9CE3-(E-Mail Removed)...
> >I can not ping by IP, Or by Name from mail2k3 to File2k3... But the other
> >way
> > around it works perfectally fine (ip or name)...
> >
> > Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
> > secondary one is just not connected... I am gonna hook them up today to
> > see
> > if it is a NIC issue.. (I doubt it, there would be other factors)...
> >
> > Little more background:
> >
> > -File2k3 is our DNS server with the proper ISP DNS's forwarded...
> > -File2k3 is our Global Catalog, and Domain Controller
> >
> > -Mail2k3 WAS a domain controller, that was taken down by 2 microsoft
> > tech's
> > about 5 days ago on a $245 Support Call.. They did all the proper steps to
> > make it Just an exchange server and not anything else.
> >
> >
> >
> > Here is the IP config for each machine..
> >
> > FILE2K3:
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : file2k3
> > Primary Dns Suffix . . . . . . . : pastongroup.com
> > Node Type . . . . . . . . . . . . : Broadcast
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : Yes
> > DNS Suffix Search List. . . . . . : pastongroup.com
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . : pastongroup.com
> > Description . . . . . . . . . . . : 3Com Gigabit NIC
> > Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.1.3
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.1.1
> > DNS Servers . . . . . . . . . . . : 192.168.1.3
> >
> > MAIL2K3:
> >
> >
> >
> > Windows IP Configuration
> >
> >
> >
> > Host Name . . . . . . . . . . . . : mail2k3
> > Primary Dns Suffix . . . . . . . : pastongroup.com
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : Yes
> > DNS Suffix Search List. . . . . . : pastongroup.com
> >
> >
> >
> > PPP adapter RAS Server (Dial In) Interface:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> > Physical Address. . . . . . . . . : 00-53-45-00-00-00
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.1.114
> > Subnet Mask . . . . . . . . . . . : 255.255.255.255
> > Default Gateway . . . . . . . . . :
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : 3Com Gigabit NIC
> > Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.1.30
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.1.1
> > DNS Servers . . . . . . . . . . . : 192.168.1.3
> >
> > ***
> >
> > Here is the ping from Mail2k3 to File2k3:
> >
> > Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
> > Request timed out.
> > Request timed out.
> > Request timed out.
> > Request timed out.
> > Ping statistics for 192.168.1.3:
> >
> > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> >
> > And here is From FILE2k3 to MAIL2k3:
> >
> > Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:
> >
> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> >
> > Ping statistics for 192.168.1.30:
> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 0ms, Maximum = 0ms, Average = 0ms
> >
> > ***
> >
> > Now here is what I notice when I do a NETSTAT -A on mail2k3... there are a
> > ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
> > getting thru and the LDAP etc is failing...
> >
> > FROM MAIL2K3 (Netstat -a) spit to a txt file.
> >
> > Active Connections
> >
> > Proto Local Address Foreign Address State
> > TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3ptp mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:http ten11.bwc.na.blackberry.net:34159
> > TIME_WAIT
> > TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
> > TCP mail2k3:691 mail2k3.pastongroup.com:48987 ESTABLISHED
> > TCP mail2k3:691 mail2k3.pastongroup.com:48997 ESTABLISHED
> > TCP mail2k3:691 mail2k3.pastongroup.com:49052 ESTABLISHED
> > TCP mail2k3:691 mail2k3.pastongroup.com:49055 ESTABLISHED
> > TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3ptp ool-457251fd.dyn.optonline.net:1151
> > ESTABLISHED
> > TCP mail2k3ptp ool-457b9bc5.dyn.optonline.net:2912
> > ESTABLISHED
> > TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
> > TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:3916 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3918 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3929 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3930 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3935 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3936 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3937 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3938 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3939 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3940 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3942 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:4459 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:4908 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5325 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5771 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
> > ESTABLISHED
> > TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn
> > TIME_WAIT
> > TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
> > TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
> > TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
> > TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
> > TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
> > TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
> > TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
> > TCP mail2k3:5934 file2k3.pastongroup.com:domain TIME_WAIT
> > TCP mail2k3:5935 file2k3.pastongroup.com:domain TIME_WAIT
> > TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
> > TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
> > TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
> > TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
> > TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
> > TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
> > TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
> > TCP mail2k3:48998 EXT285:2018 ESTABLISHED
> > TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
> > TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
> > TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED
> > TCP mail2k3:48998 ext240.pastongroup.com:1275 ESTABLISHED
> > TCP mail2k3:48998 ext292.pastongroup.com:3766 ESTABLISHED
> > TCP mail2k3:48998 ext227.pastongroup.com:3811 ESTABLISHED
> > TCP mail2k3:48998 ext275.pastongroup.com:1119 ESTABLISHED
> > TCP mail2k3:48998 ext297.pastongroup.com:2418 ESTABLISHED
> > TCP mail2k3:48998 ext200.pastongroup.com:1251 ESTABLISHED
> > TCP mail2k3:48998 ext209.pastongroup.com:1096 ESTABLISHED
> > TCP mail2k3:48998 ext299.pastongroup.com:1653 ESTABLISHED
> > TCP mail2k3:48998 ext206.pastongroup.com:3831 ESTABLISHED
> > TCP mail2k3:48998 ext273.pastongroup.com:3103 ESTABLISHED
> > TCP mail2k3:48998 ext236.pastongroup.com:1127 ESTABLISHED
> > TCP mail2k3:48998 ext211.pastongroup.com:1266 ESTABLISHED
> > TCP mail2k3:48998 ext269.pastongroup.com:1154 ESTABLISHED
> > TCP mail2k3:48998 ext217.pastongroup.com:3694 ESTABLISHED
> > TCP mail2k3:48998 ext233.pastongroup.com:2778 ESTABLISHED
> > TCP mail2k3:48998 ext293.pastongroup.com:2177 ESTABLISHED
> > TCP mail2k3:48998 ext276.pastongroup.com:1755 ESTABLISHED
> > TCP mail2k3:48998 192.168.1.105:1629 ESTABLISHED
> > TCP mail2k3:48998 ext269.pastongroup.com:3829 ESTABLISHED
> > TCP mail2k3:48998 ext282.pastongroup.com:2949 ESTABLISHED
> > TCP mail2k3:48998 ext282.pastongroup.com:2952 ESTABLISHED
> > TCP mail2k3:48998 ira.pastongroup.com:1638 ESTABLISHED
> > TCP mail2k3:48998 EXT272:1103 ESTABLISHED
> > TCP mail2k3:48998 ext279.pastongroup.com:4178 ESTABLISHED
> > TCP mail2k3:48998 ext277.pastongroup.com:4431 ESTABLISHED
> > TCP mail2k3:48998 ext248.pastongroup.com:1114 ESTABLISHED
> > TCP mail2k3:48998 ext234.pastongroup.com:4836 ESTABLISHED
> > TCP mail2k3:48998 ext288.pastongroup.com:2854 ESTABLISHED
> > TCP mail2k3:48998 scottxp.pastongroup.com:3144 ESTABLISHED
> > TCP mail2k3:49052 mail2k3.pastongroup.com:691 ESTABLISHED
> > TCP mail2k3:49055 mail2k3.pastongroup.com:691 ESTABLISHED
> > TCP mail2k3:50087 file2k3.pastongroup.com:1025 ESTABLISHED
> > TCP mail2k3:50094 file2k3.pastongroup.com:ldap CLOSE_WAIT

 
Reply With Quote
 
Chris Baldassano
Guest
Posts: n/a

 
      05-01-2006, 03:39 PM
I think the IP routing was enabled because of the dual NIC's in the system...
When i went into RRAS it shows:

LOOPBACK 127.0.0.1
LOCAL AREA CONNECTION 192.168.1.30
INTERNAL 192.168.1.114

Note that Mail2k3 is also our VPN EndPoint / DHCP Server.
--
Network Administrator
Simon Paston & Sons Agency


"Miha Pihler [MVP]" wrote:

> Why do you have IP Routing enabled on both your servers? This is not the
> default nor usual setting.
>
> After you try and ping the server and it fails -- can you run the following
> command
>
> arp -a
>
> What is the output of the arp command?
>
> --
> Mike
> Microsoft MVP - Windows Security
>
>
> "Chris Baldassano" <(E-Mail Removed)> wrote in
> message news:FF4AACD6-E0DD-4017-9CE3-(E-Mail Removed)...
> >I can not ping by IP, Or by Name from mail2k3 to File2k3... But the other
> >way
> > around it works perfectally fine (ip or name)...
> >
> > Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
> > secondary one is just not connected... I am gonna hook them up today to
> > see
> > if it is a NIC issue.. (I doubt it, there would be other factors)...
> >
> > Little more background:
> >
> > -File2k3 is our DNS server with the proper ISP DNS's forwarded...
> > -File2k3 is our Global Catalog, and Domain Controller
> >
> > -Mail2k3 WAS a domain controller, that was taken down by 2 microsoft
> > tech's
> > about 5 days ago on a $245 Support Call.. They did all the proper steps to
> > make it Just an exchange server and not anything else.
> >
> >
> >
> > Here is the IP config for each machine..
> >
> > FILE2K3:
> >
> > Windows IP Configuration
> >
> > Host Name . . . . . . . . . . . . : file2k3
> > Primary Dns Suffix . . . . . . . : pastongroup.com
> > Node Type . . . . . . . . . . . . : Broadcast
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : Yes
> > DNS Suffix Search List. . . . . . : pastongroup.com
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . : pastongroup.com
> > Description . . . . . . . . . . . : 3Com Gigabit NIC
> > Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.1.3
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.1.1
> > DNS Servers . . . . . . . . . . . : 192.168.1.3
> >
> > MAIL2K3:
> >
> >
> >
> > Windows IP Configuration
> >
> >
> >
> > Host Name . . . . . . . . . . . . : mail2k3
> > Primary Dns Suffix . . . . . . . : pastongroup.com
> > Node Type . . . . . . . . . . . . : Unknown
> > IP Routing Enabled. . . . . . . . : Yes
> > WINS Proxy Enabled. . . . . . . . : Yes
> > DNS Suffix Search List. . . . . . : pastongroup.com
> >
> >
> >
> > PPP adapter RAS Server (Dial In) Interface:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> > Physical Address. . . . . . . . . : 00-53-45-00-00-00
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.1.114
> > Subnet Mask . . . . . . . . . . . : 255.255.255.255
> > Default Gateway . . . . . . . . . :
> >
> > Ethernet adapter Local Area Connection:
> >
> > Connection-specific DNS Suffix . :
> > Description . . . . . . . . . . . : 3Com Gigabit NIC
> > Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
> > DHCP Enabled. . . . . . . . . . . : No
> > IP Address. . . . . . . . . . . . : 192.168.1.30
> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > Default Gateway . . . . . . . . . : 192.168.1.1
> > DNS Servers . . . . . . . . . . . : 192.168.1.3
> >
> > ***
> >
> > Here is the ping from Mail2k3 to File2k3:
> >
> > Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
> > Request timed out.
> > Request timed out.
> > Request timed out.
> > Request timed out.
> > Ping statistics for 192.168.1.3:
> >
> > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> >
> > And here is From FILE2k3 to MAIL2k3:
> >
> > Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:
> >
> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> >
> > Ping statistics for 192.168.1.30:
> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> > Approximate round trip times in milli-seconds:
> > Minimum = 0ms, Maximum = 0ms, Average = 0ms
> >
> > ***
> >
> > Now here is what I notice when I do a NETSTAT -A on mail2k3... there are a
> > ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
> > getting thru and the LDAP etc is failing...
> >
> > FROM MAIL2K3 (Netstat -a) spit to a txt file.
> >
> > Active Connections
> >
> > Proto Local Address Foreign Address State
> > TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3ptp mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:http ten11.bwc.na.blackberry.net:34159
> > TIME_WAIT
> > TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
> > TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
> > TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
> > TCP mail2k3:691 mail2k3.pastongroup.com:48987 ESTABLISHED
> > TCP mail2k3:691 mail2k3.pastongroup.com:48997 ESTABLISHED
> > TCP mail2k3:691 mail2k3.pastongroup.com:49052 ESTABLISHED
> > TCP mail2k3:691 mail2k3.pastongroup.com:49055 ESTABLISHED
> > TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3ptp ool-457251fd.dyn.optonline.net:1151
> > ESTABLISHED
> > TCP mail2k3ptp ool-457b9bc5.dyn.optonline.net:2912
> > ESTABLISHED
> > TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
> > TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:3916 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3918 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3929 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3930 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3935 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3936 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3937 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3938 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3939 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3940 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3942 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:4459 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:4908 file2k3.pastongroup.com:3268 ESTABLISHED
> > TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5325 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
> > TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5771 file2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
> > TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
> > ESTABLISHED
> > TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn
> > TIME_WAIT
> > TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
> > TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
> > TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
> > TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
> > TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
> > TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
> > TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
> > TCP mail2k3:5934 file2k3.pastongroup.com:domain TIME_WAIT
> > TCP mail2k3:5935 file2k3.pastongroup.com:domain TIME_WAIT
> > TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
> > TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
> > ESTABLISHED
> > TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
> > TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
> > TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
> > TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
> > TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
> > TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
> > TCP mail2k3:48998 EXT285:2018 ESTABLISHED
> > TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
> > TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
> > TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED
> > TCP mail2k3:48998 ext240.pastongroup.com:1275 ESTABLISHED
> > TCP mail2k3:48998 ext292.pastongroup.com:3766 ESTABLISHED
> > TCP mail2k3:48998 ext227.pastongroup.com:3811 ESTABLISHED
> > TCP mail2k3:48998 ext275.pastongroup.com:1119 ESTABLISHED
> > TCP mail2k3:48998 ext297.pastongroup.com:2418 ESTABLISHED
> > TCP mail2k3:48998 ext200.pastongroup.com:1251 ESTABLISHED
> > TCP mail2k3:48998 ext209.pastongroup.com:1096 ESTABLISHED
> > TCP mail2k3:48998 ext299.pastongroup.com:1653 ESTABLISHED
> > TCP mail2k3:48998 ext206.pastongroup.com:3831 ESTABLISHED
> > TCP mail2k3:48998 ext273.pastongroup.com:3103 ESTABLISHED
> > TCP mail2k3:48998 ext236.pastongroup.com:1127 ESTABLISHED
> > TCP mail2k3:48998 ext211.pastongroup.com:1266 ESTABLISHED
> > TCP mail2k3:48998 ext269.pastongroup.com:1154 ESTABLISHED
> > TCP mail2k3:48998 ext217.pastongroup.com:3694 ESTABLISHED
> > TCP mail2k3:48998 ext233.pastongroup.com:2778 ESTABLISHED
> > TCP mail2k3:48998 ext293.pastongroup.com:2177 ESTABLISHED
> > TCP mail2k3:48998 ext276.pastongroup.com:1755 ESTABLISHED
> > TCP mail2k3:48998 192.168.1.105:1629 ESTABLISHED
> > TCP mail2k3:48998 ext269.pastongroup.com:3829 ESTABLISHED
> > TCP mail2k3:48998 ext282.pastongroup.com:2949 ESTABLISHED
> > TCP mail2k3:48998 ext282.pastongroup.com:2952 ESTABLISHED
> > TCP mail2k3:48998 ira.pastongroup.com:1638 ESTABLISHED
> > TCP mail2k3:48998 EXT272:1103 ESTABLISHED
> > TCP mail2k3:48998 ext279.pastongroup.com:4178 ESTABLISHED
> > TCP mail2k3:48998 ext277.pastongroup.com:4431 ESTABLISHED
> > TCP mail2k3:48998 ext248.pastongroup.com:1114 ESTABLISHED
> > TCP mail2k3:48998 ext234.pastongroup.com:4836 ESTABLISHED
> > TCP mail2k3:48998 ext288.pastongroup.com:2854 ESTABLISHED
> > TCP mail2k3:48998 scottxp.pastongroup.com:3144 ESTABLISHED
> > TCP mail2k3:49052 mail2k3.pastongroup.com:691 ESTABLISHED
> > TCP mail2k3:49055 mail2k3.pastongroup.com:691 ESTABLISHED
> > TCP mail2k3:50087 file2k3.pastongroup.com:1025 ESTABLISHED
> > TCP mail2k3:50094 file2k3.pastongroup.com:ldap CLOSE_WAIT

 
Reply With Quote
 
Miha Pihler [MVP]
Guest
Posts: n/a

 
      05-01-2006, 03:45 PM
Hi,

In general Active Directory server should not be multihomed (multiple
NIC) -- (not a recommended configuration). There are quite a few problems
when domain controller is multihomed... Here are few of them...

Troubleshooting browser Event ID 8021 and 8032 on master browsers
http://support.microsoft.com/?id=135404

Clients cannot log on to domain controllers that are Windows Server
2003-based DNS servers, and network interfaces that are not registered in
DNS can still perform dynamic updates
http://support.microsoft.com/default...b;en-us;832478

--
Mike
Microsoft MVP - Windows Security

"Chris Baldassano" <(E-Mail Removed)> wrote in
message news:8DDD4FFB-509F-4A55-AB32-(E-Mail Removed)...
> An Additional note:
>
> I enabled the secondary NIC's (File2k3 @ 192.168.1.20, MAIL2k3 @
> 192.168.1.21) and Added the DNS Record in the DNS Lookup Zones...
>
> Mail can now ping File Perfectly to 192.168.1.20, but it still times out
> on
> 192.168.1.3...
>
> This is not acceptable because the /20 address is also going thru a 100
> meg
> switch and not the gigabit router.. just an FYI.
>
> I did a ipconfig /flushdns on the mail2k3 server so it would see the DNS
> change.
>
> This is VERY Strange.
> --
> Network Administrator
> Simon Paston & Sons Agency
>
>
> "Chris Baldassano" wrote:
>
>> I can not ping by IP, Or by Name from mail2k3 to File2k3... But the other
>> way
>> around it works perfectally fine (ip or name)...
>>
>> Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
>> secondary one is just not connected... I am gonna hook them up today to
>> see
>> if it is a NIC issue.. (I doubt it, there would be other factors)...
>>
>> Little more background:
>>
>> -File2k3 is our DNS server with the proper ISP DNS's forwarded...
>> -File2k3 is our Global Catalog, and Domain Controller
>>
>> -Mail2k3 WAS a domain controller, that was taken down by 2 microsoft
>> tech's
>> about 5 days ago on a $245 Support Call.. They did all the proper steps
>> to
>> make it Just an exchange server and not anything else.
>>
>>
>>
>> Here is the IP config for each machine..
>>
>> FILE2K3:
>>
>> Windows IP Configuration
>>
>> Host Name . . . . . . . . . . . . : file2k3
>> Primary Dns Suffix . . . . . . . : pastongroup.com
>> Node Type . . . . . . . . . . . . : Broadcast
>> IP Routing Enabled. . . . . . . . : Yes
>> WINS Proxy Enabled. . . . . . . . : Yes
>> DNS Suffix Search List. . . . . . : pastongroup.com
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . : pastongroup.com
>> Description . . . . . . . . . . . : 3Com Gigabit NIC
>> Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.3
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DNS Servers . . . . . . . . . . . : 192.168.1.3
>>
>> MAIL2K3:
>>
>>
>>
>> Windows IP Configuration
>>
>>
>>
>> Host Name . . . . . . . . . . . . : mail2k3
>> Primary Dns Suffix . . . . . . . : pastongroup.com
>> Node Type . . . . . . . . . . . . : Unknown
>> IP Routing Enabled. . . . . . . . : Yes
>> WINS Proxy Enabled. . . . . . . . : Yes
>> DNS Suffix Search List. . . . . . : pastongroup.com
>>
>>
>>
>> PPP adapter RAS Server (Dial In) Interface:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.114
>> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>> Default Gateway . . . . . . . . . :
>>
>> Ethernet adapter Local Area Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : 3Com Gigabit NIC
>> Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
>> DHCP Enabled. . . . . . . . . . . : No
>> IP Address. . . . . . . . . . . . : 192.168.1.30
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.1.1
>> DNS Servers . . . . . . . . . . . : 192.168.1.3
>>
>> ***
>>
>> Here is the ping from Mail2k3 to File2k3:
>>
>> Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Request timed out.
>> Ping statistics for 192.168.1.3:
>>
>> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>>
>> And here is From FILE2k3 to MAIL2k3:
>>
>> Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:
>>
>> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>>
>> Ping statistics for 192.168.1.30:
>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> Approximate round trip times in milli-seconds:
>> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>>
>> ***
>>
>> Now here is what I notice when I do a NETSTAT -A on mail2k3... there are
>> a
>> ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
>> getting thru and the LDAP etc is failing...
>>
>> FROM MAIL2K3 (Netstat -a) spit to a txt file.
>>
>> Active Connections
>>
>> Proto Local Address Foreign Address State
>> TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3ptp mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:http ten11.bwc.na.blackberry.net:34159
>> TIME_WAIT
>> TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
>> TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
>> TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
>> TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
>> TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
>> TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
>> TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
>> TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
>> TCP mail2k3:691 mail2k3.pastongroup.com:48987
>> ESTABLISHED
>> TCP mail2k3:691 mail2k3.pastongroup.com:48997
>> ESTABLISHED
>> TCP mail2k3:691 mail2k3.pastongroup.com:49052
>> ESTABLISHED
>> TCP mail2k3:691 mail2k3.pastongroup.com:49055
>> ESTABLISHED
>> TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3ptp ool-457251fd.dyn.optonline.net:1151
>> ESTABLISHED
>> TCP mail2k3ptp ool-457b9bc5.dyn.optonline.net:2912
>> ESTABLISHED
>> TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
>> TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:3916 file2k3.pastongroup.com:3268 ESTABLISHED
>> TCP mail2k3:3918 file2k3.pastongroup.com:3268 ESTABLISHED
>> TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3929 file2k3.pastongroup.com:3268 ESTABLISHED
>> TCP mail2k3:3930 file2k3.pastongroup.com:3268 ESTABLISHED
>> TCP mail2k3:3935 file2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3936 file2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3937 file2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3938 file2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3939 file2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3940 file2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3942 file2k3.pastongroup.com:3268 ESTABLISHED
>> TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:4459 file2k3.pastongroup.com:3268 ESTABLISHED
>> TCP mail2k3:4908 file2k3.pastongroup.com:3268 ESTABLISHED
>> TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5325 file2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5771 file2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
>> TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
>> ESTABLISHED
>> TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn
>> TIME_WAIT
>> TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
>> TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
>> ESTABLISHED
>> TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
>> TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
>> ESTABLISHED
>> TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
>> ESTABLISHED
>> TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
>> TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
>> TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
>> TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
>> TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
>> TCP mail2k3:5934 file2k3.pastongroup.com:domain TIME_WAIT
>> TCP mail2k3:5935 file2k3.pastongroup.com:domain TIME_WAIT
>> TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
>> ESTABLISHED
>> TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
>> TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
>> ESTABLISHED
>> TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
>> TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
>> TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
>> TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
>> TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
>> TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
>> TCP mail2k3:48998 EXT285:2018 ESTABLISHED
>> TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
>> TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
>> TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED
>> TCP mail2k3:48998 ext240.pastongroup.com:1275 ESTABLISHED
>> TCP mail2k3:48998 ext292.pastongroup.com:3766 ESTABLISHED
>> TCP mail2k3:48998 ext227.pastongroup.com:3811 ESTABLISHED
>> TCP mail2k3:48998 ext275.pastongroup.com:1119 ESTABLISHED
>> TCP mail2k3:48998 ext297.pastongroup.com:2418 ESTABLISHED
>> TCP mail2k3:48998 ext200.pastongroup.com:1251 ESTABLISHED
>> TCP mail2k3:48998 ext209.pastongroup.com:1096 ESTABLISHED
>> TCP mail2k3:48998 ext299.pastongroup.com:1653 ESTABLISHED
>> TCP mail2k3:48998 ext206.pastongroup.com:3831 ESTABLISHED
>> TCP mail2k3:48998 ext273.pastongroup.com:3103 ESTABLISHED
>> TCP mail2k3:48998 ext236.pastongroup.com:1127 ESTABLISHED
>> TCP mail2k3:48998 ext211.pastongroup.com:1266 ESTABLISHED
>> TCP mail2k3:48998 ext269.pastongroup.com:1154 ESTABLISHED
>> TCP mail2k3:48998 ext217.pastongroup.com:3694 ESTABLISHED
>> TCP mail2k3:48998 ext233.pastongroup.com:2778 ESTABLISHED
>> TCP mail2k3:48998 ext293.pastongroup.com:2177 ESTABLISHED
>> TCP mail2k3:48998 ext276.pastongroup.com:1755 ESTABLISHED
>> TCP mail2k3:48998 192.168.1.105:1629 ESTABLISHED
>> TCP mail2k3:48998 ext269.pastongroup.com:3829 ESTABLISHED
>> TCP mail2k3:48998 ext282.pastongroup.com:2949 ESTABLISHED
>> TCP mail2k3:48998 ext282.pastongroup.com:2952 ESTABLISHED
>> TCP mail2k3:48998 ira.pastongroup.com:1638 ESTABLISHED
>> TCP mail2k3:48998 EXT272:1103 ESTABLISHED
>> TCP mail2k3:48998 ext279.pastongroup.com:4178 ESTABLISHED
>> TCP mail2k3:48998 ext277.pastongroup.com:4431 ESTABLISHED
>> TCP mail2k3:48998 ext248.pastongroup.com:1114 ESTABLISHED
>> TCP mail2k3:48998 ext234.pastongroup.com:4836 ESTABLISHED
>> TCP mail2k3:48998 ext288.pastongroup.com:2854 ESTABLISHED
>> TCP mail2k3:48998 scottxp.pastongroup.com:3144 ESTABLISHED
>> TCP mail2k3:49052 mail2k3.pastongroup.com:691 ESTABLISHED
>> TCP mail2k3:49055 mail2k3.pastongroup.com:691 ESTABLISHED
>> TCP mail2k3:50087 file2k3.pastongroup.com:1025 ESTABLISHED
>> TCP mail2k3:50094 file2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:50095 file2k3.pastongroup.com:ldap CLOSE_WAIT
>> TCP mail2k3:50098 file2k3.pastongroup.com:3268 CLOSE_WAIT
>> TCP mail2k3:50099 file2k3.pastongroup.com:3268 CLOSE_WAIT
>> TCP mail2k3:53777 file2k3.pastongroup.com:1025 ESTABLISHED
>> TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
>> UDP mail2k3:epmap *:*
>> UDP mail2k3:microsoft-ds *:*
>> UDP mail2k3:isakmp *:*
>> UDP mail2k3:1025 *:*
>> UDP mail2k3:1026 *:*
>> UDP mail2k3:1027 *:*
>> UDP mail2k3:1028 *:*
>> UDP mail2k3:1030 *:*
>> UDP mail2k3:1032 *:*
>> UDP mail2k3:1034 *:*
>> UDP mail2k3:1035 *:*
>> UDP mail2k3hone *:*
>> UDP mail2k3:1184 *:*
>> UDP mail2k3:1241 *:*
>> UDP mail2k3:1242 *:*
>> UDP mail2k3:l2tp *:*
>> UDP mail2k3:3456 *:*



 
Reply With Quote
 
Miha Pihler [MVP]
Guest
Posts: n/a

 
      05-01-2006, 03:50 PM
If I understand you correctly -- Mail2K3 server does not have anything in
the arp cache?

--
Mike
Microsoft MVP - Windows Security

"Chris Baldassano" <(E-Mail Removed)> wrote in
message news:A7B3CEAC-8194-4E4A-AB91-(E-Mail Removed)...
>I dont know why IP routing is on.. I did not setup these servers, an
> outsource company did.. Should I turn that off? We have a simple network
> here with no need for specific routes.. We have 1 gateway for our internet
> and 3 servers, 50 workstations. No remote offices etc...
>
> Here is the command from both machines:
>
>
> FILE2K3
>
> Interface: 192.168.1.30 --- 0x10003
> Internet Address Physical Address Type
> 192.168.1.1 00-0f-b5-8c-85-7b dynamic
> 192.168.1.3 00-0a-5e-1a-01-41 dynamic
> 192.168.1.7 00-0a-5e-1a-02-f1 dynamic
> 192.168.1.8 00-14-22-0a-19-9a dynamic
> 192.168.1.31 00-0a-5e-1a-b9-9b dynamic
> 192.168.1.43 00-0c-f1-92-cd-46 dynamic
> 192.168.1.44 00-0c-f1-92-c6-90 dynamic
> 192.168.1.46 00-0c-f1-92-cc-f0 dynamic
> 192.168.1.48 00-0c-f1-92-cd-5d dynamic
> 192.168.1.49 00-0c-f1-92-51-50 dynamic
> 192.168.1.53 00-0c-f1-92-f7-c8 dynamic
> 192.168.1.55 00-0c-f1-92-de-fe dynamic
> 192.168.1.58 00-0c-f1-92-f8-1c dynamic
> 192.168.1.60 00-0c-f1-92-cd-76 dynamic
> 192.168.1.63 00-0c-f1-92-df-dd dynamic
> 192.168.1.64 00-0c-f1-92-f7-ff dynamic
> 192.168.1.65 00-0c-f1-92-df-30 dynamic
> 192.168.1.66 00-0c-f1-92-f6-e7 dynamic
> 192.168.1.67 00-0c-f1-92-c3-07 dynamic
> 192.168.1.68 00-0c-f1-92-f7-88 dynamic
> 192.168.1.69 00-0c-f1-92-df-14 dynamic
> 192.168.1.70 00-0c-f1-92-c7-c3 dynamic
> 192.168.1.71 00-0c-f1-92-cb-d6 dynamic
> 192.168.1.72 00-0c-f1-92-cc-fb dynamic
> 192.168.1.73 00-0c-f1-92-de-1c dynamic
> 192.168.1.74 00-0c-f1-92-f8-65 dynamic
> 192.168.1.104 00-10-83-59-d0-f6 dynamic
> 192.168.1.107 00-60-b0-41-f6-1a dynamic
> 192.168.1.109 00-01-e6-3b-b4-0b dynamic
> 192.168.1.125 00-0c-f1-92-ef-0c dynamic
> 192.168.1.127 00-0c-f1-92-f7-bd dynamic
> 192.168.1.130 00-0c-f1-92-df-42 dynamic
> 192.168.1.131 00-0c-f1-92-cc-ae dynamic
> 192.168.1.146 00-0c-f1-92-f3-a9 dynamic
> 192.168.1.155 08-00-09-bd-f6-54 dynamic
> 192.168.1.156 00-0c-f1-92-c6-9a dynamic
> 192.168.1.159 00-0c-f1-92-de-65 dynamic
> 192.168.1.191 00-08-0d-90-3c-2a dynamic
> 192.168.1.200 08-00-09-bd-16-43 dynamic
> 192.168.1.202 00-01-e6-7e-c3-6b dynamic
> 192.168.1.223 00-0c-f1-92-f8-26 dynamic
> 192.168.1.227 00-0c-f1-92-51-93 dynamic
> 192.168.1.252 00-11-85-fb-26-7b dynamic
>
>
> Interface: 192.168.1.3 --- 0x10003
> Internet Address Physical Address Type
> 192.168.1.1 00-0f-b5-8c-85-7b dynamic
> 192.168.1.7 00-0a-5e-1a-02-f1 dynamic
> 192.168.1.8 00-14-22-0a-19-9a dynamic
> 192.168.1.30 00-0a-5e-1a-02-c3 dynamic
> 192.168.1.31 00-0a-5e-1a-b9-9b dynamic
> 192.168.1.40 00-0c-f1-92-e5-de dynamic
> 192.168.1.42 00-0c-f1-92-46-d1 dynamic
> 192.168.1.43 00-0c-f1-92-cd-46 dynamic
> 192.168.1.44 00-0c-f1-92-c6-90 dynamic
> 192.168.1.45 00-0c-f1-92-e5-a4 dynamic
> 192.168.1.46 00-0c-f1-92-cc-f0 dynamic
> 192.168.1.48 00-0c-f1-92-cd-5d dynamic
> 192.168.1.49 00-0c-f1-92-51-50 dynamic
> 192.168.1.53 00-0c-f1-92-f7-c8 dynamic
> 192.168.1.55 00-0c-f1-92-de-fe dynamic
> 192.168.1.56 00-0c-f1-92-cd-3b dynamic
> 192.168.1.58 00-0c-f1-92-f8-1c dynamic
> 192.168.1.59 00-0c-f1-92-dc-ae dynamic
> 192.168.1.63 00-0c-f1-92-df-dd dynamic
> 192.168.1.64 00-0c-f1-92-f7-ff dynamic
> 192.168.1.65 00-0c-f1-92-df-30 dynamic
> 192.168.1.66 00-0c-f1-92-f6-e7 dynamic
> 192.168.1.67 00-0c-f1-92-c3-07 dynamic
> 192.168.1.68 00-0c-f1-92-f7-88 dynamic
> 192.168.1.69 00-0c-f1-92-df-14 dynamic
> 192.168.1.70 00-0c-f1-92-c7-c3 dynamic
> 192.168.1.71 00-0c-f1-92-cb-d6 dynamic
> 192.168.1.72 00-0c-f1-92-cc-fb dynamic
> 192.168.1.73 00-0c-f1-92-de-1c dynamic
> 192.168.1.74 00-0c-f1-92-f8-65 dynamic
> 192.168.1.88 00-0c-f1-92-f7-ea dynamic
> 192.168.1.114 00-0a-5e-1a-02-c3 dynamic
> 192.168.1.125 00-0c-f1-92-ef-0c dynamic
> 192.168.1.127 00-0c-f1-92-f7-bd dynamic
> 192.168.1.130 00-0c-f1-92-df-42 dynamic
> 192.168.1.131 00-0c-f1-92-cc-ae dynamic
> 192.168.1.146 00-0c-f1-92-f3-a9 dynamic
> 192.168.1.156 00-0c-f1-92-c6-9a dynamic
> 192.168.1.159 00-0c-f1-92-de-65 dynamic
> 192.168.1.164 00-0c-f1-92-f8-6d dynamic
> 192.168.1.223 00-0c-f1-92-f8-26 dynamic
>
>
> MAIL2K3:
>
>
>
> --
> Network Administrator
> Simon Paston & Sons Agency
>
>
> "Miha Pihler [MVP]" wrote:
>
>> Why do you have IP Routing enabled on both your servers? This is not the
>> default nor usual setting.
>>
>> After you try and ping the server and it fails -- can you run the
>> following
>> command
>>
>> arp -a
>>
>> What is the output of the arp command?
>>
>> --
>> Mike
>> Microsoft MVP - Windows Security
>>
>>
>> "Chris Baldassano" <(E-Mail Removed)> wrote in
>> message news:FF4AACD6-E0DD-4017-9CE3-(E-Mail Removed)...
>> >I can not ping by IP, Or by Name from mail2k3 to File2k3... But the
>> >other
>> >way
>> > around it works perfectally fine (ip or name)...
>> >
>> > Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
>> > secondary one is just not connected... I am gonna hook them up today to
>> > see
>> > if it is a NIC issue.. (I doubt it, there would be other factors)...
>> >
>> > Little more background:
>> >
>> > -File2k3 is our DNS server with the proper ISP DNS's forwarded...
>> > -File2k3 is our Global Catalog, and Domain Controller
>> >
>> > -Mail2k3 WAS a domain controller, that was taken down by 2 microsoft
>> > tech's
>> > about 5 days ago on a $245 Support Call.. They did all the proper steps
>> > to
>> > make it Just an exchange server and not anything else.
>> >
>> >
>> >
>> > Here is the IP config for each machine..
>> >
>> > FILE2K3:
>> >
>> > Windows IP Configuration
>> >
>> > Host Name . . . . . . . . . . . . : file2k3
>> > Primary Dns Suffix . . . . . . . : pastongroup.com
>> > Node Type . . . . . . . . . . . . : Broadcast
>> > IP Routing Enabled. . . . . . . . : Yes
>> > WINS Proxy Enabled. . . . . . . . : Yes
>> > DNS Suffix Search List. . . . . . : pastongroup.com
>> >
>> > Ethernet adapter Local Area Connection:
>> >
>> > Connection-specific DNS Suffix . : pastongroup.com
>> > Description . . . . . . . . . . . : 3Com Gigabit NIC
>> > Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
>> > DHCP Enabled. . . . . . . . . . . : No
>> > IP Address. . . . . . . . . . . . : 192.168.1.3
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Default Gateway . . . . . . . . . : 192.168.1.1
>> > DNS Servers . . . . . . . . . . . : 192.168.1.3
>> >
>> > MAIL2K3:
>> >
>> >
>> >
>> > Windows IP Configuration
>> >
>> >
>> >
>> > Host Name . . . . . . . . . . . . : mail2k3
>> > Primary Dns Suffix . . . . . . . : pastongroup.com
>> > Node Type . . . . . . . . . . . . : Unknown
>> > IP Routing Enabled. . . . . . . . : Yes
>> > WINS Proxy Enabled. . . . . . . . : Yes
>> > DNS Suffix Search List. . . . . . : pastongroup.com
>> >
>> >
>> >
>> > PPP adapter RAS Server (Dial In) Interface:
>> >
>> > Connection-specific DNS Suffix . :
>> > Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>> > Physical Address. . . . . . . . . : 00-53-45-00-00-00
>> > DHCP Enabled. . . . . . . . . . . : No
>> > IP Address. . . . . . . . . . . . : 192.168.1.114
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.255
>> > Default Gateway . . . . . . . . . :
>> >
>> > Ethernet adapter Local Area Connection:
>> >
>> > Connection-specific DNS Suffix . :
>> > Description . . . . . . . . . . . : 3Com Gigabit NIC
>> > Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
>> > DHCP Enabled. . . . . . . . . . . : No
>> > IP Address. . . . . . . . . . . . : 192.168.1.30
>> > Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> > Default Gateway . . . . . . . . . : 192.168.1.1
>> > DNS Servers . . . . . . . . . . . : 192.168.1.3
>> >
>> > ***
>> >
>> > Here is the ping from Mail2k3 to File2k3:
>> >
>> > Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
>> > Request timed out.
>> > Request timed out.
>> > Request timed out.
>> > Request timed out.
>> > Ping statistics for 192.168.1.3:
>> >
>> > Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>> >
>> > And here is From FILE2k3 to MAIL2k3:
>> >
>> > Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:
>> >
>> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>> > Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
>> >
>> > Ping statistics for 192.168.1.30:
>> > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> > Approximate round trip times in milli-seconds:
>> > Minimum = 0ms, Maximum = 0ms, Average = 0ms
>> >
>> > ***
>> >
>> > Now here is what I notice when I do a NETSTAT -A on mail2k3... there
>> > are a
>> > ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
>> > getting thru and the LDAP etc is failing...
>> >
>> > FROM MAIL2K3 (Netstat -a) spit to a txt file.
>> >
>> > Active Connections
>> >
>> > Proto Local Address Foreign Address State
>> > TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3ptp mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:http ten11.bwc.na.blackberry.net:34159
>> > TIME_WAIT
>> > TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
>> > TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
>> > TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
>> > TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
>> > TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
>> > TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
>> > TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
>> > TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
>> > TCP mail2k3:691 mail2k3.pastongroup.com:48987
>> > ESTABLISHED
>> > TCP mail2k3:691 mail2k3.pastongroup.com:48997
>> > ESTABLISHED
>> > TCP mail2k3:691 mail2k3.pastongroup.com:49052
>> > ESTABLISHED
>> > TCP mail2k3:691 mail2k3.pastongroup.com:49055
>> > ESTABLISHED
>> > TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3ptp ool-457251fd.dyn.optonline.net:1151
>> > ESTABLISHED
>> > TCP mail2k3ptp ool-457b9bc5.dyn.optonline.net:2912
>> > ESTABLISHED
>> > TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
>> > TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:3916 file2k3.pastongroup.com:3268
>> > ESTABLISHED
>> > TCP mail2k3:3918 file2k3.pastongroup.com:3268
>> > ESTABLISHED
>> > TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3929 file2k3.pastongroup.com:3268
>> > ESTABLISHED
>> > TCP mail2k3:3930 file2k3.pastongroup.com:3268
>> > ESTABLISHED
>> > TCP mail2k3:3935 file2k3.pastongroup.com:ldap
>> > ESTABLISHED
>> > TCP mail2k3:3936 file2k3.pastongroup.com:ldap
>> > ESTABLISHED
>> > TCP mail2k3:3937 file2k3.pastongroup.com:ldap
>> > ESTABLISHED
>> > TCP mail2k3:3938 file2k3.pastongroup.com:ldap
>> > ESTABLISHED
>> > TCP mail2k3:3939 file2k3.pastongroup.com:ldap
>> > ESTABLISHED
>> > TCP mail2k3:3940 file2k3.pastongroup.com:ldap
>> > ESTABLISHED
>> > TCP mail2k3:3942 file2k3.pastongroup.com:3268
>> > ESTABLISHED
>> > TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:4459 file2k3.pastongroup.com:3268
>> > ESTABLISHED
>> > TCP mail2k3:4908 file2k3.pastongroup.com:3268
>> > ESTABLISHED
>> > TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:5325 file2k3.pastongroup.com:ldap
>> > ESTABLISHED
>> > TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
>> > TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:5771 file2k3.pastongroup.com:ldap
>> > ESTABLISHED
>> > TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
>> > TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
>> > ESTABLISHED
>> > TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn
>> > TIME_WAIT
>> > TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
>> > TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
>> > ESTABLISHED
>> > TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
>> > TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
>> > ESTABLISHED
>> > TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
>> > ESTABLISHED
>> > TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
>> > TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
>> > TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
>> > TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
>> > TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
>> > TCP mail2k3:5934 file2k3.pastongroup.com:domain
>> > TIME_WAIT
>> > TCP mail2k3:5935 file2k3.pastongroup.com:domain
>> > TIME_WAIT
>> > TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
>> > ESTABLISHED
>> > TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
>> > TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
>> > ESTABLISHED
>> > TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
>> > TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
>> > TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
>> > TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
>> > TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
>> > TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
>> > TCP mail2k3:48998 EXT285:2018 ESTABLISHED
>> > TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
>> > TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
>> > TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED
>> > TCP mail2k3:48998 ext240.pastongroup.com:1275 ESTABLISHED
>> > TCP mail2k3:48998 ext292.pastongroup.com:3766 ESTABLISHED
>> > TCP mail2k3:48998 ext227.pastongroup.com:3811 ESTABLISHED
>> > TCP mail2k3:48998 ext275.pastongroup.com:1119 ESTABLISHED
>> > TCP mail2k3:48998 ext297.pastongroup.com:2418 ESTABLISHED
>> > TCP mail2k3:48998 ext200.pastongroup.com:1251 ESTABLISHED
>> > TCP mail2k3:48998 ext209.pastongroup.com:1096 ESTABLISHED
>> > TCP mail2k3:48998 ext299.pastongroup.com:1653 ESTABLISHED
>> > TCP mail2k3:48998 ext206.pastongroup.com:3831 ESTABLISHED
>> > TCP mail2k3:48998 ext273.pastongroup.com:3103 ESTABLISHED
>> > TCP mail2k3:48998 ext236.pastongroup.com:1127 ESTABLISHED
>> > TCP mail2k3:48998 ext211.pastongroup.com:1266 ESTABLISHED
>> > TCP mail2k3:48998 ext269.pastongroup.com:1154 ESTABLISHED
>> > TCP mail2k3:48998 ext217.pastongroup.com:3694 ESTABLISHED
>> > TCP mail2k3:48998 ext233.pastongroup.com:2778 ESTABLISHED
>> > TCP mail2k3:48998 ext293.pastongroup.com:2177 ESTABLISHED
>> > TCP mail2k3:48998 ext276.pastongroup.com:1755 ESTABLISHED
>> > TCP mail2k3:48998 192.168.1.105:1629 ESTABLISHED
>> > TCP mail2k3:48998 ext269.pastongroup.com:3829 ESTABLISHED
>> > TCP mail2k3:48998 ext282.pastongroup.com:2949 ESTABLISHED
>> > TCP mail2k3:48998 ext282.pastongroup.com:2952 ESTABLISHED
>> > TCP mail2k3:48998 ira.pastongroup.com:1638 ESTABLISHED
>> > TCP mail2k3:48998 EXT272:1103 ESTABLISHED
>> > TCP mail2k3:48998 ext279.pastongroup.com:4178 ESTABLISHED
>> > TCP mail2k3:48998 ext277.pastongroup.com:4431 ESTABLISHED
>> > TCP mail2k3:48998 ext248.pastongroup.com:1114 ESTABLISHED
>> > TCP mail2k3:48998 ext234.pastongroup.com:4836 ESTABLISHED
>> > TCP mail2k3:48998 ext288.pastongroup.com:2854 ESTABLISHED
>> > TCP mail2k3:48998 scottxp.pastongroup.com:3144
>> > ESTABLISHED
>> > TCP mail2k3:49052 mail2k3.pastongroup.com:691 ESTABLISHED
>> > TCP mail2k3:49055 mail2k3.pastongroup.com:691 ESTABLISHED
>> > TCP mail2k3:50087 file2k3.pastongroup.com:1025
>> > ESTABLISHED
>> > TCP mail2k3:50094 file2k3.pastongroup.com:ldap CLOSE_WAIT



 
Reply With Quote
 
Chris Baldassano
Guest
Posts: n/a

 
      05-01-2006, 03:55 PM
Well the secondary NIC's have anways been disabled... I just enabled them for
this test.. Originally i believe they were putin there for redundancy just
incase...

Should i delete the IP routing? Will that have adverse affects? I have
full backups just incase. There should be no set routes for anything on my
network.. It should flow free so to speak.
--
Network Administrator
Simon Paston & Sons Agency


"Miha Pihler [MVP]" wrote:

> Hi,
>
> In general Active Directory server should not be multihomed (multiple
> NIC) -- (not a recommended configuration). There are quite a few problems
> when domain controller is multihomed... Here are few of them...
>
> Troubleshooting browser Event ID 8021 and 8032 on master browsers
> http://support.microsoft.com/?id=135404
>
> Clients cannot log on to domain controllers that are Windows Server
> 2003-based DNS servers, and network interfaces that are not registered in
> DNS can still perform dynamic updates
> http://support.microsoft.com/default...b;en-us;832478
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Chris Baldassano" <(E-Mail Removed)> wrote in
> message news:8DDD4FFB-509F-4A55-AB32-(E-Mail Removed)...
> > An Additional note:
> >
> > I enabled the secondary NIC's (File2k3 @ 192.168.1.20, MAIL2k3 @
> > 192.168.1.21) and Added the DNS Record in the DNS Lookup Zones...
> >
> > Mail can now ping File Perfectly to 192.168.1.20, but it still times out
> > on
> > 192.168.1.3...
> >
> > This is not acceptable because the /20 address is also going thru a 100
> > meg
> > switch and not the gigabit router.. just an FYI.
> >
> > I did a ipconfig /flushdns on the mail2k3 server so it would see the DNS
> > change.
> >
> > This is VERY Strange.
> > --
> > Network Administrator
> > Simon Paston & Sons Agency
> >
> >
> > "Chris Baldassano" wrote:
> >
> >> I can not ping by IP, Or by Name from mail2k3 to File2k3... But the other
> >> way
> >> around it works perfectally fine (ip or name)...
> >>
> >> Now both machines have Dual Gigabit NIC's (Onboard and a 3com) and the
> >> secondary one is just not connected... I am gonna hook them up today to
> >> see
> >> if it is a NIC issue.. (I doubt it, there would be other factors)...
> >>
> >> Little more background:
> >>
> >> -File2k3 is our DNS server with the proper ISP DNS's forwarded...
> >> -File2k3 is our Global Catalog, and Domain Controller
> >>
> >> -Mail2k3 WAS a domain controller, that was taken down by 2 microsoft
> >> tech's
> >> about 5 days ago on a $245 Support Call.. They did all the proper steps
> >> to
> >> make it Just an exchange server and not anything else.
> >>
> >>
> >>
> >> Here is the IP config for each machine..
> >>
> >> FILE2K3:
> >>
> >> Windows IP Configuration
> >>
> >> Host Name . . . . . . . . . . . . : file2k3
> >> Primary Dns Suffix . . . . . . . : pastongroup.com
> >> Node Type . . . . . . . . . . . . : Broadcast
> >> IP Routing Enabled. . . . . . . . : Yes
> >> WINS Proxy Enabled. . . . . . . . : Yes
> >> DNS Suffix Search List. . . . . . : pastongroup.com
> >>
> >> Ethernet adapter Local Area Connection:
> >>
> >> Connection-specific DNS Suffix . : pastongroup.com
> >> Description . . . . . . . . . . . : 3Com Gigabit NIC
> >> Physical Address. . . . . . . . . : 00-0A-5E-1A-01-41
> >> DHCP Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 192.168.1.3
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> Default Gateway . . . . . . . . . : 192.168.1.1
> >> DNS Servers . . . . . . . . . . . : 192.168.1.3
> >>
> >> MAIL2K3:
> >>
> >>
> >>
> >> Windows IP Configuration
> >>
> >>
> >>
> >> Host Name . . . . . . . . . . . . : mail2k3
> >> Primary Dns Suffix . . . . . . . : pastongroup.com
> >> Node Type . . . . . . . . . . . . : Unknown
> >> IP Routing Enabled. . . . . . . . : Yes
> >> WINS Proxy Enabled. . . . . . . . : Yes
> >> DNS Suffix Search List. . . . . . : pastongroup.com
> >>
> >>
> >>
> >> PPP adapter RAS Server (Dial In) Interface:
> >>
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
> >> Physical Address. . . . . . . . . : 00-53-45-00-00-00
> >> DHCP Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 192.168.1.114
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.255
> >> Default Gateway . . . . . . . . . :
> >>
> >> Ethernet adapter Local Area Connection:
> >>
> >> Connection-specific DNS Suffix . :
> >> Description . . . . . . . . . . . : 3Com Gigabit NIC
> >> Physical Address. . . . . . . . . : 00-0A-5E-1A-02-C3
> >> DHCP Enabled. . . . . . . . . . . : No
> >> IP Address. . . . . . . . . . . . : 192.168.1.30
> >> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> >> Default Gateway . . . . . . . . . : 192.168.1.1
> >> DNS Servers . . . . . . . . . . . : 192.168.1.3
> >>
> >> ***
> >>
> >> Here is the ping from Mail2k3 to File2k3:
> >>
> >> Pinging file2k3.pastongroup.com [192.168.1.3] with 32 bytes of data:
> >> Request timed out.
> >> Request timed out.
> >> Request timed out.
> >> Request timed out.
> >> Ping statistics for 192.168.1.3:
> >>
> >> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
> >>
> >> And here is From FILE2k3 to MAIL2k3:
> >>
> >> Pinging mail2k3.pastongroup.com [192.168.1.30] with 32 bytes of data:
> >>
> >> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> >> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> >> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> >> Reply from 192.168.1.30: bytes=32 time<1ms TTL=128
> >>
> >> Ping statistics for 192.168.1.30:
> >> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> >> Approximate round trip times in milli-seconds:
> >> Minimum = 0ms, Maximum = 0ms, Average = 0ms
> >>
> >> ***
> >>
> >> Now here is what I notice when I do a NETSTAT -A on mail2k3... there are
> >> a
> >> ton of ports in a CLOSE_WAIT state, which has to be why the pings arent
> >> getting thru and the LDAP etc is failing...
> >>
> >> FROM MAIL2K3 (Netstat -a) spit to a txt file.
> >>
> >> Active Connections
> >>
> >> Proto Local Address Foreign Address State
> >> TCP mail2k3:smtp mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:http mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:epmap mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:https mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:microsoft-ds mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:593 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:691 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:1029 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:1033 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:1037 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:1149 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:1160 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:1166 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3ptp mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:3389 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:6001 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:6002 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:6004 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:7930 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:12174 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:34571 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:34572 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:34573 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:38292 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:48974 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:48975 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:48976 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:48977 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:48981 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:48998 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:1031 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:1179 mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:http ten11.bwc.na.blackberry.net:34159
> >> TIME_WAIT
> >> TCP mail2k3:netbios-ssn mail2k3.pastongroup.com:0 LISTENING
> >> TCP mail2k3:netbios-ssn ext211.pastongroup.com:1667 ESTABLISHED
> >> TCP mail2k3:microsoft-ds ext286.pastongroup.com:2879 ESTABLISHED
> >> TCP mail2k3:microsoft-ds ext263.pastongroup.com:1702 ESTABLISHED
> >> TCP mail2k3:microsoft-ds ext290.pastongroup.com:1115 ESTABLISHED
> >> TCP mail2k3:microsoft-ds ext292.pastongroup.com:2457 ESTABLISHED
> >> TCP mail2k3:microsoft-ds ext206.pastongroup.com:3725 ESTABLISHED
> >> TCP mail2k3:microsoft-ds ext273.pastongroup.com:4323 ESTABLISHED
> >> TCP mail2k3:691 mail2k3.pastongroup.com:48987
> >> ESTABLISHED
> >> TCP mail2k3:691 mail2k3.pastongroup.com:48997
> >> ESTABLISHED
> >> TCP mail2k3:691 mail2k3.pastongroup.com:49052
> >> ESTABLISHED
> >> TCP mail2k3:691 mail2k3.pastongroup.com:49055
> >> ESTABLISHED
> >> TCP mail2k3:1079 web2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:1080 web2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:kpop file2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:1150 web2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:1288 file2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3ptp ool-457251fd.dyn.optonline.net:1151
> >> ESTABLISHED
> >> TCP mail2k3ptp ool-457b9bc5.dyn.optonline.net:2912
> >> ESTABLISHED
> >> TCP mail2k3:1788 web2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:2638 web2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:2740 file2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:3389 ext288.pastongroup.com:3032 ESTABLISHED
> >> TCP mail2k3:3908 web2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:3916 file2k3.pastongroup.com:3268 ESTABLISHED
> >> TCP mail2k3:3918 file2k3.pastongroup.com:3268 ESTABLISHED
> >> TCP mail2k3:3919 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3920 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3921 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3922 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3923 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3924 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3925 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3926 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3927 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3929 file2k3.pastongroup.com:3268 ESTABLISHED
> >> TCP mail2k3:3930 file2k3.pastongroup.com:3268 ESTABLISHED
> >> TCP mail2k3:3935 file2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3936 file2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3937 file2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3938 file2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3939 file2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3940 file2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3942 file2k3.pastongroup.com:3268 ESTABLISHED
> >> TCP mail2k3:3946 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3991 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:3998 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:4459 file2k3.pastongroup.com:3268 ESTABLISHED
> >> TCP mail2k3:4908 file2k3.pastongroup.com:3268 ESTABLISHED
> >> TCP mail2k3:5217 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5325 file2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5377 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5426 file2k3.pastongroup.com:ldap CLOSE_WAIT
> >> TCP mail2k3:5515 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5535 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5741 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5769 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5771 file2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5778 web2k3.pastongroup.com:ldap ESTABLISHED
> >> TCP mail2k3:5800 file2k3.pastongroup.com:netbios-ssn
> >> ESTABLISHED
> >> TCP mail2k3:5888 ext240.pastongroup.com:netbios-ssn
> >> TIME_WAIT
> >> TCP mail2k3:5901 file2k3.pastongroup.com:epmap TIME_WAIT
> >> TCP mail2k3:5908 ext286.pastongroup.com:microsoft-ds
> >> ESTABLISHED
> >> TCP mail2k3:5915 192.168.1.200:9100 TIME_WAIT
> >> TCP mail2k3:5917 ext292.pastongroup.com:microsoft-ds
> >> ESTABLISHED
> >> TCP mail2k3:5923 ext263.pastongroup.com:microsoft-ds
> >> ESTABLISHED
> >> TCP mail2k3:5928 file2k3.pastongroup.com:epmap TIME_WAIT
> >> TCP mail2k3:5930 web2k3.pastongroup.com:ldap TIME_WAIT
> >> TCP mail2k3:5931 file2k3.pastongroup.com:ldap TIME_WAIT
> >> TCP mail2k3:5932 file2k3.pastongroup.com:3268 TIME_WAIT
> >> TCP mail2k3:5933 web2k3.pastongroup.com:ldap TIME_WAIT
> >> TCP mail2k3:5934 file2k3.pastongroup.com:domain TIME_WAIT
> >> TCP mail2k3:5935 file2k3.pastongroup.com:domain TIME_WAIT
> >> TCP mail2k3:5937 file2k3.pastongroup.com:microsoft-ds
> >> ESTABLISHED
> >> TCP mail2k3:5940 web2k3.pastongroup.com:ldap TIME_WAIT
> >> TCP mail2k3:5941 web2k3.pastongroup.com:microsoft-ds
> >> ESTABLISHED
> >> TCP mail2k3:47666 file2k3.pastongroup.com:3268 CLOSE_WAIT
> >> TCP mail2k3:48987 mail2k3.pastongroup.com:691 ESTABLISHED
> >> TCP mail2k3:48997 mail2k3.pastongroup.com:691 ESTABLISHED
> >> TCP mail2k3:48998 ext286.pastongroup.com:2130 ESTABLISHED
> >> TCP mail2k3:48998 ext228.pastongroup.com:4869 ESTABLISHED
> >> TCP mail2k3:48998 ext263.pastongroup.com:1148 ESTABLISHED
> >> TCP mail2k3:48998 EXT285:2018 ESTABLISHED
> >> TCP mail2k3:48998 ext270.pastongroup.com:1190 ESTABLISHED
> >> TCP mail2k3:48998 ext256.pastongroup.com:2208 ESTABLISHED
> >> TCP mail2k3:48998 ext290.pastongroup.com:1141 ESTABLISHED

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Global Catalog Server Chris Windows Networking 0 11-02-2006 11:43 PM
Global catalog Mr.B Windows Networking 0 07-26-2005 12:16 PM
Global Catalog Sean Connery Windows Networking 2 02-03-2004 03:51 PM
WIN2K, Global Catalog and Exchange =?Utf-8?B?SmVycnk=?= Windows Networking 0 01-28-2004 10:31 PM
Global Catalog Server =?Utf-8?B?c25kMWs=?= Windows Networking 2 12-10-2003 03:19 PM



1 2 3 4 5 6 7 8 9 10 11