Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Can't connect 2 laptops to my Windows Home Server RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I just installed a new Windows Home Server for my church and used a Dell 4600 and 1.5TB of SATA hard drives. All went well for the 1st 6 PC's, but the last 2 devices will not connect to the server. I can see the server, access the remote connection software folder and begin the install process, but then the client cannot find the server, not even "manually". I've installed 3 Home Servers and this is the 1st time I've encountered this. 1 laptop is running Vista and 1 is running WinXP. The LAN is up and running and is stable. Any suggestions? Thanks!

    Tuesday, September 2, 2008 4:09 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Art,

    As it appears your not close to the network, it could be as well while you are there, to run an 'ipconfig /all' from a Command prompt, on both a working Client and a non-working Client.
    There is also the Connector Troubleshooting Document, which could be a worthwhile read before you get back to the Church.

    Colin
    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Thursday, September 4, 2008 6:04 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    BTW, Windows firewall is "off" and I'm logging in as the user (who had admin privileges). I can see the server when browsing the network and I can access the shared (public) folders. The server is up and running fine and i've applied all patches and Power Pack 1. All IP addresses are DHCP. Thanks!

     

    Tuesday, September 2, 2008 4:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Nothing? I've been researching this issue and will try a few things in a week or so, but has anyone else seen this same thing? The 2 laptops wil not connect to the server although they can see the server and download the connector software from the server. Thanks!
    Art Zasadny
    Wednesday, September 3, 2008 3:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Art, what happens when you try to ping the server from one of the affected PCs? By name? By IP address? Have you installed the Windows Home Server toolkit (documentation) on one of the affected PCs and used it to see if it reports any issues? Are there identifiable differences in network connection between the machines that work and those that don't?
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, September 3, 2008 4:30 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Ken,

       Thanks for the advice. I'll try to get more info the next time I work on the laptops at my church. Both laptops have wireless NICs (which I disabled) and they are using the Ethernet to connect to the LAN. Everything about the laptops seems to be OK, but they will not detect the server after loading the connector software. I'll post again here after I do more troubleshooting. Thanks again!

    Art
    Art Zasadny
    Thursday, September 4, 2008 4:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Art,

    As it appears your not close to the network, it could be as well while you are there, to run an 'ipconfig /all' from a Command prompt, on both a working Client and a non-working Client.
    There is also the Connector Troubleshooting Document, which could be a worthwhile read before you get back to the Church.

    Colin
    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
    Thursday, September 4, 2008 6:04 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm having the same problem!  Everything runs great on all of my XP SP3 systems but one.  The old connector software has been uninstalled.  I can ping the WHS by name and IP.  I can access its shares.  I browse to the connector share on the WHS and run setup.  During setup it looks for the WHS and can't find it.

    Now even more interesting.  At this point, after aborting the install, I can no longer see the WHS.  I can't ping it, and I can't see it's shares.  I can still ping other systems on the network by name and see their shares.  If I reboot this client I'm back to the original state and can see the WHS again.

    Help...?!
    Saturday, September 6, 2008 3:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Im having the same issuie HERE... I've been chronicling my journy...
    Thursday, September 11, 2008 5:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I got both of the laptops to connect by manually connecting them to the WHS. I typed in the name of the server during the installation process and then the laptops were able to continue the install and then connect to the server. Backups and shares work perfectly. I'm glad it worked and I hope this helps someone else!
    Art Zasadny
    Thursday, September 25, 2008 6:11 PM