|I have yet to work with any managed D-Link switches so am unfamiliar with those models. |
If your trunk ports aren't configured correctly, then clients will not be able to talk to the DHCP server. When you set the fiber link up, did you confirm connectivity between switches? If not, this is step one after making the physical connection.
You state the second switch has no VLAN. By this I'm assuming you mean, you've left it setup with the factory defaults which in every switch I've worked on is, VLAN 1 (the default VLAN) is assigned to every port on the switch. If this is true for your switch, then you need to ensure VLAN 1 is the primary VLAN on the port of the other switch you're connecting to. Again, both ports would have to be configured as "trunk" ports and set to "Tag all"
When working with VLAN's you need to duplicate VLAN's across all switches. For example....
Where I work, VLAN 1 (default) is our management VLAN. All network appliances have IP's on the subnet belonging to this VLAN and no other devices (printers, clients, etc) use this subnet/VLAN. So, if I were to add a switch to my network and leave it with the default configuration (ie: VLAN 1 on all ports) then clients would not be able to communicate as they are on different VLAN's.
So, lets say your client is using VLAN 2 and that's the VLAN your client DHCP server resides on. Now you plug a client computer onto your new switch, even if you have the uplink ports configured correctly, if the client is plugging into a port that's assigned VLAN 1, it will not be able to reach the DHCP server because it's on VLAN 2. VLAN's 1 and 2 are segregated from each other and do not speak to each other. You would therefore have to create VLAN 2 on your new switch, add that VLAN to the uplink (trunk) port and then, it could reach the DHCP server.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.
message edited by Curt R