Networking Forums

Networking Forums > Computer Networking > Windows Networking > Windows networking issue

Reply
Thread Tools Display Modes

Windows networking issue

 
 
Alan Siu
Guest
Posts: n/a

 
      09-29-2006, 04:28 PM
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 network.
The Second NIC card connected to a B switch that has 192.168.30.0 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 address
on the windows 2003 server, but if I tried to ping any PC on the 192.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 way and
don't want to add any additional euqipment to the network. How can I make
any PC on the B switch to connect to any PC in the A switch? Do I need to
add a route or something to the PC on the B switch in order to make it work?
If yes, then can you show me how? Thanks a lot.

Thanks,
Alan


 
Reply With Quote
 
 
 
 
Doug Sherman [MVP]
Guest
Posts: n/a

 
      09-29-2006, 04:55 PM
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\Servic es\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" <(E-Mail Removed)> wrote in message
news:u7X6tS#(E-Mail Removed)...
> 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 network.
> The Second NIC card connected to a B switch that has 192.168.30.0 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

address
> on the windows 2003 server, but if I tried to ping any PC on the

192.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 way

and
> don't want to add any additional euqipment to the network. How can I make
> any PC on the B switch to connect to any PC in the A switch? Do I need to
> add a route or something to the PC on the B switch in order to make it

work?
> If yes, then can you show me how? Thanks a lot.
>
> Thanks,
> Alan
>
>



 
Reply With Quote
 
Alan Siu
Guest
Posts: n/a

 
      09-29-2006, 06:13 PM
Hi,

Thanks for replying. I did what you said by enabling RRAS LAN Routing only.
I have a pc with ip 198.168.30.21 and GW 192.168.30.10 (The 2nd NIC on 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, The
pc with ip 192.168.0.107 can ping back to 192.168.30.21, but not the other
machine on 192.168.30.X network.Why? am I missing something?

Thanks,
Alan

"Doug Sherman [MVP]" <(E-Mail Removed)> wrote in
message news:OWneFg%(E-Mail Removed)...
> 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\Servic es\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" <(E-Mail Removed)> wrote in message
> news:u7X6tS#(E-Mail Removed)...
>> 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 network.
>> The Second NIC card connected to a B switch that has 192.168.30.0
>> 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

> address
>> on the windows 2003 server, but if I tried to ping any PC on the

> 192.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 way

> and
>> don't want to add any additional euqipment to the network. How can I make
>> any PC on the B switch to connect to any PC in the A switch? Do I need to
>> add a route or something to the PC on the B switch in order to make it

> work?
>> If yes, then can you show me how? Thanks a lot.
>>
>> Thanks,
>> Alan
>>
>>

>
>



 
Reply With Quote
 
Doug Sherman [MVP]
Guest
Posts: n/a

 
      09-29-2006, 06:56 PM
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" <(E-Mail Removed)> wrote in message
news:#iKYbN$(E-Mail Removed)...
> Hi,
>
> Thanks for replying. I did what you said by enabling RRAS LAN Routing

only.
> I have a pc with ip 198.168.30.21 and GW 192.168.30.10 (The 2nd NIC on 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,

The
> pc with ip 192.168.0.107 can ping back to 192.168.30.21, but not the other
> machine on 192.168.30.X network.Why? am I missing something?
>
> Thanks,
> Alan
>
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in
> message news:OWneFg%(E-Mail Removed)...
> > 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\Servic es\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" <(E-Mail Removed)> wrote in message
> > news:u7X6tS#(E-Mail Removed)...
> >> 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

network.
> >> The Second NIC card connected to a B switch that has 192.168.30.0
> >> 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

> > address
> >> on the windows 2003 server, but if I tried to ping any PC on the

> > 192.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

way
> > and
> >> don't want to add any additional euqipment to the network. How can I

make
> >> any PC on the B switch to connect to any PC in the A switch? Do I need

to
> >> add a route or something to the PC on the B switch in order to make it

> > work?
> >> If yes, then can you show me how? Thanks a lot.
> >>
> >> Thanks,
> >> Alan
> >>
> >>

> >
> >

>
>



 
Reply With Quote
 
Alan Siu
Guest
Posts: n/a

 
      09-29-2006, 08:30 PM
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]" <(E-Mail Removed)> wrote in
message news:%2326g2j$(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:#iKYbN$(E-Mail Removed)...
>> Hi,
>>
>> Thanks for replying. I did what you said by enabling RRAS LAN Routing

> only.
>> I have a pc with ip 198.168.30.21 and GW 192.168.30.10 (The 2nd NIC on
>> 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,

> The
>> pc with ip 192.168.0.107 can ping back to 192.168.30.21, but not the
>> other
>> machine on 192.168.30.X network.Why? am I missing something?
>>
>> Thanks,
>> Alan
>>
>> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in
>> message news:OWneFg%(E-Mail Removed)...
>> > 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\Servic es\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" <(E-Mail Removed)> wrote in message
>> > news:u7X6tS#(E-Mail Removed)...
>> >> 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

> network.
>> >> The Second NIC card connected to a B switch that has 192.168.30.0
>> >> 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
>> > address
>> >> on the windows 2003 server, but if I tried to ping any PC on the
>> > 192.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

> way
>> > and
>> >> don't want to add any additional euqipment to the network. How can I

> make
>> >> any PC on the B switch to connect to any PC in the A switch? Do I need

> to
>> >> add a route or something to the PC on the B switch in order to make it
>> > work?
>> >> If yes, then can you show me how? Thanks a lot.
>> >>
>> >> Thanks,
>> >> Alan
>> >>
>> >>
>> >
>> >

>>
>>

>
>



 
Reply With Quote
 
Doug Sherman [MVP]
Guest
Posts: n/a

 
      09-29-2006, 09:45 PM
If a machine on the 192.168.0.x network does not have a default gateway or
static route, then when it receives a ping from a machine on the
192.168.30.x network, it doesn't know where to send the reply - it won't
automatically send it to the server. If the 192.168.0.x machine has a
default gateway, it will send the reply there. If it has a static route for
the remote network, it will send the reply to the gateway configured for the
route.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"Alan Siu" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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]" <(E-Mail Removed)> wrote in
> message news:%2326g2j$(E-Mail Removed)...
> > 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" <(E-Mail Removed)> wrote in message
> > news:#iKYbN$(E-Mail Removed)...
> >> Hi,
> >>
> >> Thanks for replying. I did what you said by enabling RRAS LAN Routing

> > only.
> >> I have a pc with ip 198.168.30.21 and GW 192.168.30.10 (The 2nd NIC on
> >> 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,
> > The
> >> pc with ip 192.168.0.107 can ping back to 192.168.30.21, but not the
> >> other
> >> machine on 192.168.30.X network.Why? am I missing something?
> >>
> >> Thanks,
> >> Alan
> >>
> >> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote

in
> >> message news:OWneFg%(E-Mail Removed)...
> >> > 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\Servic es\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" <(E-Mail Removed)> wrote in message
> >> > news:u7X6tS#(E-Mail Removed)...
> >> >> 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

> > network.
> >> >> The Second NIC card connected to a B switch that has 192.168.30.0
> >> >> 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
> >> > address
> >> >> on the windows 2003 server, but if I tried to ping any PC on the
> >> > 192.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

> > way
> >> > and
> >> >> don't want to add any additional euqipment to the network. How can I

> > make
> >> >> any PC on the B switch to connect to any PC in the A switch? Do I

need
> > to
> >> >> add a route or something to the PC on the B switch in order to make

it
> >> > work?
> >> >> If yes, then can you show me how? Thanks a lot.
> >> >>
> >> >> Thanks,
> >> >> Alan
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>

> >
> >

>
>



 
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
Windows 2008 x64 SP2 & R2 Networking Issue Ruben Mendoza Windows Networking 3 07-01-2010 10:51 PM
No logon server available - Windows 2003 Trust Issue? NS Issue? newsgroups.jd@gmail.com Windows Networking 15 08-21-2006 07:38 PM
Odd Networking Issue: Windows vs Linux RedPenguin Linux Networking 8 02-25-2006 07:01 PM
Networking Issue with Microsoft Windows XP Home =?Utf-8?B?SUMgSUNUIFNMSWRkbGU=?= Broadband Hardware 0 06-15-2005 09:54 AM
Windows ME to 98SE networking issue Eric Windows Networking 1 09-18-2003 06:08 AM



1 2 3 4 5 6 7 8 9 10 11