Windows Home Server Beta...

[dave87]

Well, I've been running it for about an hour, and just hit my first hiccup.

Basically:

Just tried to install the Home Server Connect Software on my laptop, and keep hitting unknown network error, though the server is communicating perfectly fine with the server (eg Synergy works, remote folders etc) and it finds the server and prompts for a password. After entering the correct password, it freezes, then pops up the error message.

I don't want to submit a bug report if its me being a numpty that is causing it...

Server - Athlon 2000+/512mb/80gb/WHS Beta.

Laptop - Inspiron 6400, CoreDuo 2ghz, 2gb DDR2, 80gb, Win XP Pro/SP2. Connected via a switch to the WHS.

Any thoughts?

I've tried disabling software firewall (SP2 inbuilt) made no difference. As said above, all other services are running fine....

Dave

[Metier9]

check the event logs on the server

See if its crashing when its trying to connect? e.g. does the server register you have tried to log on or not.

[dave87]

Spike in Network traffic to the server, but nothing listed in the logs...

[Metier9]

Terminal server issue?

[dave87]

It is built on Server 2003, so that could be an issue, will have a little look see

Edit - nope, not as far as I can see. I've just finished re-installing .Net 2.0 again, incase it was an issue with my laptop...

[Metier9]

Installing all the updates would be a start

[dave87]

Heh, according to Windows Update there are no more

I'm just wondering if its a networking issue, though it can't be if everything else works fine?

[Metier9]

Ive had this problem before... it does sound familiar...

what does the error message say? User cant log in or timeout one etc?

[dave87]

This is the error I get:

[Metier9]

That has to be classed as one of the most useful error messages lol

do you have to use this home server connector software? Cant you just remote desktop to it? And set up terminal server on the home server?

[dave87]

RDP'ing to the Server works, but only if I enter the IP, entering 'server' doesn't work (ie like Server 2003 used to, via the name of the server)

The idea of the remote connector software is to make it easy to link client computers with this simplified version of WS2k3, but its done everything but that. It's basically an all in one tool to schedule backups, share folders, allow private user stores etc.

[Metier9]

home server doesnt have DNS?

[dave87]

I'm not sure, I'm not using it as one, that I've left to my router for the time being... Its got a fixed IP, and entering the name used to work on a server 2003 trial I had, the network topology hasn't changed in between times?

[Metier9]

Alot of things seem to point back to the home server... the home server sure is in a beta ^^, what about the beta forums on microsoft, anyone else having these problems?

[dave87]

Not that I've seen, but a lot are running Vista as their main OS. I'm still running XP Pro, admittedly with SP2 and all latest updates, except IE7...

[Metier9]

Home server is a stripped down version of 2003 which is a server version of XP.

Vista's server equiv is not out till this year or next... although it wouldnt surprise me if they used some 'ideas' from vista in the home server.