Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Can't connect via connector, can't access via Console, CAN access shared folders via explorer. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hey all,

    Having a few headaches here trying to get my WHS up and running.  Here's some specs:

    WHS:
    WHS updated to power pack 2
    Asus M3A78-EM/CM mobo (drivers up to date, LAN drivers up to date directly from Realtek website)
    AMD Athlon 64 x2 5050e
    3x1.5tb Seagate barracuda HD's (updated to newest firmware)

    Connector:
    HP DV9500t Notebook running Vista (up to date)

    Router:
    Belkin F5D7231-4, firmware up to date. UPnP enabled.


    So after installing everything and running my connector, I'm not able to connect to my server via the the connector at all.  When I try logging on to the Console, i get a message telling me i can't log on, and that I should restart my WHS box. 
    However, I am able to occassionally access my WHS shared folders via Windows explorer on my connector notebook, albeit not through the connector software.

    Here are the error messages i get when I run the Connector Troubleshooter:
    • Cannot connect to the server backup
    • Cannot Connect to the server transport
    • IP address mismatch between discovery and name resolution
    • Cannot connect to the server internal website (password hint page)
    • Cannot connect to the server secure internal website
    • Cannot connect to the server secure internal website (simple authenticated page)
    • Cannot connect to the server internal website (ASPX page)
    • Cannot connect to the server internal web services
    • Cannot connect to the server internal secure web services
    • cannot connect to the server internal website (simple page)
    • name resolution failed
    I've also run the troubleshooter in advanced mode, but I'm not sure how to post the logs here.

    I've tried:
    • Opening all the ports suggested by the troubleshooter help articles (even though UPnP is enabled on my router and should handle the port forwarding, no?)
    • Reinstalling WHS via the boot cd
    • "Try Join Server Again" button in the Advanced Troubleshooter
    • Changing LAN cables
    • Restarting my router
    • Installing the Connector from the files on my updated WHS box rather than from the Connector installer CD

    I really want to get my server up and running, and any advice would be greatly appreciated.  Thanks in advance for any help.  Please let me know if you need any additional information from me, and instructions on how to find/post that information.

    Wednesday, May 20, 2009 7:22 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I think i might have found the problem...

    There was an obscure setting in my router under LAN settings  called "Local Domain Name".  It was set to "belkin" by default, and I didn't think much of it...However when i changed it from "belkin" to completely blank, and applied the settings, everything seemed to click into place.  I ran the connector troubleshooter and all my previous errors went away.

    It seems a rather peculiar and obscure default setting of the router that caused me much grief.  Thanks to Brubber and everyone else for their help.

    For more info on the peculiar default settings of this router, there's a lengthy article/review here:
    http://www.epinions.com/review/Belkin_802_11g_Wireless_Router_587009_4/content_404449431172
    • Marked as answer by PATSCRU Wednesday, June 10, 2009 10:44 AM
    Wednesday, June 10, 2009 10:44 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Could be a DNS issue. I guess the clients get their IP address by DHCP from the router. To check on client go to Control Panel, Network Connections. Right click LAN connection (or wireless if you're using that to connect to the network), select Properties. Then in the General Tab of the properties Window select TCP/IP, click Properties. IP address and DNS server address should both be set to automatic.

    If not you can ADD a DNS server address using the advanced button. The DNS server address to add should be identical to the default gateway in the TCP/IP properties window

    If both are set to automatic the best fix for this would be to get into your router settings software, then go to DHCP settings, set primary DNS server address to the routers IP address (=default gateway in the TCP/IP properties screen)

    Also please note, Connector software should best be installed from http://yourservername:55000 (replace yourservername with the name you assigned to your homeserver)
    Wednesday, May 20, 2009 7:52 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the input brubber, looks like you isolated the problem.
    Both my IP address and DNS server addresses were set to automatic on my client in both ipv4 and ipv6, so i went into my router settings and checked my DNS server.  My router was set to get DNS address automatically from ISP.  I changed it to manual, and set my dns server to 192.168.2.1.  This seems to have fixed my issue; I was able to finally connect my connector to my server, and the troubleshooter found no issues. 

    However, while my WHS issues were fixed, my internet access was completely cut off  when i set my DNS server to 192.168.2.1.  Is there a way to resolve the DNS issue on my home network while still maintaining internet access?

    My ISP is Time Warner Cable if that helps.

    Thanks
    Wednesday, May 20, 2009 4:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Would I have to have my own DNS server for WHS to work correctly?  Right now my router gets DNS addresses automatically from my isp.  Is this a problem for WHS?
    Thursday, May 21, 2009 7:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Would I have to have my own DNS server for WHS to work correctly?  Right now my router gets DNS addresses automatically from my isp.  Is this a problem for WHS?

    I think it has to do with your router.  I have a Linksys router and all of my computers in my LAN function properly (both internally and externally) and I use the DNS servers provided by my ISP as well.
    Saturday, May 23, 2009 7:37 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for the input brubber, looks like you isolated the problem.
    Both my IP address and DNS server addresses were set to automatic on my client in both ipv4 and ipv6, so i went into my router settings and checked my DNS server.  My router was set to get DNS address automatically from ISP.  I changed it to manual, and set my dns server to 192.168.2.1.  This seems to have fixed my issue; I was able to finally connect my connector to my server, and the troubleshooter found no issues. 

    However, while my WHS issues were fixed, my internet access was completely cut off  when i set my DNS server to 192.168.2.1.  Is there a way to resolve the DNS issue on my home network while still maintaining internet access?

    My ISP is Time Warner Cable if that helps.

    Thanks

    You made the change in the wrong place, you router should get the DNS server addresses from your ISP, so please undo this change. Then in your router find DHCP server settings and set the primary DNS server address to your routers gateway address. Sorry I didn't reply any sooner, short holiday.
    Monday, May 25, 2009 7:37 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I think everything's good according to Brubber's suggestions, and I've attached images of my router settings just so that can be verified:

    http://img188.imageshack.us/img188/4946/adsf.png
    http://img13.imageshack.us/img13/4273/sdfyjl.png

    Still having the same problem, can't login via console, but occassionally, backups will start on my client laptop, and i can browse and modify my shared folders in Explorer on my client laptop as well.  Thanks for your help so far.
    Wednesday, June 10, 2009 10:10 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I think i might have found the problem...

    There was an obscure setting in my router under LAN settings  called "Local Domain Name".  It was set to "belkin" by default, and I didn't think much of it...However when i changed it from "belkin" to completely blank, and applied the settings, everything seemed to click into place.  I ran the connector troubleshooter and all my previous errors went away.

    It seems a rather peculiar and obscure default setting of the router that caused me much grief.  Thanks to Brubber and everyone else for their help.

    For more info on the peculiar default settings of this router, there's a lengthy article/review here:
    http://www.epinions.com/review/Belkin_802_11g_Wireless_Router_587009_4/content_404449431172
    • Marked as answer by PATSCRU Wednesday, June 10, 2009 10:44 AM
    Wednesday, June 10, 2009 10:44 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for posting your solution!

    EDIT: I must admit I'm a bit surprised by the solution you found. I wouldn't expect this setting to be relevant. Perhaps applying the settings also applied some settings you changed but didn't apply previously. I do wonder what happens if you change the "Local Domain Name" back to it's previous value.
    Wednesday, June 10, 2009 11:13 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for posting your solution!

    EDIT: I must admit I'm a bit surprised by the solution you found. I wouldn't expect this setting to be relevant. Perhaps applying the settings also applied some settings you changed but didn't apply previously. I do wonder what happens if you change the "Local Domain Name" back to it's previous value.

    I am not really surprised after seeing so many times similar reasons.
    Thats kind of a plague, which creates DNS suffixes and/or DNS Search suffixes in DHCP and causing the clients to search the home server in the Internet instead of the local network, if name resolution goes strictly via DNS.

    Best greetings from Germany
    Olaf
    Wednesday, June 10, 2009 1:40 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yea that one tiny setting caused such a headache for me, I feel that anyone else trying to run WHS with that router might give up (it took me about a month of tinkering to accidentally stumble on that setting). I wonder why the Microsoft site lists that particular router as being completely compatible with WHS. It'd be helpful to many if they listed this issue there.
    • Proposed as answer by SamC1931 Thursday, June 18, 2009 1:43 PM
    Wednesday, June 10, 2009 10:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

     
    User name:   
    Password:   
    Service Name (Optional):   
     Connect on Demand:Max Idle Time    minutes
     Keep Alive: Redial Period    seconds
    Host Name:   
    Domain Name:   
    MTU:        Size:  
    IP Address:    .  .  . 
    Subnet Mask:   
    URL Address:   
    Yes, Thanks I removed the Host Name and Domain Name, repowered modem, router, and computers and was able to use the WHS console again.  I reentered the T-Online and Speedport_200 and was unable to access WHS with the console. Removed them again and all OK  I am using a Linksys WRT600N router here in Germany.  I spent a week on this ... Thanks again ...Sam
    Thursday, June 18, 2009 1:55 PM