connect XP home computer to the network

  • Thread starter Thread starter XPhomenetworkprob
  • Start date Start date
X

XPhomenetworkprob

Hi,

I am using a windows 2003 server (standard server) as the main file
server. On this network I have clients using XP professional, XP home,
Mac OSX operating system.

One of the user using XP home is not able to use the file server. User
is also not able to connect to any other client while all the other
clients are able to comfortable interact. I have checked the firewall
settings. Also I am able to ping from the users computer to any other
client and vice versa but some how accessing any shared folder is not
becoming possible.

Can someone please help.

Thanks,

pg
 
Hi,

I am using a windows 2003 server (standard server) as the main file
server. On this network I have clients using XP professional, XP home,
Mac OSX operating system.

One of the user using XP home is not able to use the file server. User
is also not able to connect to any other client while all the other
clients are able to comfortable interact. I have checked the firewall
settings. Also I am able to ping from the users computer to any other
client and vice versa but some how accessing any shared folder is not
becoming possible.

Can someone please help.

Thanks,

pg

Knowing what "is not able" actually includes is the first step here. And
knowing how the LAN is setup (is it a domain or workgroup, what name resolution
is used, etc).
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>
http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html

Why not start with "browstat status" and "ipconfig /all" from the problem
computer, from the server, and from one XP client, so we can diagnose the
problem. Read this article, and linked articles, and follow instructions
precisely (download browstat!):
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
 
A lot would depend on whether this server is setup as a domain controller, or
not. If yes, then use of a domain-user account to authenticate is necessary.
For example:

net use \\server\share /user:domainname\domainaccount

There might also be a problem with the server-side policy requiring the use
of signed communications. This policy was introduced as default on 2003
domain controllers, and it does cause some problems.

Possibly worth giving MyLogon a try here, it would enable your Home
computers to log-on properly. (won't solve no-connection issues of course,
after all it can't do the impossible!)
 
I've been specifically informed that Windows XP Home will not ever see a
doamin controller. Nor will Window Vista Basic (which) I wish I had checked).

I am trying to find out myself, if I can demote the server from a domain
controller and make it a regular PC with multi-tasking remote access.

Lotta secrets outhere. i have much upgradeing and muchhoo$$ to spend
now..Let me know if you hear different.

mark
MSWO
most stupid Widows Operator
 
Mark said:
I've been specifically informed that Windows XP Home will not ever see a
doamin controller. Nor will Window Vista Basic (which) I wish I had checked).

I am trying to find out myself, if I can demote the server from a domain
controller and make it a regular PC with multi-tasking remote access.

Lotta secrets outhere. i have much upgradeing and muchhoo$$ to spend
now..Let me know if you hear different.


You have been "specifically informed" incorrectly. While XP Home cannot
join a domain, it certainly can use domain resources. If you have an XP
Home machine that can't "see" your domain controller, you have something
set up wrong.

Windows XP Home Accessing data on a Domain Server -
http://www.windowsnetworking.com/articles_tutorials/wxphdoms.html

Malke
 
Appreciate your reply I think... lol. Certainly I could have missed
something. But, I wouldn't be able to tell u where. XPHome has firewall
disabled Norton Disabled, belongs to workgroup Office. Server is hpf.tld. If
I hit firewall on the server I get some kind of ntap.sys(warning). Other than
that standard router from ATT.

Whats the difference between connecting and usuing and joining domain?

Can Ping server but server can not ping client(Home)

Should the Server show up someplace in the explorer tree?

If I demote the server from a domain controller to a non domain C. does that
stop remote access to the static IP? Would I still be able to FTP in? I just
want to use a multi application program on the server.. Thats it. For the
life of me I can't see what I have missed.

You guys are very much appreciated in help us.

Mark
 
I should add, that after looking at your page for Home connection. Yhe Server
sees the PC's in the explorer, but gives a permission error and hangs when
selected. The server can not ping either PC, but can ping the router.

The PC's can ping the router!!!!, but they DO NOT see or ping server! In
network places or any other place!

It is as if it didn't exist from the client side.

Workgroups are identical.

Is it because of the "Identical login required?
 
if no Shares are displayed,
then use
"View Workgroup Computers",
it should display the Domain Server.

Niether PC display a workgroup Server.
 
Mark said:
if no Shares are displayed,
then use
"View Workgroup Computers",
it should display the Domain Server.

Niether PC display a workgroup Server.


All your various posts are confusing. It would be better if you had just
made a list of what you've tried using numbers or bullet points. Include
error messages and what your end goal is.

If you have a computer on your network (no matter what its MS OS) and it
is not "seeing" other computers, then it could be:

1. A firewall misconfigured and/or two firewalls running at the same time.
2. Make sure the computers are on the same subnet.

Naturally you will need to have the XP Home user account created on the
server with the identical password. If you will read the information at
the link I gave you (not "my" page), that will walk you through this.

Demoting the server from being PDC will not make any difference if your
networking setup is incorrect. You will just then mess up your domain
thoroughly.

If you are still unable to network your XP Home computer, then go
through this troubleshooter by MVP Hans-Georg Michna OR have a local
professional come on-site to set you up correctly.

http://winhlp.com/wxnet.htm


Malke
 
1st...don't think I don't feel dumb. I have spent many a hour trying to
figure this cr_p out.

Situation.:::


Houston ::

#1 Dell W2k3 server
# 2 -2 dell PC's one with Home, one with Basic Vista.

Was expecting Houston to have a local LAN ,,,,because they are connected to
an ATT modem/router. Configured ok from what I see.. ALL FIREWALLS DISABLED>

PC's (home and vista can ping the server)....

Server can ping router and actually see workgroup!!!!

....BUT thats as far as that goes.

PC' s see nothing... period. Can't see each other , even on the same
workgroup. I realize they can not join a domain. need solve!

2nd.... I, and one other need to Remote in ( which we can)... the server has
DHCP off!!!!

we remote in via MSTSC to the Servers Static IP. ....***.**.**.**.129

FTP for me..OK////..***.129

In Houston, we want to use the very same Quickbooks multi user we used in
Atlanta.. Somehow when we moved the server. it didn't show up on the LAN..
It can Ping the router.

I can ping the server (from Fla. ) But the PC's can't do or see squat.

Enuff info? I understand we look a bit off kilter here.. but we study and
try and ..try to learn., Yet as we try we are made to look a bit dumb..

We have paid for service in Atlanta.

We were willing to pay ATT. They don't get it either. A local LAN..and
Remote/FTP in.

I did get conflicting info about Home and Vista Basic..

Summarry:

Need PC1 (Vista Basic) to see server.
Need PC2 to do the same.

need to remote /FTP in.

Need server to see the PC's..

Am tired an used up... need a laymens reading as to why I am so screwed up.
I can live with,..."you are just basically stupid.".

thanks \
Mark
 
Back
Top