Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Subnet

Posted on 2008-10-22
3
Medium Priority
?
408 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
  • 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 1500 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

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

Question has a verified solution.

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

Problem Description: Actually I found the below issue with some customers after migration from SMS 2003 to SCCM 2007 and epically if they change site code, some clients may appear in the console with old site code, plus old sites still appearing …
Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
this video summaries big data hadoop online training demo (http://onlineitguru.com/big-data-hadoop-online-training-placement.html) , and covers basics in big data hadoop .
Is your OST file inaccessible, Need to transfer OST file from one computer to another? Want to convert OST file to PST? If the answer to any of the above question is yes, then look no further. With the help of Stellar OST to PST Converter, you can e…
Suggested Courses

572 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