Domain / Workgroup Connectivity

  • Thread starter Thread starter Brian
  • Start date Start date
B

Brian

I have a laptop from work running Windows 2000 that connects to the work
domain/userid ( company\me ). When I have it at home I connect to work
using VPN via the IPSec client. I plug it into a Linksys router. Also
connected to this router is my home PC which is running Windows XP Pro
in workgroup mode. I have folders and printers on the Windows XP box
that I've shared to my home network but the Windows 2000 laptop cannot
see them from Windows Explorer (regardless if I have the VPN running or
not). Both PCs can ping each other. I'm told at work that they should
be able to work together. Any suggestions why can aren't? The network
wizard on Windows XP created a floppy that needed to be run on another
Windows 98 box in order for it to talk to XP. Do I need to do the same
for Windows 2000?

Brian
 
On your laptop, once you're connected to the home network & have logged into
the domain with cached credentials, see if you can ping the XP box by both
IP address and name.

If you can do so by name, you can 'blind map' a share -

net use x: \\winxpbox\sharename /user:winxpbox\validuseronthatpc
 
Tried that. I can ping the IP but not the name.

Lanwench said:
On your laptop, once you're connected to the home network & have logged into
the domain with cached credentials, see if you can ping the XP box by both
IP address and name.

If you can do so by name, you can 'blind map' a share -

net use x: \\winxpbox\sharename /user:winxpbox\validuseronthatpc
Click to expand...
 
A question: Do the passwords on the Domain Windows 2000 box and the
Workgroup Windows XP box need to be the same?

Brian
 
If you can ping the xp box from the w2K laptop then on the W2k box goto
Start - Run and type \\xpboxipaddress and then Ok

What do you get?
 
I can ping the XP IP address. I can ping the XP box name without the
leading \\, i.e.
ping family
But if I try: ping \\family it doesn't work. If I go to Start - Run and
type: \\192.168.1.100 I get the message:
\\192.168.1.100 is not accessible.
There are currently no logon servers to available to service the logon
request.

Brian
 
Back
Top