Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Networking with Windows 2000 Prof

Status
Not open for further replies.

robdon

Programmer
May 21, 2001
252
ES
Hi,

I did have my 2 computers networked on a local LAN, and I shared files & folders fine.

One was Win 2000 Prof, and the other Win 98.

Both had NetBeui installed.

I have now got a new computer with WinXP prof. on it and I am having trouble seeing the other pc (win 2000).

The actual connection is fine, cause I have internet access.

I have installed NetBeui on WindowsXP. And I have the same user name on both machines.

In file explorer under 'Entire Network' I can only see the 'local' machine not the other one.

This worked fine with win98 & Win 2000.

Anyone any ideas on what I could do?

Thanks for any help,

Rob D.
 
PS..... They are all in the same workgroup 'WORKGROUP'

Rob D
 
Ok,

I've got a bit further....

I removed NetBeui from the XP side.

I connected another Win 2000 PC and the 2 Win2000 pcs can see and share files fine.

Seemed like after rebooting it took a while before the computers showed up on the XP side....

Now I can see the Win 2000 Pc name in the XP's 'Entire Network' list.

When I click on the computer name I get '\\computer_name is not accessible. You might not have permission to use this network resource.'

I have the same user setup on both PC's.

Are there any other 'security' issues that I may need to setup that are new in XP?

Any ideas???

Thanks,

Rob D
 
Idea...

Does the Win2k computer have any shares? If there are no shares other than the administrative shares (e.g. C$) then there is nothing a non-admin type user can access and that may be the issue.

The two rules for success are:
1. Never tell them everything you know.

 
Hi,

Yes, the win2k machine does have shared dirs.

My other Win2k machine can see them fine, its just my XP machine that can't.

Strange thing, my XP machine can see both the 2 pcs (I just cant connect to them, they are shown in the 'Entire Network', but clicking on them gives the above error), but the 2 Win2k machines cannot even see the XP machine....

Thanks,

Rob D
 
Question,

When I open "Entire Network" I see none of the local Lan computers but if I open the "Microsoft Windows Network" I then see the workgroup (in my case 4431windsor). I also see the workgroup 4431windsor in My Network Places the same as I see 'under' the "Entire Network". Is this the same for you? Do You see your workgroup "WORKGROUP" anywhere? The two rules for success are:
1. Never tell them everything you know.

 
Sorry, I was missing a bit....

On my WinXP machine I get

Entire Network
Microsoft Windows Network
Workgroup
PC1 (Win2k)
PC2 (Win2k)
PC3 (WinXP)

On my Win2k machines I get
Entire Network
Microsoft Windows Network
Workgroup
PC1 (Win2k)
PC2 (Win2k)

If I click on either PC1 or PC2 from the WinXP machine, I get the error message. Clicking on PC1 or PC2 on the Win2K machines goes to the 'share' folders.

Thanks.

Rob D

 
This one has me stumped...

Has the XP machine ever asked you to log on when you tried to open the Win2K machine?

I have only WinXP machines but when I access one machine from another it asks for a logon name and password for the target machine e.g. computername\username where computername is the name of the computer I'm trying to open. But once I have done that I'm never asked again even if I reboot. The next time I access the other machine I just go there and see it's shares.

Are you sure, just asking cause this is buggin' me :), the usernames are exactly the same on all machines and that they are included in the shares. On the permissions of the shares the users that have permissions are in the notation - user (computername\user) where the computername is the local computer's name and the user is a local user. The two rules for success are:
1. Never tell them everything you know.

 
Found this on another forum:

Windows XP comes defaulted with simple network management when using workgroups. To change this, go to start and then my computer. Click on tools and folder options and then on the view tab. Then down in the checkbox, uncheck use simple file sharing. Then you have the normal sharing password and administration like you would in NT or 2000. You can access this information at MS knowledgebase here...

On my my system I do have simple file sharing turned off. The two rules for success are:
1. Never tell them everything you know.
 
Hi,

Thanks for those pointers....

Xp has never asked me for username/password to logon... that sounds strange.

I went through all the links, and could not find anythings that applied to me.

I have now turned 'simple file sharing' off, but it did not help....

Anyone else....

Thanks,

Rob D
 
A basic response.

XP does not normally have accounts for computers automatically.

Does the XP machine have an account on the server?

Good luck.

Mark
 
Server???

I have 3 PCs, which all that the same username/password on them.

Rob D
 
Has a solution to this one been found? I'm having exactly the same problems. I'm assuming the firewall mentioned is the internet connection firewall on the advanced tab of the local area connection. Mine is turned off.
 
Found the solution at least in my case. If you have zone alarm installed, it's running whether you know it or not. Either take the trouble to configure zone alarm for your network, or uninstall it. Simply not starting it isn't an option, as it runs whether you know it or not. Some sort of startup service I imagine.
 
This is likely your problem... Windows XP has NEW built-in security, if the account does NOT have a password, most networking features will be disabled. This applies to sharing and other network tools, such as Remote Desktop. The planning behind it, falls into the migration of the Home User away from the 9x/ME system to the NT/2000/XP model. The idea here is that the average home user won't have a clue as to how vunerable their system would be, if they had an account without a password. The secondary issue is from an OEM standpoint, how do you preload a security account driven OS with a standard preload, without setting up a password? Also, another problem is the built-in firewall. My solution to you is to do the following

1.) Make sure that you have a password for each account on the XP box.

2.) To get around the TCPIP/Firewall issues with XP, install IPX on all the systems. This is especially crucial on a home network that uses a router (e.g. LinkSys DSL router)

3.) Get rid of Simplifed Sharing via the Folder Options tab and disable Desktop Remote/Assistance via System Properties (Windows Key + Pause).

4.) Make sure all computers belong to the same workgroup, Note: the wizard in XP will create a workgroup called MSHOME, the other OSes you listed create a workgroup called "WORKGROUP". (Advice : Avoid like the plague, the networking wizard). Change this through the System Properties (see above) > Computername Tab.

Test the configuration using a test folder and test file on any non-XP box. Then browse the network from the XP box to test your configuration.

Good Luck
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top