Windows .net server 2003 question

ok here it is.

I have recieved a copy of Windows .Net Server 2003 (from microsoft, as part of the advanced beta team). I am setting it up as a workgroup, NOT A DOMAIN, and am trying to use a secondary laptop to access a shared drive on it.

The secondary laptop is running on Windows XP Home.(which is why im not using domins, but a workgroup).

Ive tried mapped drives, vpn's, remote desptops, and nothing seems to work. I can see the drives, even log in, but then i get failures or lock ups.

Im assumoing this is related to win XP Home, but there has to be a work wround, as i can get into other work groups, just not domains.

Ideas??

 

XP-home uses "simple file sharing" by default. Have you tried turning that off? I know it is supposed to just make shares on the XP-home system easier to get to but I'm not completely convinced there aren't other effects.

Also if you used the networking wizard to set up XP-home, you will have activated the firewall. Could be an issue there.

From what I read, earlier .Net versions were supposed to be happy enough playing in a workgroup/peer environment.

But my real suggestion if you intend to do any serious work with your XP box is to upgrade to XP-Pro.

 

ok

I tried all your points prior to posting, to no avail.

and I agree, if I were to be using this for anything else other then beta testing, I would be doing just that(upgrading that is).

But im not, I'm beta testing only, so my desire is to fix the issue, not obviate the problem.

Please don't take that as an attack, its not, I do agree, but Windows goes out of its way sometimies to make it difficult, and I hate giving in.

Ideas??

 

Callanan - I certainly didn't take your response as anything other than your setup/situation and the fact that my WAGs didn't work. Wish they had but they were strictly guesses. My .Net experience is around zero.

And I do understand about doing the Beta stuff and hating to let a blasted OS not behave like it should.

The only other thing I can add is I still think it would be good to try with XP-pro in your present enviornment just to see if it works. If yes, then you know you are dealing with an OS issue with XP-home. If not, then something else is busted. Should help narrow down the field some for you.

I'm assuming from all this that Microsoft expects XP-home to work with your environment.

I noticed from a FAQ Here that at least one University which has the thing in Beta has noticed similar problems to yours.

And This site might be worth a look. Appears to be a Beta .Net site with a forum.