Workgroup 1pro 1Home and lots of trouble

B

BT

Hello all :)

I Posted the following yesterday.
Today things improved in the sense that now the machines can ping each other.
I still cannot see both machines in the neighborhood or in "Microsoft windows Network" I can only see the machine that I am on , like they belong to completely different networks.
All firewalls and similar BS has been removed .
The X-over cable was tested and is OK
The Ethernet adapters did also test ok ( ping self, ping each other and ping loopback).

If I try to map a share though (i.e \\192.168.0.18\sharedc) (since they ping) I get "the path was not found" The home machine has an identical username and password with one of the two users on the pro machine and it is this account that I use on both trying to set it up.

Server and Workstation services are started up automatically and they run on both machines.

What else could be the problem? Is the sledgehammer the only tool that will put an end to this misery??
Ahh how much I miss NT 4!!!

Thanks
Bill T
==============================================================================================
Please help :)

Two PCs one runs windows XP home the other Windows XP Pro both servicepack 1, both properly registered and activated.

Both machines have add on firewire (PCI) adapters. ( Do not want to use these for PC to PC connection, too far)

The Pro machine has Ethernet adapter on board and the Home has a 10/100 Level one PCI Ethernet card.

Pro was manually configured with IP 192.168.0.1 and mask 255.255.255.0 and a member of workgroup "MSHOME"

Home was also manually configured with IP 192.168.0.18, mask 255.255.255.0 and also a member of workgroup "MSHOME"

now trouble begins.

They refuse to see each other >Network neighborhood> etc..

The Pro pings Home but when I try to ping the Pro from Home it times out. No way to map a shared drive from either machine using IPs (\\192.168.0.18\sharedc) where sharedc is the shared as name for the C drive of machine Home. It tells me that I do not have permissions and I should seee the administrator of " MSHOME" (the Home does not even ping so no point to try and map)

This thing has ruined my weekend and It has gotten me so mad I cannot think of what may be the problem.

I thank in advance anyone that tries to Help

Thanks

BT
==============================================================================================================================
 
M

madmax

have you set up some files to be shared?

--
the smartest man in the world doesn't know everything
he just knows where to look
Hello all :)

I Posted the following yesterday.
Today things improved in the sense that now the machines can ping each
other.
I still cannot see both machines in the neighborhood or in "Microsoft
windows Network" I can only see the machine that I am on , like they belong
to completely different networks.
All firewalls and similar BS has been removed .
The X-over cable was tested and is OK
The Ethernet adapters did also test ok ( ping self, ping each other and ping
loopback).

If I try to map a share though (i.e \\192.168.0.18\sharedc) (since they
ping) I get "the path was not found" The home machine has an identical
username and password with one of the two users on the pro machine and it is
this account that I use on both trying to set it up.

Server and Workstation services are started up automatically and they run on
both machines.

What else could be the problem? Is the sledgehammer the only tool that will
put an end to this misery??
Ahh how much I miss NT 4!!!

Thanks
Bill T
============================================================================
==================
Please help :)

Two PCs one runs windows XP home the other Windows XP Pro both servicepack
1, both properly registered and activated.

Both machines have add on firewire (PCI) adapters. ( Do not want to use
these for PC to PC connection, too far)

The Pro machine has Ethernet adapter on board and the Home has a 10/100
Level one PCI Ethernet card.

Pro was manually configured with IP 192.168.0.1 and mask 255.255.255.0 and a
member of workgroup "MSHOME"

Home was also manually configured with IP 192.168.0.18, mask 255.255.255.0
and also a member of workgroup "MSHOME"

now trouble begins.

They refuse to see each other >Network neighborhood> etc..

The Pro pings Home but when I try to ping the Pro from Home it times out. No
way to map a shared drive from either machine using IPs
(\\192.168.0.18\sharedc) where sharedc is the shared as name for the C drive
of machine Home. It tells me that I do not have permissions and I should
seee the administrator of " MSHOME" (the Home does not even ping so no point
to try and map)

This thing has ruined my weekend and It has gotten me so mad I cannot think
of what may be the problem.

I thank in advance anyone that tries to Help

Thanks

BT
============================================================================
==================================================
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

XP Home And XP PRO do not talk 5
Workgroup 1pro 1Home and lots of trouble 2
Xp Home AND Pro refuse to talk to each other 3
Home Networking -- 2 Networks 3
ICS - 2 x WINXP Pro 1
~Not allowed to see MSHOME~ 1
Workgroup sharing help need please 2
Peer to Peer network using a Crossover cable 5

Top