Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 10 replies
  • Subscribers 3 subscribers
  • Views 35277 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DHCP Reservations Not Working

LawrenceReynolds

I have a Sophos UTM 220. We have four DHCP server scopes setup. 192.168.1.xx, 2.xx, 3.xx, 4.xx. The 4.xx server is designated as the guest network. We have setup network definitions for computers on the 1.xx, 2.xx, and 3.xx network. However when computers, that have a reservation on one of these networks, are turned on and log on they are getting an ip address on the guest network instead of their network definition ip address. Right now to prevent this we have to disable the guest network. Once disable the computers will get the proper ip address according to the network definition. Why is this happening? To fix it right now we are having to ipconfig /release and then ipconfig /renew. Then they get the proper ip address and work good. But later on they will once again get a ip address on the guest network. Not sure what is going on!! Please suggest.



This thread was automatically locked due to age.
Parents
  • 0
    I had a similar issue a while back (not with the Sophos), and it turned out that our VLANs were misconfigured. Some ports were tagging with the wrong VLAN identifiers and because of that, the PCs on those networks were being assigned incorrectly. If you're using VLANs, I would check there and make sure that there isn't an extra tag or two being used.
Reply
  • 0
    I had a similar issue a while back (not with the Sophos), and it turned out that our VLANs were misconfigured. Some ports were tagging with the wrong VLAN identifiers and because of that, the PCs on those networks were being assigned incorrectly. If you're using VLANs, I would check there and make sure that there isn't an extra tag or two being used.
Children
Unfiltered HTML