Member Avatar for khushhappy

I am having a problem with the configuration setup, I am working in a organization in which
192.198.1.1 ( DHCP)
192.168.1.3 (DNS)
192.168.1.6 (ISA server)- Gateway

Ip to wireless Router i.e. Static Ip ( 192.168.1.23)

  1. I have configured the router by dhcp configuration , but not working.
    can anyone suggest whether to configure through dhcp mode or static ?

  2. And if static, what may be the ip settings of it?

  • 3 Contributors
  • 3 Replies
  • 281 Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by khushhappy

Dani AI

Generated

Likely cause: the Linksys is creating an IP/subnet or DHCP conflict with the corporate network. correctly highlighted the danger of overlapping subnets; correctly warned about running a second DHCP server on the office LAN. Two practical, safe modes address that conflict: run the WRT54GS as an isolated router (NAT) on a different private subnet, or run it as an access point/switch so all clients get addresses from the corporate DHCP.

Router (NAT) mode — use when a separate private network is required:

  1. In the router admin UI set the WAN/Internet interface to the static address assigned by the organization (enter IP, netmask, gateway and DNS exactly as provided by IT).
  2. Change the Linksys LAN subnet to a non-overlapping private range (examples: 10.10.10.0/24 or 172.16.5.0/24).
  3. Enable the router DHCP for that LAN range.
  4. Connect the upstream cable to the router WAN port and verify the WAN status and NAT.

Access-point / LAN-to-LAN mode — preferred when integrating into an existing corporate network:

  1. Assign the router a management IP inside the corporate subnet but outside the DHCP pool.
  2. Disable the router DHCP server.
  3. Connect the upstream cable to a LAN port (do not use the WAN port). Wireless can remain enabled if allowed by network policy; clients will obtain addresses from the corporate DHCP.

Quick verification checklist (no changes should be made before confirming with IT): confirm the org’s assigned IP/gateway/DNS; check client addressing with ipconfig /all or ip addr; verify the router’s WAN page shows the correct gateway; ping the gateway to confirm connectivity. Never leave the Linksys DHCP enabled on a corporate LAN without explicit permission; that is the most common cause of outages and complaints.

Recommended Answers

All 3 Replies

Member Avatar for CimmerianX

Need to get a better understanding of what isn't working? Can you access the router? Does it boot? Does it get an external IP from the network DHCP?

My guess is this: Since linksys default to an internal LAN of 192.168.1.0/24, you probably have the same internal and external LAN. Maybe the linksys doesn't like it.

Disconnect from the network. Connect your PC to the inside lan of the linksys. Your PC should get an IP from the linksys on 192.168.1.0. Conenct to the linksys at Change the internal LAN subnet to something else... like 192.168.15.0 just so it's different than the office lan. Save and restart. Connect it all back up. Connect to the router on 192.168.15.1 (or whatever you chose) and verify it still has 192.168.1.23 statically assigned on the outside. You should be able to connect though it now.

Edited by CimmerianX
Member Avatar for JorgeM

In addition, make sure you disable the dhcp service and wireless. Your organization's network team isn't going to appreciate it very much when your device issues IP leases to other network hosts on the LAN.

Member Avatar for khushhappy

Thanks CimmerianX and JorgeM for solution.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.