Solved

Subnet

Posted on 2008-10-22
3
394 Views
Last Modified: 2010-04-20
I have successfully created subnet using following steps. But I can not ping or RDP from any client on 192.168.1.0 network to client on 192.168.5.0 subnet and vise versa.Though I can ping and RDP from router (Multihomed PC). How can I resolve this issue ?

1. Assigning IP address 192.168.1.17 to second NIC (and 255.255.255.0 mask, no default gateway),  
    enable it
2. Changing default gateway of all devices on second subnet to 192.168.5.17
3. On router adding static route for subnet 192.168.5.0 mask 255.255.255.0 gateway 192.168.1.4
4.  Enabling Routing and Remote Access on 192.168.1.17 server, LAN routing only.

0
Comment
Question by:nakulamin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 8

Expert Comment

by:DocSeltsam
ID: 22774422
Hi nakulamin,

> 1. Assigning IP address 192.168.1.17 to second NIC (and 255.255.255.0 mask, no default
>     gateway),  enable it
> 2. Changing default gateway of all devices on second subnet to 192.168.5.17

So you set the default gateway of all hosts on the 192.168.1.0/24 subnet to 192.168.5.17?

Supposed that the second NIC is connected to the second subnet, try setting the default gateway to 192.168.1.17, then it should work.

--Thomas
0
 

Author Comment

by:nakulamin
ID: 22774496
1.I have assiged ip address 192.168.5.17 , 255.255.255 and no default gatewat to second NIC

2.I have changed default gateway of all devices on second subnet to 192.168.5.17 with static address
   of 192.168.5.x
3.Default gateway of all host on 192.168.1.0 subnet is 192.168.1.2

I tried to set default gateway of second NIC(192.168.5.17) to 192.168.1.17 but didn't work....





 
0
 
LVL 8

Accepted Solution

by:
DocSeltsam earned 500 total points
ID: 22775305
Hmm, ok.

Router:
  NIC 1: 192.168.1.17, no default gateway
  NIC 2: 192.168.5.17, no default gateway
  Static route 192.168.5.0 mask 255.255.255.0 gateway 192.168.1.4

Clients, 192.168.1.x
  NIC: 192.168.1.x, default gatway 192.168.1.17

Clients, 192.168.5.x
  NIC: 192.168.5.x, default gatway 192.168.5.17

Since you've Enabled Routing and Remote Access with 'LAN routing only' on the router, the static route for the 192.168.5.0 network should be unnecessary.

Did you try this already?

--Thomas
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After having deployed hundreds of thousands of Terminal Services seats worldwide, I still see all the time people asking me that same old question: "If TS/RDS is that reliable why are you telling me I should reboot it that often? My DC/SQL/Exchange/…
Some time ago I faced the need to use a uniform folder structure that spanned across numerous sites of an enterprise to be used as a common repository for the Software packages of the Configuration Manager 2007 infrastructure. Because the procedu…
Are you ready to implement Active Directory best practices without reading 300+ pages? You're in luck. In this webinar hosted by Skyport Systems, you gain insight into Microsoft's latest comprehensive guide, with tips on the best and easiest way…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question