Unable to see the base side network

Toggle sidebar Toggle sidebar
S

srkraidu

Distinguished
Aug 16, 2012
19
0
18,520
Input to the router - ip 192.168.1.xxx (Internet Port)

Router working on ip 192.168.0.1 (not allowing to change the ip - Error coming as: DHCP pool should be in the same network with gateway address). Router is Dlink DIR 615. Support from Dlink couldn't provide a single valid ip that is valid and acceptable to router.

As the Router is on 192.168.0.1 and the network is on 192.168.1.xxx, i could not see the the network that is on 192.168.1.xxx

Detailed Description:
Have a base network - IP 192.168.1.77 Subnet: 255.255.0.0 Gateway: 192.168.251.1 (for the wire that taken from another router)

Added the above as input to router

Config on router: IP: 192.168.0.2 Subnet: 255.255.255.0 DNS Server: 192.168.0.1
Dlink DIR - 615 As per the manufacturer, they didn't provide any other valid ipconfig other than the above.

The wire emanating from router is connected to the PC and able to get internet but not the base network. Any solution in resoluting the same is commendable.


Hope the below clears the configuration in the system

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\XXX>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : XX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.name

Ethernet adapter Local Area Connection 5:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a5b1:8bd9:eddd:11b1%33(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.250.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.251.1
DHCPv6 IAID . . . . . . . . . . . : 553779276
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-F2-0A-CC-8C-DC-D4-41-69-A4

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 4:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : EasyTether Network Adapter
Physical Address. . . . . . . . . : 02-00-54-74-68-71
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain.name
Description . . . . . . . . . . . : Intel(R) Ethernet Connection I217-LM
Physical Address. . . . . . . . . : 8C-DC-D4-41-69-A5
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::7474:9ac6:1c64:6be8%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.2(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, June 23, 2017 3:53:00 PM
Lease Expires . . . . . . . . . . : Friday, June 23, 2017 6:52:59 PM
Default Gateway . . . . . . . . . : fe80::a2ab:1bff:fed6:9bb7%11
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 244112596
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-F2-0A-CC-8C-DC-D4-41-69-A4

DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.domain.name:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : domain.name
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:90d7:209e:2c00:3f57:fffd(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::209e:2c00:3f57:fffd%12(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{4A57CD7C-EF9B-485A-914F-813C38859285}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{E2DC0576-0791-4DD2-AD5F-CE7BBB33E294}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
 
Solution
B
Just use the 10.x.x.x block for your lan ip and then you will not get a conflict. It is not common to use 255.255.0.0 mask with ip out of the 192.168 range. It works and is valid it is just common so some times you see software issues because they did not test the firmware properly.
Sort by date Sort by votes
B

bill001g

Titan
Aug 9, 2012
28,277
2,741
125,640
The whole thing that makes IP addresses work properly is the subnet masks. You can not mix this on same network. All devices that connect to the same LAN/network must have the same mask. If you mix them you get inconsistent results. Some things work and other will not but it is not a recommended install.

You can make it work by being even more non standard. Just put in static routes for the subnets you want and point them to the gateway. The traffic may still not know how to get back it depends on many things.

Pretty much the only way to fix this is to define your subnet masks so all devices on the same segment use the same.
 
Upvote 0 Downvote
S

srkraidu

Distinguished
Aug 16, 2012
19
0
18,520


Thank you for response bill.

Here i am trying to change the ip address of the router. Router not allowing to change ip's or subnet masks as per the incoming ip address.

For Instance: the incoming ip is: 192.168.1.77
255.255.0.0
192.168.1.251

I am giving ip range for router: 192.168.1.248 to 192.168.1.249 (the unassigned free range for checking)
with the above subnets and gateway

Any suggestion regarding Dlink DIR-615 router if configured from its default ip's is welcome, as dlink failed to provide an acceptable range for the issue "Dhcp pool should be in the same network with gateway address".
 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,277
2,741
125,640
Just use the 10.x.x.x block for your lan ip and then you will not get a conflict. It is not common to use 255.255.0.0 mask with ip out of the 192.168 range. It works and is valid it is just common so some times you see software issues because they did not test the firmware properly.
 
Upvote 0 Downvote
Solution
S

srkraidu

Distinguished
Aug 16, 2012
19
0
18,520


Thank you.

Only option left out.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom