none
DNS Issues?

    Question

  • I apologize if this this has been posted already; I have been up and down the internet for help and I can't seem to find it.

    My Set Up:

    I run an Apache web server (ver. 2.2) I have three laptops, one PC (my main PC), and a server (which hosts the web server). Laptops and main PC run Windows 7 Enterprise, Server runs Windows Server 2003.

    All my workstations live on a domain with DNS provided by the same server.

    I have a dynamic DNS resolving my external IP address for my router.

    I have never had any issues up until a few weeks ago when this all started.

    My Issue:

    My three laptops have no issues connecting and navigating throughout my web server, however my main PC and the server itself loads the pages really slow. Actually to be more accurate, when I navigate to a page or even load the home page, there is about a 30 second to a minute where the browser just sits and thinks before it actually begins to load anything.

    This seems to only be when I browse my web server because doing any other kind of internet browsing isn't affected.

    What I have done thus far:

    Tested different web browsers
    Rebooted into a Linux Live CD to ensure it wasn't a NIC failure (web pages loaded fine)
    Tested from a virtual machine both Windows and Linux from the main PC (web pages didn't load find)
    I had different users from different ISPs navigate my site(no issues)
    Tested IIS web server to ensure it wasn't Apache (IIS has the same issue)

    What I think it might be:

    I am leaning toward the issue being something to do with DNS resolution but I'm not 100% sure on this yet or what steps I can take to check.


    Something interesting to think about:

    From the server, if in the browser I type in http://localhost/ the web pages work great and they are fast; and they should be because I’m getting them directly from itself. However, if I use the IP address of the machine (not the loopback IP), it goes back to being sluggish.



    I hope that someone can help me with this. I probably didn't provide enough information here because mainly I don't know what information I should provide yet.

    Friday, June 28, 2013 5:37 PM

Answers

  • Ok, its may be the result of the virtualbox install and something left over causes this. I'd clean install it if you can.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 11:19 PM

All replies

  • Please post an unedited ipconfig /all of server and problem workstation.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Friday, June 28, 2013 9:59 PM
  • Problem PC

    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    
    C:\Users\jbliske.ZEDDSHOUSE>ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : W-SysAdm
       Primary Dns Suffix  . . . . . . . : zeddshouse.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : zeddshouse.local
    
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 90-E6-BA-31-08-40
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.110(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.254
       DNS Servers . . . . . . . . . . . : 192.168.1.100
                                           208.67.222.222
                                           208.67.220.220
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter VirtualBox Host-Only Network:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
       Physical Address. . . . . . . . . : 08-00-27-00-0C-1A
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::6d57:7b5c:ae91:9877%34(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 570949671
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-C1-5D-65-90-E6-BA-31-08-40
    
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter isatap.{85759712-1136-4C53-8029-0B14D5723F65}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter Local Area Connection* 11:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{5E9A6359-9AED-4403-89D7-31C86E835085}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Server

    Microsoft Windows [Version 5.2.3790]
    (C) Copyright 1985-2003 Microsoft Corp.
    
    C:\Documents and Settings\Administrator>ipconfig /all
    
    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : s-510fs1
       Primary Dns Suffix  . . . . . . . : zeddshouse.local
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : Yes
       DNS Suffix Search List. . . . . . : zeddshouse.local
    
    Ethernet adapter Local Area Connection(Main NIC):
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit Ether
    net NIC
       Physical Address. . . . . . . . . : 00-14-D1-15-47-B9
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.1.100
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.254
       DNS Servers . . . . . . . . . . . : 127.0.0.1
                                           208.67.222.222
                                           208.67.220.220
    
    Ethernet adapter VirtualBox Host-Only Network:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
       Physical Address. . . . . . . . . : 08-00-27-00-48-57
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.56.1
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
    
    C:\Documents and Settings\Administrator>

    Friday, June 28, 2013 10:08 PM
  • Change server DNS primary to 192.168.1.100 and secondary to 127.0.0.1 and remove public DNS addresses from both client and server. Always put public DNS addresses as forwarders on your local DNS server. If you installed a DC/DNS on virtual box host that is multi-homed there will be no end to problems.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Friday, June 28, 2013 10:18 PM
  • Thank you for your quick responses back and thank you for taking the time to help me out.

    I did as you said and still no change.  The public DNS IPs were already configured as forwarders.

    I restarted the DNS service; flushed DNS on both machines; cleared cache on both machines.


    Friday, June 28, 2013 10:33 PM
  • Please repost unedited ipconfig /all of both. Also you can't multi-home the DC/DNS server and get this to work right. I'd stand up another guest for this.

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.


    Friday, June 28, 2013 11:17 PM
  • You suggest that I separate the DNS and the DC.  I don't have another physical machine to do that with and I'm pretty certain the server won't be able to run a virtual machine very well.

    What I don't understand is why do all my laptops work just fine but my main PC and server does not and it's just with when browsing my web server.

    Main PC

    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : W-SysAdm
       Primary Dns Suffix  . . . . . . . : zeddshouse.local
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : zeddshouse.local
    
    Ethernet adapter Local Area Connection:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
       Physical Address. . . . . . . . . : 90-E6-BA-31-08-40
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.110(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.254
       DNS Servers . . . . . . . . . . . : 192.168.1.100
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Ethernet adapter VirtualBox Host-Only Network:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
       Physical Address. . . . . . . . . : 08-00-27-00-0C-1A
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::6d57:7b5c:ae91:9877%34(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
       DHCPv6 IAID . . . . . . . . . . . : 570949671
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-C1-5D-65-90-E6-BA-31-08-40
    
       DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                           fec0:0:0:ffff::2%1
                                           fec0:0:0:ffff::3%1
       NetBIOS over Tcpip. . . . . . . . : Enabled
    
    Tunnel adapter isatap.{85759712-1136-4C53-8029-0B14D5723F65}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter Local Area Connection* 11:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    
    Tunnel adapter isatap.{5E9A6359-9AED-4403-89D7-31C86E835085}:
    
       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
    

    Server

    Windows IP Configuration
    
       Host Name . . . . . . . . . . . . : s-510fs1
       Primary Dns Suffix  . . . . . . . : zeddshouse.local
       Node Type . . . . . . . . . . . . : Broadcast
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : Yes
       DNS Suffix Search List. . . . . . : zeddshouse.local
    
    Ethernet adapter Local Area Connection(Main NIC):
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Realtek RTL8169/8110 Family Gigabit Ether
    net NIC
       Physical Address. . . . . . . . . : 00-14-D1-15-47-B9
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.1.100
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.254
       DNS Servers . . . . . . . . . . . : 192.168.1.100
                                           127.0.0.1
    
    Ethernet adapter VirtualBox Host-Only Network:
    
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
       Physical Address. . . . . . . . . : 08-00-27-00-48-57
       DHCP Enabled. . . . . . . . . . . : No
       IP Address. . . . . . . . . . . . : 192.168.56.1
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . :
    

    Friday, June 28, 2013 11:33 PM
  • I was suggesting to not have the host also the DC/DNS as its multi-homed. I now see the main is also multi-homed. Try on both Control Panel|Network|Connection|Properties|IPV4|Properties|Advanced|DNS and uncheck register this connection's address in DNS on the unwanted adapters, then ipconfig /flushdns on both, delete the host A dns records on server and possibly reboot them both.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.


    Friday, June 28, 2013 11:48 PM
  • My mistake, I misunderstood your suggestion.  Just so it's cleared up, the main PC is one physical machine and the server is a separate physical machine.  I'm not running any virtual machines here.  I thought you meant that I shouldn't have the DC and the DNS on the same server.

    I have done as you suggested and rebooted still no joy.
    Saturday, June 29, 2013 12:19 AM
  • Someone has installed virtualbox on both. Disable those adapters if they're not being used, then ipconfig /flushdns on both and reboot them, then wait patiently for DNS to startup (like 5 minutes or so)

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 12:27 AM
  • You are right, I did have Virtual Box installed on both.  The VBox on the server I don't use so I did disable that adapter; I'll probably uninstall it from the server.

    On my PC I also have it installed and I do use it but none of my virtual machines are part of the domain.  However, for testing purposes I did disable that adapter as well.

    I am still experiencing the same issue on both machines.  I gave the server a good bit of time to start up before I even started my PC.

    Saturday, June 29, 2013 12:52 AM
  • Lets run cmd.exe then dcdiag /dnsall >C:\dnsall.txt and post output from text file.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 1:13 AM

  • Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests
       
       Testing server: Default-First-Site-Name\S-510FS1
          Starting test: Connectivity
             ......................... S-510FS1 passed test Connectivity

    Doing primary tests
       
       Testing server: Default-First-Site-Name\S-510FS1
          Starting test: Replications
             ......................... S-510FS1 passed test Replications
          Starting test: NCSecDesc
             ......................... S-510FS1 passed test NCSecDesc
          Starting test: NetLogons
             ......................... S-510FS1 passed test NetLogons
          Starting test: Advertising
             ......................... S-510FS1 passed test Advertising
          Starting test: KnowsOfRoleHolders
             ......................... S-510FS1 passed test KnowsOfRoleHolders
          Starting test: RidManager
             ......................... S-510FS1 passed test RidManager
          Starting test: MachineAccount
             ......................... S-510FS1 passed test MachineAccount
          Starting test: Services
             ......................... S-510FS1 passed test Services
          Starting test: ObjectsReplicated
             ......................... S-510FS1 passed test ObjectsReplicated
          Starting test: frssysvol
             ......................... S-510FS1 passed test frssysvol
          Starting test: frsevent
             ......................... S-510FS1 passed test frsevent
          Starting test: kccevent
             ......................... S-510FS1 passed test kccevent
          Starting test: systemlog
             ......................... S-510FS1 passed test systemlog
          Starting test: VerifyReferences
             ......................... S-510FS1 passed test VerifyReferences
       
       Running partition tests on : ForestDnsZones
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
       
       Running partition tests on : DomainDnsZones
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
       
       Running partition tests on : Schema
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
       
       Running partition tests on : Configuration
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
       
       Running partition tests on : zeddshouse
          Starting test: CrossRefValidation
             ......................... zeddshouse passed test CrossRefValidation
          Starting test: CheckSDRefDom
             ......................... zeddshouse passed test CheckSDRefDom
       
       Running enterprise tests on : zeddshouse.local
          Starting test: Intersite
             ......................... zeddshouse.local passed test Intersite
          Starting test: FsmoCheck
             ......................... zeddshouse.local passed test FsmoCheck

    Saturday, June 29, 2013 2:19 AM
  • Looks Ok. Try also;

    DCDIAG /TEST:DNS /DnsForwarders >C:\dcdiag.txt

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 2:44 AM

  • Domain Controller Diagnosis

    Performing initial setup:
       Done gathering initial info.

    Doing initial required tests
       
       Testing server: Default-First-Site-Name\S-510FS1
          Starting test: Connectivity
             ......................... S-510FS1 passed test Connectivity

    Doing primary tests
       
       Testing server: Default-First-Site-Name\S-510FS1
    Saturday, June 29, 2013 2:49 AM
  • From client you should get server name and address when you run from cmd.exe

    nslookup

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 2:56 AM
  • Ok I ran this from the client and here is the output.  What I find interesting is that default server is unknown.  Also, should primary name server be = localhost?  Even though it is, shouldn't that value be the actual server name?

    Saturday, June 29, 2013 3:07 AM
  • Interesting that the image didn't come through on the first post.  Sorry about that.

    Saturday, June 29, 2013 3:16 AM
  • I'd work through some of this.

    http://technet.microsoft.com/en-us/library/cc959303.aspx

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 3:21 AM
  • If you browse by address is it then fast?

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 3:28 AM
  • From the client:

    If I browse either from IP address or web address, I get the same effect.  20-30 seconds of thinking before it begins loading.

    From the server:

    If I browse by IP address or web address, same effect as above.  However, I enter in 'localhost' in the browser, it loads fast and all links work great.

    I have checked on both systems IE and Firefox so I don't believe it would be a browser issue.

    Saturday, June 29, 2013 3:33 AM
  • When you browse by addy are you testing with the public or private address?

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 3:38 AM
  • I tried both and I get the same effect either way.  I would think that using the private IP it would be fast since it never has to leave my router.
    Saturday, June 29, 2013 3:41 AM
  • I agree, and also takes DNS out of it. Sounding more like a router issue.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 3:55 AM
  • Hello,

    remove the 208.67.222.222 and 208.67.220.220 from ALL domain machines NICs and run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service on the DC and reboot the client machines.

    Then check again and post also again an unedited ipconfig /all from the DC/DNS servers and the client.

    Also assure the at NONE of the Virtual box adapters is registered in the DNS zones from the DNS server. This result in multihoming for the DC, which is NOT recommended and result in multiple network problems. DCs MUST have unique DNS records to work correct.


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Saturday, June 29, 2013 6:04 PM
  • Hello,

    remove the 208.67.222.222 and 208.67.220.220 from ALL domain machines NICs and run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service on the DC and reboot the client machines.

    Then check again and post also again an unedited ipconfig /all from the DC/DNS servers and the client.

    Also assure the at NONE of the Virtual box adapters is registered in the DNS zones from the DNS server. This result in multihoming for the DC, which is NOT recommended and result in multiple network problems. DCs MUST have unique DNS records to work correct.


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    I had already removed the public DNS servers from all NICs.  They are however set up as forwarders on my DNS server.(screenshot above)

    I did reboot the server and clients and also ran the commands you listed and restarted the netlogon service.  One thing seem to change; on the server only, I can now enter in the server IP address into the browser and the web site seems to load great.  However, I still get use the web address.  The client has no change.

    Server:

    Client

    Saturday, June 29, 2013 7:43 PM
  • Why is my PC not showing up in DNS?  W-SysAdm should be listed and its not.

    Saturday, June 29, 2013 7:48 PM
  • Hello,

    on the DC please remove or disable RRAS and also disable the WINS proxy:

    IP Routing Enabled. . . . . . . . : Yes
    WINS
    Proxy Enabled. . . . . . . . : Yes

    Are you able to ping the DC from the client with ip address, machine name and FQDN?


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Saturday, June 29, 2013 8:32 PM
  • Hello,

    on the DC please remove or disable RRAS and also disable the WINS proxy:

    IP Routing Enabled. . . . . . . . : Yes
    WINS
    Proxy Enabled. . . . . . . . : Yes

    Are you able to ping the DC from the client with ip address, machine name and FQDN?


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    I might need help finding where to disable those two options.

    I am able to ping all three ways from the client machine.

    Saturday, June 29, 2013 8:46 PM
  • Ok I think I found where to disable RRAS but the option to disable it is greyed out.  I ran RRAS as administrator so I'm not sure why this option is greyed out.

    Saturday, June 29, 2013 8:52 PM
    • Start Routing and Remote Access in Administrative Tools.
    • Right-click the server name, and then click Properties.
    • On the IP tab, click to clear the Enable IP Routing check box.

    http://support.microsoft.com/kb/319848

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 8:55 PM
    • Start Routing and Remote Access in Administrative Tools.
    • Right-click the server name, and then click Properties.
    • On the IP tab, click to clear the Enable IP Routing check box.

    http://support.microsoft.com/kb/319848

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    When I right click properties on the server, I get an message that says it hasn't been set up.

    Saturday, June 29, 2013 8:56 PM
  • Probably a remnant of virtualbox. You can reverse the setting with this article.

    http://support.microsoft.com/kb/323339

    Also

    http://support.microsoft.com/kb/319848

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 9:04 PM
  • RRAS is already disabled in the regedit, but I also just deleted the RRAS server because I couldn't seem to disable it and there was a green up arrow on it so I don't know what was going on there.

    I have disabled WINS as well but ipconfig /all shows only WINS Proxy disabled but RRAS is still set to yes.  I also uninstalled Virutal Box.

    Saturday, June 29, 2013 9:29 PM
  • Have you rebooted? Is your only test from Main PC? Might try another. Seems to me still a routing issue of some sort.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 9:40 PM
  • I have rebooted and all my other workstations work fine.  I have been checking them along with my main PC as we did things.

    As far as a routing issue goes, there are not many settings on my router that could do something like this; at least none that I can see.  I do have some port forwarding going on but some of the systems that I'm running on the server and on my main PC, but all of them are correct and functioning.  I use a dynamic DNS to resolve my external IP address but I can't see how that would cause my issue.

    Saturday, June 29, 2013 10:07 PM
  • I thought you said yesterday that browsing the web by private address from main was slow. Has this changed? How about other machines?

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 10:10 PM
  • No, browsing from the main PC is still slow using private IP or web address.  The only thing that changed was that on the server I was able to use the private IP and the web pages were loading fast; but only on the server did this change.
    Saturday, June 29, 2013 10:13 PM
  • What was done to change that?

     

     

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 10:22 PM
  • I was instructed to do the following:

    "remove the 208.67.222.222 and 208.67.220.220 from ALL domain machines NICs and run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service on the DC and reboot the client machines.

    Then check again and post also again an unedited ipconfig /all from the DC/DNS servers and the client.

    Also assure the at NONE of the Virtual box adapters is registered in the DNS zones from the DNS server. This result in multihoming for the DC, which is NOT recommended and result in multiple network problems. DCs MUST have unique DNS records to work correct."

    Once I rebooted I tested all of my workstations again and the server.  I noticed that the server seemed to return the webpages pretty quick when using private IP address.  I know it wasn't doing that before.

    I also removed a couple of A record entries in DNS that were lingering from my Virtual Box.

    Saturday, June 29, 2013 10:27 PM
  • Ok, well it was long before that as I had you remove them earlier in this thread. Since it has this behavior using address only it is not a DNS issue. I think its either a routing remnant of virtualbox or possibly IIS. If you're using IIS you might ask them over here about performance issues.

    http://forums.iis.net/

     (I think I'd consider building up another web server from ground up)

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 10:46 PM
  • I'm using Apache 2.2, but I do have IIS installed for testing purposes but it's disabled as to not conflict with Apache.

    I'll try uninstalling IIS and see if that does anything.

    Saturday, June 29, 2013 10:49 PM
  • Ok, its may be the result of the virtualbox install and something left over causes this. I'd clean install it if you can.

     

     

     


    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Saturday, June 29, 2013 11:19 PM
  • hello dear..

    pls ask ur netwrok team, if there are any access list implemented.. sometimes u need to think a bit out of the box..

    moreover ur server is running in services mode, i dont think it has enough memory for apps :)


    Regards Shah. MCITP, MCMA, MCTS No claims (try at your own risk)

    Sunday, June 30, 2013 12:24 AM
  • I am the team.  This is a personal network and there are no access lists implemented.

    The server has plenty of memory for apps.

    Sunday, June 30, 2013 1:44 AM