Networking with Windows 2003

[George Schneider]

I'm having a hard time figuring this one out. I have three Windows 20003
member servers in a location Main. We can get to the 2003 servers without a
problem from location Main. From an other site we canmot get to the Windows
2003 member servers. All sites have at least one Windows 2000 DC. We cannot
ping or browse to these servers from another site.
What in Windows would prevent form getting to these servers?

[Robert L [MS-MVP]]

assuming the server doesn't have firewall blocking the ping, does it have two NICs?

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com

"George Schneider" <georgeds...@news.postalias> wrote in message news:3992D677-938F-4255...@microsoft.com...

[George Schneider]

yes.

[Robert L [MS-MVP]]

Have you enable NAT? Posting the result of ipconfig /all or routing table here may help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com

"George Schneider" <georgeds...@news.postalias> wrote in message news:FDD4F6EB-7A7C-460F...@microsoft.com...

[Tom Che [MSFT]]

Hi George,

Thank you for posting here!

Could you ping or browse Windows 2000 DC in one site from another site? If
so, I think you may check the settings in Windows Firewall of Windows
Server 2003. The following KB article may be a good reference:

832017 Service overview and network port requirements for the Windows
Server system
http://support.microsoft.com/default.aspx?scid=kb;EN-US;832017

You may also try to access the shared folder on the Windows Server 2003 for
a test.

If you are unable to access the Windows 2000 DC between the sites, I think
you may consider Robert's suggestion, and check whether the IP settings or
route settings are collect. Please also let us know your network structure
for further assistance, and the detailed information will help us resolve
this issue as soon as possible.

Hope this helps.

Have a nice day!

Sincerely,
Tom Che
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>From: "Robert L [MS-MVP]" <nor...@hotmail.com>
>References: <3992D677-938F-4255...@microsoft.com>
<eGW8KHc...@TK2MSFTNGP15.phx.gbl>
<FDD4F6EB-7A7C-460F...@microsoft.com>
>Subject: Re: Networking with Windows 2003
>Date: Wed, 30 Nov 2005 12:05:48 -0600
>Lines: 117
>MIME-Version: 1.0
>Content-Type: multipart/alternative;
> boundary="----=_NextPart_000_0014_01C5F5A6.666DDF20"
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
>Message-ID: <erzGyid...@TK2MSFTNGP12.phx.gbl>
>Newsgroups: microsoft.public.win2000.networking
>NNTP-Posting-Host: 64.107.43.200
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.win2000.networking:87325
>X-Tomcat-NG: microsoft.public.win2000.networking

[George Schneider]

We can browse and ping DC controllers in the network without any issues. It
seems to be isolated just to a few servrs (the Windows 2003 serveres recently
implemented) where we cannot browse, connect to shares or ping from other
sites. Otherwise all connectivity is perfect between sites.

[Tom Che [MSFT]]

Hi George,

Thanks for your reply!

Since the issue only occurs with a few Windows Server 2003 machines, you
may check the following items:

1. In the DC of the other site, use the following command to get a correct
route:
tracert IPAdress (replace the IPAdress with the IP of the DC on the site
has the Windows Server 2003)

2. Still in above DC, use the following command to get a abnormal route:
tracert IPAdress (replace the IPAdress with the IP of the Windows Server
2003)

3. Compare above results, and find out the Time Out occurs on which node
and then check whether there is anything wrong on that node.

Hope this helps.

Have a nice day!

Sincerely,
Tom Che
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: Networking with Windows 2003
>thread-index: AcX2hGq/jT0OY8QhS86NncjY1CvOdA==
>X-WBNR-Posting-Host: 209.244.152.162
>From: "=?Utf-8?B?R2VvcmdlIFNjaG5laWRlcg==?="
<georgeds...@news.postalias>
>References: <3992D677-938F-4255...@microsoft.com>
<eGW8KHc...@TK2MSFTNGP15.phx.gbl>
<FDD4F6EB-7A7C-460F...@microsoft.com>
<erzGyid...@TK2MSFTNGP12.phx.gbl>
<x9bQJfm9...@TK2MSFTNGXA02.phx.gbl>

>Subject: Re: Networking with Windows 2003

>Date: Thu, 1 Dec 2005 06:35:03 -0800
>Lines: 103
>Message-ID: <90427BB9-F438-4963...@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.win2000.networking
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.win2000.networking:87348
>X-Tomcat-NG: microsoft.public.win2000.networking