Re: Windows networking issue
- From: "Alan Siu" <alansiu@xxxxxxxxxxxx>
- Date: Fri, 29 Sep 2006 16:30:21 -0400
Alright, I think I understand what happened. The machine on B network that
doesn't have a gateway assigned won't respond to a ping request from a
network and vice versa. After I configure every host with proper gateway,
everything works. Why does a machine need a gateway to respond a ping
request? Since the routing has been enabled, I thought windows server will
be able to deliver the request to the network that attaches on both network
with proper ip and subnet mask assigned. I am not familiar with routing, is
there any good resources you can give me for reading.
Thanks,
Alan
"Doug Sherman [MVP]" <nodspamherman@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%2326g2j$4GHA.1196@xxxxxxxxxxxxxxxxxxxxxxx
1. Check firewall and/or security software settings and make sure they
are
not set to block ping.
2. Check default gateways and/or static routes on any machines which do
not
respond to ping. These machine must have a valid route back to the ping
source machine.
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"Alan Siu" <alansiu@xxxxxxxxxxxx> wrote in message
news:#iKYbN$4GHA.3604@xxxxxxxxxxxxxxxxxxxxxxx
Hi,only.
Thanks for replying. I did what you said by enabling RRAS LAN Routing
I have a pc with ip 198.168.30.21 and GW 192.168.30.10 (The 2nd NIC onThe
the
server). I was able to ping one machine on the 192.168.0.X network
(192.168.0.107) after enabling the router but not the others. Strangely,
pc with ip 192.168.0.107 can ping back to 192.168.30.21, but not thenetwork.
other
machine on 192.168.30.X network.Why? am I missing something?
Thanks,
Alan
"Doug Sherman [MVP]" <nodspamherman@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:OWneFg%234GHA.3404@xxxxxxxxxxxxxxxxxxxxxxx
You need to do 2 things:
1. On the server enable routing. You can do this with RRAS or edit
the
registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Set the value for IPEnableRouter to 1.
2. The machines on the 192.168.0.x network need a default gateway of
192.168.0.10; or configure a static on the 192.168.0.x machines:
route -p add 192.168.30.0 mask 255.255.255.0 192.168.0.10
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"Alan Siu" <alansiu@xxxxxxxxxxxx> wrote in message
news:u7X6tS#4GHA.4832@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have some windows networking question that I am not sure if it can
be
done.
I have a windows 2003 server that has two NIC cards.
First NIC has an ip 192.168.0.10 mask 255.255.255.0
The second NIC has an ip 192.168.30.10 mask 255.255.255.0
The First NIC card connected to a A switch that has 192.168.0.0
wayThe Second NIC card connected to a B switch that has 192.168.30.0address
network.
From a PC connected to B Switch with static ip 192.168.30.11 mask
255.255.255.0 and gateway 192.168.30.10, I was able to ping both ip
on the windows 2003 server, but if I tried to ping any PC on the192.168.0.0
network (ex. ip 192.168.0.100), I won't be able to ping them.
I am not too familiar with routing, and I want the network stay that
makeand
don't want to add any additional euqipment to the network. How can I
toany PC on the B switch to connect to any PC in the A switch? Do I need
add a route or something to the PC on the B switch in order to make itwork?
If yes, then can you show me how? Thanks a lot.
Thanks,
Alan
.
- Follow-Ups:
- Re: Windows networking issue
- From: Doug Sherman [MVP]
- Re: Windows networking issue
- References:
- Windows networking issue
- From: Alan Siu
- Re: Windows networking issue
- From: Doug Sherman [MVP]
- Re: Windows networking issue
- From: Alan Siu
- Re: Windows networking issue
- From: Doug Sherman [MVP]
- Windows networking issue
- Prev by Date: Block internet radio and MSN messenger.
- Next by Date: Re: Block internet radio and MSN messenger.
- Previous by thread: Re: Windows networking issue
- Next by thread: Re: Windows networking issue
- Index(es):
Relevant Pages
|