Posted on 05/16/2004 4:35:48 AM PDT by LuLuLuLu
We are trying to set up a two computer, peer-to-peer network with a laptop and desktop, both Dell machines.
The desktop has Windows ME and the laptop has XP. To make a long story short, they aren't talking to each other.
Help in ME says that it can network with 95, 98 and ME only. We can't find anything in XP that says it's not backwards compatible.
Any suggestions?
Yeah use the xp install disk to install the network on the ME computer. You can choose to do that from the menu that comes up when you put the cd in the drive.
The first step is to get rid of Windows ME.
IIRC, I believe the ME computer will allow you to create a small networking program on diskette. Running that disk on the XP will install the necessary networking software. I networked several computers at my office this way and it was quite a simple (thank heavens) operation. Good luck.
Are you doing it with a CAT 5 line (RJ-45 jacks and plugs) but without a hub? If so, some of the lines need to be switched around (into what's called a "crossover"), and that can be done at the jack/plug junction. ...sorry I haven't done the peer-to-peer thing in a long time and don't have a diagram. But you should be able to find a peer-to-peer wiring diagram on the Web, somewhere. Just try keywords like, "peer-to-peer," "CAT 5," "RJ-45," "diagram," "crossover" and so forth.
Not sure what networking protocol your intending to use but
Microsoft's old windows to windows peer networks used netbeui protocol which is not included in the standard setup of XP. I beleive ME is the old one and uses netbeui to connect peer to peer. Check MS tech support on how to add netbeui protocol to XP machines, you have to copy some files and move them. Then setup peer to peer using netbeui and internet using TCP/ip. Thats how I have it working on my machines which also include a few older windows 98se, 2000, and xp machines. Hope it helps.
I vote for the cable problem as being the most likely suspect. Most cables are sold for hub setups. If you are going peer to peer, you need a cross-over cable.
If you connect to the internet (your here aren't you) then consider buying a cheap hub 4 computer hub and networking them that way.
ME is the older version of software. It will not mention XP because XP was not out when it was shipped.
If hardware is OK you should be able to PING the machines and get a successful response. If you don't know what a PING is, find out how to do it. Microsoft - Troubleshooting home networking in Windows XP
On the XP machine, you have to turn off the firewall (I would disconnect from the internet first, if you don't have a router, though).
The key with XP is that the XP machine and the ME machine have to have the same username and password setup in user accounts. For example, if the username and password for the ME machine is username foo password foopasswd, there has to be an account on the XP machine with the very same username and password.
With that established, you have to share folders on both machines, and, in XP, either make sure simple file-sharing is turned on (the easiest way), or, set permissions appropriately (the most secure way).
HTH
longjack
"The key with XP is that the XP machine and the ME machine have to have the same username and password setup in user accounts. For example, if the username and password for the ME machine is username foo password foopasswd, there has to be an account on the XP machine with the very same username and password."
I hate to disagree with you, but Username & Password
don`t have to be the same on both machines. Guess you
are confusing Domains and Workgroups?
In this case, the original poster should control if the *name* of the workgroup is *identical*, on both systems.
This is the usual reason if PC 1 doesn`t "see" PC 2.
I dunno about american versions, but the default name
for a workgroup in my german Win 98 is "workgroup",
but "Arbeitsgruppe" in my german XP. I guess there is
a similiar problem with his U.S. ME & XP... just different
default names.
The used OS is irrelevant, you are able to connect with
XP + ME + 98 + Linux + MAC OS + .... as long as they are
sharing the same protocols and the workgroup.
...just my 0.2 Euros :o)
Hun
Are you using dialup and ICS (Internet Connection Sharing) or an ethernet connection to a cable or DSL hub? In either case I STRONGLY recommend buying a hub or router and using standard instead of crossover cables, but if you are using ICS with dialup, the machine with the modem acts as a ROUTER, translating addresses and converting the protocol. I think you have to have the newer OS as the ICS router, where the upstream connection occurs.
if you intend to access data on a Windows 2000/XP system, then you MUST make sure that the username (and password) used during the Windows 95/98/ME/2000/XP start-up is identical to the username (and password) defined in User Management of the Windows2000/XP system, to which you like to connect. Like sitting down at the keyboard, where you need to enter your username, also a connection via network requires identification !
longjack
"if you intend to access data on a Windows 2000/XP system, then you MUST make sure that the username (and password) used during the Windows 95/98/ME/2000/XP start-up is identical to the username (and password) defined in User Management of the Windows2000/XP system, to which you like to connect. Like sitting down at the keyboard, where you need to enter your username, also a connection via network requires identification."
Yes & No... :o)
You are talking about the problem how to access data on
a shared network drive. A network drive can either be
blocked for remote access, or enabled for certain users
or just everybody (except System Folders). The access for
certain users is usually a limitation set by the NTFS file system, not by the network
shared drives settings.
The problem of the original poster is a pure network
configuration problem. It may be caused by the points
you`ve already mentioned (cables,protocolls, etc), but
the fact that both machines don`t see each other is
often (most of the time...) caused by simple mistakes,
such as different names for the workgroup...
Hun,
MCP
As always, one should check the basic settings first:
Microsoft Knowledge Base Article - 826812
Windows XP Home Edition-Based Computers Cannot Detect Windows Millennium Edition-Based Computers on a Home Network
SYMPTOMS
When you connect a Microsoft Windows XP Home Edition-based computer to a network that has Microsoft Windows Millennium Edition-based computers connected to it, the Windows XP Home Edition-based computer will be not be able to connect to any of the Windows Millennium Edition-based computers on the network.
CAUSE
This problem may occur if the Windows Millennium Edition-based computers do not have the TCP/IP network protocol installed. By default, Windows XP uses the TCP/IP networking protocol to connect to other computers on a network.
WORKAROUND
To work around this problem, configure each Windows Millennium Edition-based computer to use the TCP/IP network protocol.
For each Windows Millennium Edition-based computer on the network, follow these steps:
Click Start, click Settings, and then click Control Panel.
Double-click Network, and then click the Network Configuration tab.
Click Add, click Protocol, and then click Add.
Click Microsoft, click TCP/IP, and then click OK.
For additional information about troubleshooting home network connections, click the following article number to view the article in the Microsoft Knowledge Base:
308007 Troubleshooting Home Networking in Windows XP
For additional information about accessing shared folders from a Windows Millennium Edition-based computer, click the following article number to view the article in the Microsoft Knowledge Base:
266033 Cannot Connect to Subfolders Within a Password-Protected Share Folder
Source:
http://support.microsoft.com/default.aspx?scid=kb;en-us;826812
Regards,
Hun
PS: ...and don`t forget to check the names(s) of the
Workgroup :o)
Bumping to come back later and see all the gurus wisdom splattered all over. ;-)
If successful you should at the very least be able to PING each machine, first by its IP address, and then by its name.
That's not sound advice. ME will network just fine. And when it is configured properly it is superior to XP in some ways.
I've networked ME with every other MS OS and find that XP is the hairy beeyatch when it comes to manipulating it.
Ever try to get rid of a trojan from XP? The NTFS partition won't allow access to the disk without Windows running. That can cause a lot of headaches.
This could very well be your problem. I have networked laptops together doing this, (One with Win2k and the other with Win98se) and it is easy. You can find crossover cables on eBay for 3 or 4 bucks and all you need to do is plug the end of the cable into the NIC on each machine....and Whooppeee!
Turn off "system recovery" (something you need to do anytime you are removing a trojan or virus) and then bring the system up in safe mode.
Mark
Have this person purchase a firewall/switch combo for $30 - $70, and they'll be able to share data and the cable modem (relatively) safely.
Mark
Thanks Mark, I figured there was some gizmo like that out there. ;-)
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.