Connectivity Problem

Dear Sirs,
I have configured my Windows 2003 Standered Server with
clients Windows 2000 Professional. I configured the IP
192.168.0.151 to Windows 2003 Server and I configured
client ip address in the range 192.168.0.1 to
192.168.0.15. It is worked fine under this situation.
After that we got a public ip for leased line and I added
that ip (203.187.255.121). And Primary Dns, Secondary Dns,
Default gateway. So that I can get my local network and
internet. But after that I can ping my server to the
clients, but clietns can't ping to my server, also clients
can ping each other. what will be problem? how can I
solve it? Please help me in this regard

Hi,

Do you have one or more NIC (network cards) in your Windows 2003 Server?
Most likely, you will need two in your server. One to connect your server to
the internet and another one to connect to LAN (192.168.0.x).

How is gateway configured on your clients (Windows 2000 Professional)? Will
your clients use Windows 2003 server to access the internet?

Mike

"Sabu" <(E-Mail Removed)> wrote in message
news:354501c4a474$3c19ec70$(E-Mail Removed)...
> Dear Sirs,
> I have configured my Windows 2003 Standered Server with
> clients Windows 2000 Professional. I configured the IP
> 192.168.0.151 to Windows 2003 Server and I configured
> client ip address in the range 192.168.0.1 to
> 192.168.0.15. It is worked fine under this situation.
> After that we got a public ip for leased line and I added
> that ip (203.187.255.121). And Primary Dns, Secondary Dns,
> Default gateway. So that I can get my local network and
> internet. But after that I can ping my server to the
> clients, but clietns can't ping to my server, also clients
> can ping each other. what will be problem? how can I
> solve it? Please help me in this regard

I know it will work under 2 network cards, but we can have
the option to create more ip's through tcp/ip properties.
So far I am in testing process, so I am not interested to
give permission to the client mechines connect to internet
through the windows 2003 server. But I have our internal
ip 192.168.0.x and I created one more ip that belongs to
the same network of my router so now I can ping to my
router and to my client mechines. But why the client
can't ping into my server? the server and client has same
ip range, also server can ping to clients. Also tell me
what is the important of gateway in client mechines for
our internal network. Do you have any idea regarding this?
>-----Original Message-----
>Hi,
>
>Do you have one or more NIC (network cards) in your
Windows 2003 Server?
>Most likely, you will need two in your server. One to
connect your server to
>the internet and another one to connect to LAN
(192.168.0.x).
>
>How is gateway configured on your clients (Windows 2000
Professional)? Will
>your clients use Windows 2003 server to access the
internet?
>
>Mike
>
>"Sabu" <(E-Mail Removed)> wrote in message
>news:354501c4a474$3c19ec70$(E-Mail Removed)...
>> Dear Sirs,
>> I have configured my Windows 2003 Standered Server with
>> clients Windows 2000 Professional. I configured the IP
>> 192.168.0.151 to Windows 2003 Server and I configured
>> client ip address in the range 192.168.0.1 to
>> 192.168.0.15. It is worked fine under this situation.
>> After that we got a public ip for leased line and I
added
>> that ip (203.187.255.121). And Primary Dns, Secondary
Dns,
>> Default gateway. So that I can get my local network and
>> internet. But after that I can ping my server to the
>> clients, but clietns can't ping to my server, also
clients
>> can ping each other. what will be problem? how can I
>> solve it? Please help me in this regard
>
>
>.
>

Check to see if your Windows 2003 server has ICF (built-in firewall)
enabled. This would explain why the clients wouldn't be able to ping the
server. Another test that you can run is ping the server from the client and
even if ping times out, run

arp -a

Do you see your server IP and MAC address in the list?

Personally I wouldn't want to run any server in production the way you
describe it (two different range of IPs assigned to NIC -- one public
address and second private address).

Mike

<(E-Mail Removed)> wrote in message
news:1c9401c4a480$bb2d64e0$(E-Mail Removed)...
> I know it will work under 2 network cards, but we can have
> the option to create more ip's through tcp/ip properties.
> So far I am in testing process, so I am not interested to
> give permission to the client mechines connect to internet
> through the windows 2003 server. But I have our internal
> ip 192.168.0.x and I created one more ip that belongs to
> the same network of my router so now I can ping to my
> router and to my client mechines. But why the client
> can't ping into my server? the server and client has same
> ip range, also server can ping to clients. Also tell me
> what is the important of gateway in client mechines for
> our internal network. Do you have any idea regarding this?
> >-----Original Message-----
> >Hi,
> >
> >Do you have one or more NIC (network cards) in your
> Windows 2003 Server?
> >Most likely, you will need two in your server. One to
> connect your server to
> >the internet and another one to connect to LAN
> (192.168.0.x).
> >
> >How is gateway configured on your clients (Windows 2000
> Professional)? Will
> >your clients use Windows 2003 server to access the
> internet?
> >
> >Mike
> >
> >"Sabu" <(E-Mail Removed)> wrote in message
> >news:354501c4a474$3c19ec70$(E-Mail Removed)...
> >> Dear Sirs,
> >> I have configured my Windows 2003 Standered Server with
> >> clients Windows 2000 Professional. I configured the IP
> >> 192.168.0.151 to Windows 2003 Server and I configured
> >> client ip address in the range 192.168.0.1 to
> >> 192.168.0.15. It is worked fine under this situation.
> >> After that we got a public ip for leased line and I
> added
> >> that ip (203.187.255.121). And Primary Dns, Secondary
> Dns,
> >> Default gateway. So that I can get my local network and
> >> internet. But after that I can ping my server to the
> >> clients, but clietns can't ping to my server, also
> clients
> >> can ping each other. what will be problem? how can I
> >> solve it? Please help me in this regard
> >
> >
> >.
> >

It is because of the ICF enable that's why clients can't
communicate with the server. Thank you sir for your
suggestions.

>-----Original Message-----
>Check to see if your Windows 2003 server has ICF (built-
in firewall)
>enabled. This would explain why the clients wouldn't be
able to ping the
>server. Another test that you can run is ping the server
from the client and
>even if ping times out, run
>
>arp -a
>
>Do you see your server IP and MAC address in the list?
>
>Personally I wouldn't want to run any server in
production the way you
>describe it (two different range of IPs assigned to NIC --
one public
>address and second private address).
>
>Mike
>
><(E-Mail Removed)> wrote in message
>news:1c9401c4a480$bb2d64e0$(E-Mail Removed)...
>> I know it will work under 2 network cards, but we can
have
>> the option to create more ip's through tcp/ip
properties.
>> So far I am in testing process, so I am not interested
to
>> give permission to the client mechines connect to
internet
>> through the windows 2003 server. But I have our
internal
>> ip 192.168.0.x and I created one more ip that belongs to
>> the same network of my router so now I can ping to my
>> router and to my client mechines. But why the client
>> can't ping into my server? the server and client has
same
>> ip range, also server can ping to clients. Also tell me
>> what is the important of gateway in client mechines for
>> our internal network. Do you have any idea regarding
this?
>> >-----Original Message-----
>> >Hi,
>> >
>> >Do you have one or more NIC (network cards) in your
>> Windows 2003 Server?
>> >Most likely, you will need two in your server. One to
>> connect your server to
>> >the internet and another one to connect to LAN
>> (192.168.0.x).
>> >
>> >How is gateway configured on your clients (Windows 2000
>> Professional)? Will
>> >your clients use Windows 2003 server to access the
>> internet?
>> >
>> >Mike
>> >
>> >"Sabu" <(E-Mail Removed)> wrote in message
>> >news:354501c4a474$3c19ec70$(E-Mail Removed)...
>> >> Dear Sirs,
>> >> I have configured my Windows 2003 Standered Server
with
>> >> clients Windows 2000 Professional. I configured the
IP
>> >> 192.168.0.151 to Windows 2003 Server and I configured
>> >> client ip address in the range 192.168.0.1 to
>> >> 192.168.0.15. It is worked fine under this
situation.
>> >> After that we got a public ip for leased line and I
>> added
>> >> that ip (203.187.255.121). And Primary Dns, Secondary
>> Dns,
>> >> Default gateway. So that I can get my local network
and
>> >> internet. But after that I can ping my server to the
>> >> clients, but clietns can't ping to my server, also
>> clients
>> >> can ping each other. what will be problem? how can I
>> >> solve it? Please help me in this regard
>> >
>> >
>> >.
>> >
>
>
>.
>