Jump to content

Welcome to We Got Served Forums
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
Photo

Windows7 Home Cannot Find Whs

- - - - -

  • Please log in to reply
4 replies to this topic

#1
mapleshade

mapleshade

    Newbie

  • Members
  • Pip
  • 9 posts
I have a WHS "SERVER" PP3 on my network with multiple XP computers and a Win7 Pro x64 computer connected to it. I have been running Hamachi Server and Analog X Proxy Server on the WHS which allows a connection from my XP laptop while out of town.

I recently got a laptop with Win7 Home x64 and cannot get the WHS connector to find my server. I can ping "server", the server shows up in the network and I have access to my shares, I can go to http://server:55000 and https://server:56000. I tried running IE9 as admin and adding a certificate for https://server:56000, but it still shows "there is a problem with this website's security certificate". I turned off the Analog X proxy and disabled my Hamachi connection. I do not have UPnP enabled on my router, the http, https, and rdp ports are manually forwarded. I have tried running the WHS connector from http://server:55000 and it can't find my server. Attached is the log from running connector troubleshooter -a. I would appreciate any help getting these errors corrected as I don't know how to solve them. I would also like to not have UPnP enabled. It's working fine with my other clients, so I don't see why I can't make the router configurations manually.

Thanks
Attached File  connector troubleshooter.txt   107.76KB   4 downloads


Upgrade to a WGS Supporter Account to remove this ad.

#2
Garry

Garry

    Advanced Member

  • Members
  • PipPipPip
  • 777 posts
  • Gender:Male
Workgroup name is the same?

#3
mapleshade

mapleshade

    Newbie

  • Members
  • Pip
  • 9 posts

Workgroup name is the same?

Workgroup is the same.

I realized that the troubleshooter was still picking up my Hamachi IP on the server. I ran it again and it's gone. Still have the other errors. I'll post a new log when I have a chance.

#4
mapleshade

mapleshade

    Newbie

  • Members
  • Pip
  • 9 posts
I disabled the firewall on both the client and the server. I also turned on UPnP in my router (DLink DIR-655), although it didn't seem to help. Both computers are wired to the router. Chrome is my default browser, I also have IE9 installed. I get invalid certificate warnings whenever I vist https://server:56000 on either browser, and also when I use RDP to control the server. At least we're on the same subnet now Posted Image. Attached is the latest log...

Attached Files



#5
mapleshade

mapleshade

    Newbie

  • Members
  • Pip
  • 9 posts
Success!

After reading through the logs a dozen or so times, checking ipconfig on both machines, and reading about DNS and netBIOS, I came to some realizations. My new computer was checking my router for DNS addresses by default, which were populated as the ones from my ISP. I was using a static IP on the server and had OpenDNS configured on that machine. I changed the server's DNS address to my gateway address (router) and changed the router's DNS addresses to the fastest OpenDNS addresses available (using GRC's DNS Benchmark). I now had an issue with OpenDNS not resolving local addresses. I added my server's IP and name to the client's hosts file and rebooted. I then saved WHS connector and ran it as Administrator, viola...installation.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users


Upgrade to a WGS Supporter Account to remove this ad.