Jump to content
RESET Forums (homeservershow.com)

WS2012E Connector / Possible DNS issue


Greg Welch
 Share

Recommended Posts

To make a long story short. lol

 

Installed my Windows 8 Pro client to server using connector within LAN. no problems

also tried to connect to server using connector from https ://xxxxx.remoteaccess.com/connect

will work, of course told me need to remove current connector.

 

Installed Direct Connect / Remote Access, along with VPN support. and completed Anywhere Access using windows domain https: //xxxxx.remotewebaccess.com no problems

 

tried installing my wife's Windows 8 Pro client using connector in LAN, after choosing download software on connector page I get popup "cannot locate or identify your server" tried Domain name and IP of server,

no luck

 

tried installing using https: //xxxxx.remoteaccess.com/connect

Will find server and gives me the following popups

"getting started"

".NET REQ 4.5 "

"Network Username and Password" (Her username is already on server as User)

"connect to xxxxx.remotewebaccess" popup asking for user, pass and domain

 

after entering the credentials says server is not available

 

 

any ideas guys, gals

Link to comment
Share on other sites

  • Replies 31
  • Created
  • Last Reply

Top Posters In This Topic

  • diehard

    3

  • Greg Welch

    10

  • jmwills

    8

  • ikon

    8

Top Posters In This Topic

Were these clients ever connected to the domain at any time previously? What is the DNS server? The router or the 2012 server?

Link to comment
Share on other sites

yes, but were removed , DNS server is router

 

haven't touched .NET

 

thinking possible cert issue?

 

 

Having to retrace my steps after installing Direct Access

Link to comment
Share on other sites

Not sure, but it seems that reinstalling .NET has fixed a lot of issues in the past, so wondering if it might help here too.

 

ya but I get the same "cant find server " from 2 machines, so im thinking its a server side issue

 

Also I can ping it, see it in the network folder, (no shares other that folder redirection)

Link to comment
Share on other sites

Yeah. If the install won't work using the IP, there's an issue alright. Is it possible for you to stand up another server, even temporarily, maybe in a VM, and see if you can join the 2 clients to it?

Link to comment
Share on other sites

Yeah. If the install won't work using the IP, there's an issue alright. Is it possible for you to stand up another server, even temporarily, maybe in a VM, and see if you can join the 2 clients to it?

 

Yes that I can confirm works, its only after adding Direct Access that I loose the connector ability

 

http://channel9.msdn.com/posts/Direct-Access-in-Windows-Server-2012-demo-and-interview

Link to comment
Share on other sites

Reset the computer objects in AD. Right Click and select reset.

 

Remove the clients from the Domain (add to workgroup) and then rejoin to the domain.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share


×
×
  • Create New...