Company PC Win2k doesn't see Home WinXp

  • Thread starter Thread starter markPanger
  • Start date Start date
M

markPanger

Setup:
Cable modem using Linksys 4 port router.
Functioning home network (wired) with one PC running Win98 the other PC
running WinXP.
Those work well. Able to see each other and connect to internet.

Just got a company provided Thinkpad to connect to company network. It's
running Win 2000 Pro and communicates well with company network. Company PC
uses proxies.

Currently I'm emailing files between machines. I'd like for my Win XP
machine to see the Win 2000 office machine and vise versa. I haven't been
able to make that happen.

Is it possible?

I am PC savvy but I know little about networking. If there's a solution I
need the "Networking for Dummies" version.

THANK YOU FOR ANY HELP YOU CAN GIVE ME!!!

mark
 
See them where? - all on the home network or between work and home. To see
each other between work and home you would need a vpn setup. --- Steve
 
Is it possible?
I am PC savvy but I know little about networking. If there's a solution I
need the "Networking for Dummies" version.

THANK YOU FOR ANY HELP YOU CAN GIVE ME!!!

mark

make the workgroup on the home pc the same name as the domain name of
the work laptop assuming its attached to a domain

let the linksys hand out IP address using dhcp assuming your work laptop
doesnt use static ip's

if you want to exchange files then on your home pc create an account
with same username and password as the account your logged onto the work
machine with and share a folder and see if can access it using the start
run as in:-

\\192.168.0.1\ (using whatever youve set your ip address up as)

even if you have local admin access to your work system dont change
anything on it unless your friendly with your work it staff :)
 
I presume you mean you want to physically connect your laptop at home, on
your home network, for this.

You should be able to connect from your XP laptop to one of the other
computers even if you can't "see" them ....

net use x: \\otherPCname\sharename /user:otherPCname\usernameOnPC

You'll be prompted for a password - enter the appropriate one for that
account on the "host" computer. I'd leave it at that, rather than trying to
connect from the workgroup computer to the XP laptop -

Do not under any circumstances change your XP laptop from a domain to a
workgroup - you'll regret it, and will have to grovel to your sysadmins at
work to re-join the computer to the domain. ;-)
 
I had this problem too about a month ago.
Don't bother with the other posts here (no offense to
those taking the time to write)

Win XP and Win 2000 aren't compatible in their default
configuration. Odd but true. Win 2000 uses a protocol
called NetBEUI and TCP/IP. Win XP just uses TCP/IP. I
don't know why, neither do you in order to fix it. But you
have to install netBEUI on your XP box in order for your
2k box to see it. I am writing this on the 2k box sharing
files witht the XP box right now. I can't understand why
such an obvious requirement is so hard to troubleshoot and
repair, but it is.

I went to this site and followed the instructions:
www.practicallynetworked.com/sharing/xp/network_protocols.h
tm

Follow these instructions to install NetBEUI on your XP
box and then the two should see eachother (the 2k pc has
NetBEUI in default config.) Hope this helps.
 
hmmm... I got NETBUI installed on the XP machine. When I boot the XP
machine I get an error that I have a duplicate network name on my network (I
don't know since the network ID's on my 3 machines are unique). I still
have access to the shared folders on my Win98 machine and the Win98 machine
has access to the shared folders on the XP. BUT I still can't see the
company 2k machine's shared folders.

The XP and the 98 are in a Workgroup named MPHOME.

I looked at the installed protocols on the 2k machine and it isn't there.

Have I missed something or done something in error?

Thank you!
Mark :-)
 
David said:
I had this problem too about a month ago.
Don't bother with the other posts here (no offense to
those taking the time to write)

Hmmm - did you see my reply?
Win XP and Win 2000 aren't compatible in their default
configuration. Odd but true. Win 2000 uses a protocol
called NetBEUI and TCP/IP.

Win2k doesn't have to use NetBEUI. I've never used it on a Win2k PC. They're
perfectly compatible on networks, without NetBEUI. When you install W2k, I
don't think it installs/configures NetBEUI by default.

Win XP just uses TCP/IP. I
don't know why, neither do you in order to fix it. But you
have to install netBEUI on your XP box in order for your
2k box to see it. I am writing this on the 2k box sharing
files witht the XP box right now. I can't understand why
such an obvious requirement is so hard to troubleshoot and
repair, but it is.

I went to this site and followed the instructions:
www.practicallynetworked.com/sharing/xp/network_protocols.h
tm

Follow these instructions to install NetBEUI on your XP
box and then the two should see eachother (the 2k pc has
NetBEUI in default config.) Hope this helps.

Not necessary. TCP/IP alone will work....and less network traffic. You *can*
use NetBEUI if you wish, but it isn't necessary.
 
Windows 2000 does not have NetBEUI in its default config.

Sorry, but that is totally wrong advice. To the original poster, you should
talk to your company's IT people about what you're planning to do, as it
carries security risks to your company's network. They will be able to help
you out, if appropriate.

Oli
 
I agree with Oli. If netbeui works where tcp/ip does not that simply means you have
incorrectly configured tcp/ip. --- Steve
 
Kind of a related question:
\
I took three W2K Pro PCs from a networked environment at the main facility
to a remote location where I set them up to access the network at the main
facility using VPN and a shared DSL connection on a linksys four port
router. I can't administer the PCs at the remote location, i.e., create a
local machine user accounts, change passwords, add user rights, etc. None
of the three PCs can join a workgrup. Can't even remove them from the
domain. Only solution I can think of is to take them back to the main
facility connect them to the network then remove them from the domain.

Any suggestions?

Thanks,

Mike

Do not under any circumstances change your XP laptop from a domain to a
workgroup - you'll regret it, and will have to grovel to your sysadmins at
work to re-join the computer to the domain. ;-)
\

"Lanwench [MVP - Exchange]"
 
Probably best to post a new thread....you'll get more replies that way.

That said - what's your goal? Is this remote location supposed to be part of
the domain? If so, why would you want to remove them for the domain or use
local user accounts? You should be able to do that if you can log in as
local administrator, but I don't see the point....
Kind of a related question:
\
I took three W2K Pro PCs from a networked environment at the main
facility to a remote location where I set them up to access the
network at the main facility using VPN and a shared DSL connection on
a linksys four port router. I can't administer the PCs at the remote
location, i.e., create a local machine user accounts, change
passwords, add user rights, etc. None of the three PCs can join a
workgrup. Can't even remove them from the domain. Only solution I
can think of is to take them back to the main facility connect them
to the network then remove them from the domain.

Any suggestions?

Thanks,

Mike

Do not under any circumstances change your XP laptop from a domain
to a workgroup - you'll regret it, and will have to grovel to your
sysadmins at work to re-join the computer to the domain. ;-)
\

"Lanwench [MVP - Exchange]"
I presume you mean you want to physically connect your laptop at
home, on your home network, for this.

You should be able to connect from your XP laptop to one of the other
computers even if you can't "see" them ....

net use x: \\otherPCname\sharename /user:otherPCname\usernameOnPC

You'll be prompted for a password - enter the appropriate one for
that account on the "host" computer. I'd leave it at that, rather
than trying to connect from the workgroup computer to the XP laptop -

Do not under any circumstances change your XP laptop from a domain
to a workgroup - you'll regret it, and will have to grovel to your
sysadmins at work to re-join the computer to the domain. ;-)
 
The PCs don't need to be part of the domain. I want them to join a
workgroup so they can share files and printers.
I can't administer the PCs at the remote. site. log on as admin and that's
it. can't create local accts. Want too create a local acct
so users can log onto the PC then log onto VPN with their unique user accts
then log onto Outlook using their unique
user accts. This is preferable because most of the users share the PCs
during the day. If they have to log on and off
the PC they won't use it or they comprise confidental information. Logging
onto Outlook is another thing. Might not make a lot of sense, but that's
what
I've found works with this group of users.

Created a new thread a couple days ago, but only got one response.

Mike

"Lanwench [MVP - Exchange]"
Probably best to post a new thread....you'll get more replies that way.

That said - what's your goal? Is this remote location supposed to be part of
the domain? If so, why would you want to remove them for the domain or use
local user accounts? You should be able to do that if you can log in as
local administrator, but I don't see the point....
Kind of a related question:
\
I took three W2K Pro PCs from a networked environment at the main
facility to a remote location where I set them up to access the
network at the main facility using VPN and a shared DSL connection on
a linksys four port router. I can't administer the PCs at the remote
location, i.e., create a local machine user accounts, change
passwords, add user rights, etc. None of the three PCs can join a
workgrup. Can't even remove them from the domain. Only solution I
can think of is to take them back to the main facility connect them
to the network then remove them from the domain.

Any suggestions?

Thanks,

Mike

Do not under any circumstances change your XP laptop from a domain
to a workgroup - you'll regret it, and will have to grovel to your
sysadmins at work to re-join the computer to the domain. ;-)
\

"Lanwench [MVP - Exchange]"
I presume you mean you want to physically connect your laptop at
home, on your home network, for this.

You should be able to connect from your XP laptop to one of the other
computers even if you can't "see" them ....

net use x: \\otherPCname\sharename /user:otherPCname\usernameOnPC

You'll be prompted for a password - enter the appropriate one for
that account on the "host" computer. I'd leave it at that, rather
than trying to connect from the workgroup computer to the XP laptop -

Do not under any circumstances change your XP laptop from a domain
to a workgroup - you'll regret it, and will have to grovel to your
sysadmins at work to re-join the computer to the domain. ;-)
 
Can you log into the computers w/the local admin acct and set them up in a
workgroup?

So they'll be using Exchange? Make sure you set up the Exchange server
service in Outlook to prompt for credentials. You'll also need to create
multiple Outlook profiles, one for each user on each computer, and tell
Outlook to prompt for the profile. It's gonna be a bit of a PITA esp. if
they don't close Outlook fully on exit - if outlook.exe is running in the
background, the next user won't be prompted for a profile.

Are you not going to be managing these computers at all, after all this? Not
backing up any data, etc? Because if you want to do that, I'd keep them in
the domain and not have them use any local file shares....and set up a VPN
site link from that network to yours rather than using VPN individually on
each computer.
The PCs don't need to be part of the domain. I want them to join a
workgroup so they can share files and printers.
I can't administer the PCs at the remote. site. log on as admin and
that's it. can't create local accts. Want too create a local acct
so users can log onto the PC then log onto VPN with their unique user
accts then log onto Outlook using their unique
user accts. This is preferable because most of the users share the
PCs during the day. If they have to log on and off
the PC they won't use it or they comprise confidental information.
Logging onto Outlook is another thing. Might not make a lot of
sense, but that's what
I've found works with this group of users.

Created a new thread a couple days ago, but only got one response.

Mike

"Lanwench [MVP - Exchange]"
Probably best to post a new thread....you'll get more replies that
way.

That said - what's your goal? Is this remote location supposed to be
part of the domain? If so, why would you want to remove them for the
domain or use local user accounts? You should be able to do that if
you can log in as local administrator, but I don't see the point....
Kind of a related question:
\
I took three W2K Pro PCs from a networked environment at the main
facility to a remote location where I set them up to access the
network at the main facility using VPN and a shared DSL connection
on a linksys four port router. I can't administer the PCs at the
remote location, i.e., create a local machine user accounts, change
passwords, add user rights, etc. None of the three PCs can join a
workgrup. Can't even remove them from the domain. Only solution I
can think of is to take them back to the main facility connect them
to the network then remove them from the domain.

Any suggestions?

Thanks,

Mike


Do not under any circumstances change your XP laptop from a domain
to a workgroup - you'll regret it, and will have to grovel to your
sysadmins at work to re-join the computer to the domain. ;-)
\

"Lanwench [MVP - Exchange]"
message I presume you mean you want to physically connect your laptop at
home, on your home network, for this.

You should be able to connect from your XP laptop to one of the
other computers even if you can't "see" them ....

net use x: \\otherPCname\sharename /user:otherPCname\usernameOnPC

You'll be prompted for a password - enter the appropriate one for
that account on the "host" computer. I'd leave it at that, rather
than trying to connect from the workgroup computer to the XP
laptop -

Do not under any circumstances change your XP laptop from a domain
to a workgroup - you'll regret it, and will have to grovel to your
sysadmins at work to re-join the computer to the domain. ;-)
 
Removed one of the PCs from the domain in network neighborhood and put it
into a workgroup.
Everything is ok now.
if outlook.exe is running in the
background, the next user won't be prompted for a profile

Good tip.
and set up a VPN
site link from that network to yours rather than using VPN individually on
each computer.

Currently setup w/ VPN on each PC.

Nothing really to manage after setting up user accounts, which I was able to
do on the PC I removed from the domain.
No data will be saved on these pcs.

Mike





Mike

"Lanwench [MVP - Exchange]"
 
Back
Top