Hot Downloads

×

Notice

The forum is in read only mode.
Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1
  • 2

TOPIC: Cannot access server in different subnet

Cannot access server in different subnet 11 years 3 months ago #22091

hi all, im having a problem with my network, first, all user was assigned ip from DHCP server (172.x.x.x) and all the server have been set with static IP (10.x.x.x), how user can access the server?

Re: Cannot access server in different subnet 11 years 3 months ago #22092

  • Smurf
  • Smurf's Avatar
  • Offline
  • Moderator
  • Moderator
  • Posts: 1390
  • Karma: 1
  • Thank you received: 0
Hi,

Its not a problem with the network as such, its your addressing. A few options;

1. Configure a routing device to route between both subnets
2. Change the ip address ranges so both the clients and servers are in the same range.

Cheers

Wayne

Re: Cannot access server in different subnet 11 years 3 months ago #22192

Murphy was right! The server and the clients should be on one network. So the clients will be able to access the server. :)

<yuan> :D

Re: Cannot access server in different subnet 11 years 3 months ago #22203

ok...thanks for your advice...really appreciated it...

Re: Cannot access server in different subnet 11 years 3 months ago #22220

So in the Internet, how is it that networks on different networks can communicate with each other? What exactly do you configure on the router that allows it to be able to allow two two different networks communicate with each other? Is a SOHO router capable of this?

thanks
K

Re: Cannot access server in different subnet 11 years 3 months ago #22221

  • nske
  • nske's Avatar
  • Offline
  • Expert Member
  • Expert Member
  • Posts: 613
  • Thank you received: 0
Each IP host has a routing table that defines through which gateway (router) it will access each network to which is no part of. Routers, likewise, have such a table, only that they are configured to also accept traffic from other hosts in one network and forward it to hosts in an other network. Of course they need to have an interface to every network that they will forward packets to and from, in order to do that. Any embedded router and any PC, as long as they have the appropriate interfaces to connect to of all our IP networks (commonly Ethernet adapters, but can also be other types of physical or virtual interfaces), can do that job. The table can be populated statically, by the administrator.

In cases where our network contains many routers and many sub-networks, like in the case of Internet, populating and maintaining the routing table manually is painful, that's why there are several Dynamic Routing protocols, that handle the automatic negotiation to transfer routing information from a router the an other. According to the KISS approach, it is wise to not use dynamic routing unless you have to.

For detailed information you can check the tutorials for routing and IP in this site ;)
  • Page:
  • 1
  • 2
Time to create page: 0.198 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup