+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 19
Windows Server 2008 R2 Thread, PCs on IP range very slow login in Technical; Hi all, We moved from CC3 to Vanilla over the summer and an external company (i wont mention names) setup ...
  1. #1

    Join Date
    Mar 2010
    Location
    Gloucestershire
    Posts
    148
    Thank Post
    20
    Thanked 3 Times in 3 Posts
    Rep Power
    9

    PCs on IP range very slow login

    Hi all,

    We moved from CC3 to Vanilla over the summer and an external company (i wont mention names) setup AD, DHCP and DNS and I did the rest. We run Ip addresses over x.x.44.x and x.x.45.x. Whilst using Spiceworks I noticed x.x.45.x PCs weren't scanning, so after checking everything else I thought I would check DNS. DNS forward lookup zones all fine, checked the reverse lookup zones and I noticed that only the x.x.44 range folder was in there, so I created the x.x.45 range folder and bipadebopadeeboop the ip addresses suddenly appeared and rescanning Spiceworks all PCs are scanned fine.

    But I am still noticing that the PCs with x.x.45.x ip addresses are still logging on very slowly compared to the PCs on the other IP range. Is there something else I need to do to DNS for this range?

    Any help would be greatly appreciated.

    Cheers

  2. #2

    Join Date
    Feb 2007
    Posts
    313
    Thank Post
    93
    Thanked 25 Times in 22 Posts
    Rep Power
    22
    If you go to a machine in the 45 range and tracert to a server in the 44 range, does it go via your default gateway address or does it go straight to the server? If so, it is a routing issue and needs to be resolved by whoever manages your router.

  3. #3

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,241
    Thank Post
    239
    Thanked 1,567 Times in 1,249 Posts
    Rep Power
    339
    Have you tried stopping and restarting DNS Server? Are you operating any VLANs?

  4. #4

    Join Date
    Mar 2010
    Location
    Gloucestershire
    Posts
    148
    Thank Post
    20
    Thanked 3 Times in 3 Posts
    Rep Power
    9
    Hey, thanks for the quick reply. On a 44 range machine it went straight to the server when I tracert to the server DNS name and IP address. On the 45 range machine I tracert to the server using the server ip address it went straight to it, but when I tracert to the server using the dns name it goes to the gateway and to other places before it starts to timeout I stopped the tracert after about 16 hops.

  5. #5

    Join Date
    Mar 2010
    Location
    Gloucestershire
    Posts
    148
    Thank Post
    20
    Thanked 3 Times in 3 Posts
    Rep Power
    9
    Hi Michael,

    Thanks for the reply.

    We are not operating any VLANs and I have restarted DNS.

    Cheers

  6. #6

    Join Date
    Feb 2007
    Posts
    313
    Thank Post
    93
    Thanked 25 Times in 22 Posts
    Rep Power
    22
    Quote Originally Posted by sadams1980 View Post
    Hey, thanks for the quick reply. On a 44 range machine it went straight to the server when I tracert to the server DNS name and IP address. On the 45 range machine I tracert to the server using the server ip address it went straight to it, but when I tracert to the server using the dns name it goes to the gateway and to other places before it starts to timeout I stopped the tracert after about 16 hops.
    Do you have 2 different DHCP scopes for each range? Have you tried creating 1 scope to cover all 44 and 45 IP range?

  7. #7

    Join Date
    Mar 2010
    Location
    Gloucestershire
    Posts
    148
    Thank Post
    20
    Thanked 3 Times in 3 Posts
    Rep Power
    9
    No we have 1 DHCP scope that covers both ranges.

  8. #8

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,241
    Thank Post
    239
    Thanked 1,567 Times in 1,249 Posts
    Rep Power
    339
    Quote Originally Posted by sadams1980 View Post
    Hey, thanks for the quick reply. On a 44 range machine it went straight to the server when I tracert to the server DNS name and IP address. On the 45 range machine I tracert to the server using the server ip address it went straight to it, but when I tracert to the server using the dns name it goes to the gateway and to other places before it starts to timeout I stopped the tracert after about 16 hops.
    That would explain why logons are slow. Workstations are looking outside for information which is in fact on your LAN. I can't quite work out why .44 works and .45 doesn't however. Do you have more than one DC in your domain?

    When you run an ipconfig /all with a .45 workstation, how does this compare to a .44 workstation? I suspect there may be a difference.

  9. #9

    Join Date
    Feb 2007
    Posts
    313
    Thank Post
    93
    Thanked 25 Times in 22 Posts
    Rep Power
    22
    I would get your ISP to investigate. It sounds like a routing issue to me.

    If your 45 range goes through the gateway then all of your clients on the 45 range are accessing your servers through the tcp port, which I guess is capped at 32MB.
    Last edited by Gardinho; 16th November 2012 at 01:08 PM.

  10. #10

    Join Date
    Oct 2005
    Posts
    821
    Thank Post
    51
    Thanked 110 Times in 100 Posts
    Rep Power
    63
    Sounds like a DNS issue to me rather than a routing issue.

    If the trace route using the server's IP address is fine from a .45.x client but the trace route using the server's name isn't ok - then I'd suspect that the name isn't resolving to the correct ip address.

    If you try and ping the server by name - what IP address does it resolve to?

  11. #11

    Join Date
    Feb 2007
    Posts
    313
    Thank Post
    93
    Thanked 25 Times in 22 Posts
    Rep Power
    22
    If the client is going out to the internet first through the default gateway then it won't be able to resolve the DNS name on the way back in.

  12. #12

    Join Date
    Mar 2010
    Location
    Gloucestershire
    Posts
    148
    Thank Post
    20
    Thanked 3 Times in 3 Posts
    Rep Power
    9
    Hi Pantscat,
    If i ping the server name from a .45.x machine it tries to ping a 192.x number and times out, I am looking through DNS now to try to find where that number came from.

  13. #13

    Join Date
    Mar 2010
    Location
    Gloucestershire
    Posts
    148
    Thank Post
    20
    Thanked 3 Times in 3 Posts
    Rep Power
    9
    Looking through DNS I have noticed that the server has 2 ip addresses registered to it in the Name Servers tab. 192.x.x and x.x.44.1.

  14. #14

    Join Date
    Mar 2011
    Location
    Bournemouth
    Posts
    280
    Thank Post
    16
    Thanked 74 Times in 64 Posts
    Rep Power
    21
    can you ping both 44 and 45 addresses from your dns server? Is the dns settings in dhcp correct?

  15. #15

    Join Date
    Oct 2005
    Posts
    821
    Thank Post
    51
    Thanked 110 Times in 100 Posts
    Rep Power
    63
    @sadams1980 - there's your problem - because the DNS server has got two NICs both IP addresses will resolve the server name.

    Is the server supposed to have two NICs?

    In the DNS config you can choose which IP addresses the server will listen on.

  16. Thanks to pantscat from:

    sadams1980 (16th November 2012)

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Very slow AD login on OS X Lion
    By netadmin in forum Mac
    Replies: 6
    Last Post: 27th October 2011, 03:08 PM
  2. Changing IP ranges but keeping server on both?
    By Halfmad in forum Wireless Networks
    Replies: 4
    Last Post: 5th April 2009, 07:27 PM
  3. IP ranges on switches, how do you do it?
    By Kyle in forum Wireless Networks
    Replies: 11
    Last Post: 29th September 2008, 08:17 PM
  4. Replies: 9
    Last Post: 12th August 2007, 01:35 PM
  5. Login very slow
    By localzuk in forum Windows
    Replies: 7
    Last Post: 23rd April 2007, 03:09 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •