Hello all,
after trying and googling a lot I decided to open a new thread about my problem.
We have a 3Com 5500G-EI Stack (4x L3-Switches) with one VLAN-Interface. (homed in 5 different subnets)
The problem is:
- we try to wake up clients via WOL in different subnets with SCCM2007
- SCCM sends subnet-directed broadcasts (e.g. 192.168.10.255 for subnet 192.168.10.0/24)
I think here must be the problem
I googled and found that ip forward-broadcast has to be enabled for the system and the corresponding VLAN-interface.
-> enabling this function didn't work for our scenario.
-> this command should convert sn-directed-broadcast into broadcasts to 255.255.255.255?? (L2)
Sniffing on the destination machine gave the following results:
- subnet-directed broadcasts are only received if the sending computer is in the same subnet.
- a broadcast to 255.255.255.255 is received over different subnets
-> SCCM has no option to send packets to 255.255.255.255
Configuration / already working:
- all clients are already configured correctly and can be woke up with a pc in their subnet (using sn-directed broadcasts)
- all clients can be woke up by sending the magic packet with an extra tool to 255.255.255.255 (it doesn't matter in which subnets they are)
I hope someone can help me to fix this problem.
Thanks in advance!
after trying and googling a lot I decided to open a new thread about my problem.
We have a 3Com 5500G-EI Stack (4x L3-Switches) with one VLAN-Interface. (homed in 5 different subnets)
The problem is:
- we try to wake up clients via WOL in different subnets with SCCM2007
- SCCM sends subnet-directed broadcasts (e.g. 192.168.10.255 for subnet 192.168.10.0/24)
I think here must be the problem
I googled and found that ip forward-broadcast has to be enabled for the system and the corresponding VLAN-interface.
-> enabling this function didn't work for our scenario.
-> this command should convert sn-directed-broadcast into broadcasts to 255.255.255.255?? (L2)
Sniffing on the destination machine gave the following results:
- subnet-directed broadcasts are only received if the sending computer is in the same subnet.
- a broadcast to 255.255.255.255 is received over different subnets
-> SCCM has no option to send packets to 255.255.255.255
Configuration / already working:
- all clients are already configured correctly and can be woke up with a pc in their subnet (using sn-directed broadcasts)
- all clients can be woke up by sending the magic packet with an extra tool to 255.255.255.255 (it doesn't matter in which subnets they are)
I hope someone can help me to fix this problem.
Thanks in advance!