JesusFreak42
asked on
DHCP, VLANS, and Linksys E4200
Hello,
Here's the setup:
1) Windows Server 2008 R2
2) CIsco 3750-G Switch configured for multicasting on VLAN 200 (192.168.1.0/24)
3) Linksys E4200 at addres 192.168.1.1 running dhcp
The situation is that no wireless clients are receiving DHCP addresses. Do I need to setup something on the port the Linksys router is plugged into. Does it need to be routed through that port to a different subnet?
Here's the setup:
1) Windows Server 2008 R2
2) CIsco 3750-G Switch configured for multicasting on VLAN 200 (192.168.1.0/24)
3) Linksys E4200 at addres 192.168.1.1 running dhcp
The situation is that no wireless clients are receiving DHCP addresses. Do I need to setup something on the port the Linksys router is plugged into. Does it need to be routed through that port to a different subnet?
ASKER
What vlan is the port the Linksys E4200 plugged into and what vlan is the server 2008 r2?
They are both on VLAN 200
Are any other devices running a DHCP service on that same subnet?
No.
The VLAN question might be the total wrong question, but I did read someplace that someone was having a similar issue. They had not solved it, but it seemed to have to do with the VLANS. The confusing thing to me is that the switch is not between the wireless clients and the router. I used to have DHCP running on the 2008 server, but because of this issue I moved it to the router. It didn't help. Does the wireless default to VLAN 1 or something?
They are both on VLAN 200
Are any other devices running a DHCP service on that same subnet?
No.
The VLAN question might be the total wrong question, but I did read someplace that someone was having a similar issue. They had not solved it, but it seemed to have to do with the VLANS. The confusing thing to me is that the switch is not between the wireless clients and the router. I used to have DHCP running on the 2008 server, but because of this issue I moved it to the router. It didn't help. Does the wireless default to VLAN 1 or something?
I just realized that since DHCP is on the router then the wireless clients should get IP addresses even if the router isn't on the correct VLAN.
If you'd rather have the DHCP on the 2008 R2 server (which I know I would prefer) then you can do the following:
1. Plug one of the LAN ports of the router into the Cisco switch
2. Configure that port as switchport access mode then set it to VLAN 200
3. Turn DHCP off on the router
4. Make sure the port that the Server is plugged into is also on VLAN 200 in switchport access mode (servers are capable of communicating on more than one VLAN, but you have to add a utility to do this. By default they don't)
5. Turn on and configure DHCP on the 2008 R2 server.
If you'd rather have the DHCP on the 2008 R2 server (which I know I would prefer) then you can do the following:
1. Plug one of the LAN ports of the router into the Cisco switch
2. Configure that port as switchport access mode then set it to VLAN 200
3. Turn DHCP off on the router
4. Make sure the port that the Server is plugged into is also on VLAN 200 in switchport access mode (servers are capable of communicating on more than one VLAN, but you have to add a utility to do this. By default they don't)
5. Turn on and configure DHCP on the 2008 R2 server.
ASKER
Just out of curiousity, I have never worked with Multicasting before. Would this affect anything?
It could if your multicasting subnet is on a different VLAN. Are you using multicasting for workstation imaging? Like a ghostcast server or M$ WDS?
ASKER
Two things:
First, here is the config that I have on the switch (edited out some security settings)
Second, the use of the switch is that we are streaming video over 20 of the ports, and then feeding the video into several workstations and servers also attached to the switch. One port is for the router.
First, here is the config that I have on the switch (edited out some security settings)
Using keyboard-interactive authentication.
Password:
Prototype#sh run
Building configuration...
Current configuration : 5157 bytes
!
version 15.0
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname Prototype
!
boot-start-marker
boot-end-marker
!
!
no aaa new-model
clock timezone UTC -5 0
clock summer-time UTC recurring
system mtu routing 1500
ip routing
ip domain-name prototype
ip name-server 192.168.1.10
!
!
!
ip multicast-routing distributed
!
!
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
ip ssh version 2
!
!
!
!
!
!
interface GigabitEthernet0/1
description Video 1
switchport access vlan 200
!
interface GigabitEthernet0/2
description Video 2
switchport access vlan 200
!
interface GigabitEthernet0/3
description Video 3
switchport access vlan 200
!
interface GigabitEthernet0/4
description Video 4
switchport access vlan 200
!
interface GigabitEthernet0/5
description Video 5
switchport access vlan 200
!
interface GigabitEthernet0/6
description Video 6
switchport access vlan 200
!
interface GigabitEthernet0/7
description Video 7
switchport access vlan 200
!
interface GigabitEthernet0/8
description Video 8
switchport access vlan 200
!
interface GigabitEthernet0/9
description Video 9
switchport access vlan 200
!
interface GigabitEthernet0/10
description Video 10
switchport access vlan 200
!
interface GigabitEthernet0/11
description Video 11
switchport access vlan 200
!
interface GigabitEthernet0/12
description Video 12
switchport access vlan 200
!
interface GigabitEthernet0/13
description Video 13
switchport access vlan 200
!
interface GigabitEthernet0/14
description Video 14
switchport access vlan 200
!
interface GigabitEthernet0/15
description Video 15
switchport access vlan 200
!
interface GigabitEthernet0/16
description Video 16
switchport access vlan 200
!
interface GigabitEthernet0/17
description Video 17
switchport access vlan 200
!
interface GigabitEthernet0/18
description Video 18
switchport access vlan 200
!
interface GigabitEthernet0/19
description Video 19
switchport access vlan 200
!
interface GigabitEthernet0/20
description Video 20
switchport access vlan 200
!
interface GigabitEthernet0/21
description Internet
switchport access vlan 200
!
interface GigabitEthernet0/22
description Computer 1
switchport access vlan 200
!
interface GigabitEthernet0/23
description Computer 2
switchport access vlan 200
!
interface GigabitEthernet0/24
description Computer 3
switchport access vlan 200
!
interface GigabitEthernet0/25
description Computer 4
switchport access vlan 200
!
interface GigabitEthernet0/26
description Computer 5
switchport access vlan 200
!
interface GigabitEthernet0/27
description Computer 6
switchport access vlan 200
!
interface GigabitEthernet0/28
description Computer 7
switchport access vlan 200
!
interface Vlan1
ip address 192.168.3.1 255.255.255.0
ip pim sparse-dense-mode
!
interface Vlan200
ip address 192.168.1.2 255.255.255.0
ip pim sparse-dense-mode
!
ip default-gateway 192.168.1.1
ip http server
ip http authentication local
ip http secure-server
!
!
ip route 0.0.0.0 0.0.0.0 192.168.1.1
!
logging esm config
!
!
!
!
endSecond, the use of the switch is that we are streaming video over 20 of the ports, and then feeding the video into several workstations and servers also attached to the switch. One port is for the router.
If your server has an address on the 192.168.1.x subnet and the wireless clients need to communicate with that server then both the server and your router must be on the same VLAN and my suggestion will work for you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are any other devices running a DHCP service on that same subnet?