?
Solved

Subnet

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

Optimize your web performance

What's in the eBook?
- Full list of reasons for poor performance
- Ultimate measures to speed things up
- Primary web monitoring types
- KPIs you should be monitoring in order to increase your ROI

Question has a verified solution.

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

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration. My first tip Migration Tip #1 – Source Server Health can be found listed in my profile here: http:…
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…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
In this video, Percona Solution Engineer Dimitri Vanoverbeke discusses why you want to use at least three nodes in a database cluster. To discuss how Percona Consulting can help with your design and architecture needs for your database and infras…

762 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