Jump to content

sshabir

Members
  • Posts

    36
  • Joined

  • Last visited

Reputation

5 Neutral

About sshabir

Personal Information

  • Occupation
    IT Manager
  • Interests
    Football
  1. Did you manage to figure it out then?
  2. Thanks Koldov. Very helpful!
  3. I have both Dns server installed on Windows server 2019. Both are linked by a trust. Each dns server is using each other as preferred DNS server and itself as 'Alternative dns server.
  4. Both dns are Server 2019 and are joined by a trust.
  5. Hi All, I have 2 domain setup (Curriculum and Admin) and am just wondering if this is correct? If I go to 'DNS\Conditional Forwarders\Srv name\Properties\click 'Edit' on the server I can see the Ip address and Server FQDN but get a cross next to the ip address. The server with this IP address is not authoritative for the required zone. Is something wrong between 2 servers? Thanks Shoaib
  6. HI All, I am wondering if someone can point me to the right direction. I have 2 domain controllers in our network. On one DC I can run nslookup for both servers with ip address and host name fine but with the other server if I do nslookup with a server ip address I get the below error message but works fine with hostname. Can't find the ip address xxxx. Non existent domain. Thanks Shoaib
  7. Thanks Jcx500 it was the port 53 which was not open on our firewall. Shoaib
  8. I am not sure if port 53 is open hence raised a help desk ticket with Rm to confirm. Under 'Forwarder' tab on Dns manager i can resolve Rm Dns ip OK (194.238.50.0 & 194.238.50.3).
  9. Hi All, 1- We are with Rmbroadband and am using the 'Rm Dns Ip addresses' (194.238.50.0 & 194.238.50.3) in our Dnsmanager which validate OK but under server FQDN it says 'Unable to resolve'. 2- In the same place under 'Root Hints' all the ip address get an error message while'validating' A timeout occurred during validation. I am using Windows Server 2019 Any ideas why this is happening? Thanks Shoaib
  10. Reply from RM: Please be informed that the router is the gateway to the ISP and we did not understand what you meant by core router. As I informed earlier, the router will routes all the networks which comes under the network 10.141.80.1/22 (255.255.252.0). As per your update, the current DHCP server is set to release the IP ranges from 10.141.80.64 to 10.141.81.254. This network is 10.141.80.1/23 which is under the main network 10.141.80.1/22. So, there will not be any connectivity issue. - - - Updated - - - Thanks for your help!
  11. It is set up on the Router but not on the switches.
  12. @Jcx500- The AR129 is a router with gateway but i have asked to confirm with Rm.
  13. I was trying to avoid that possibility if i could as it does require a lot more work. How long did it take you and and advice if you were to redo it again? Thanks
  14. The router has always been using /22 mask but the dhcp server is setup to use /23 mask. By using /23 mask it works fine with current scope set up. I did try to expand the current dhcp scope using the below but got an error message: Start: 10.141.80.64 End-10.141.83.254 Subnet Mask-255.255.254.0 (Grayed out) Error message after applying the setting: The specified range either overlaps an existing range or is not valid. AR129 Router details: https://www.router-switch.com/pdf/ar129-datasheet.pdf Many Thanks
  15. Hi All, I am in an interesting situation where I am trying to expand my Ip range with Rm Networks. We currently have an ip range set to: 10.141.80.0-10.141.81.254/23 (255.255.254.0) The ip range has been increased to 10.141.83.254/22 (255.255.252.0) Rm Networks says the router is set up with /22 subnet but my dhcp server is set up with /23 (255.255.254.0)subnet I have created another scope with the below: 10.141.82.1-10.141.83.254 /23 but it is not working. we are using a Windows Server 2019. I reserved one of the ip address to use the newly created scope ip address but it was connected to wi-Fi but was not connecting to any of the websites or apps. I would like to use the scope settings if possible 10.141.82.1-10.141.83.254 /23. It should be possible if the dhcp server is working fine with 10.141.80.1-10.141.81.254 /23? Any help or advice is much appreciated as I don't want to lose any reserved ip setting while changing any of the settings. Thanks in advance.
×
×
  • Create New...