Madhur said:
Use the static IP addresses and show the output of these commands on
both computers:
ipconfig /all
ping compname
ping ipname
route print
And whats that supposed to solve?
Ipconfig shows the ip... then what?
ping is useless - he already said that.
and route print? That displays (and nothing else) routing - only
relevant when traffic leaves his LAN. Nearly useless advice...
Bruce:
If you need to use IP to communicate - set static IP-addresses on both
machines with matching subnet-masks. For instance:
WinME machine: IP 10.10.10.10, Subnetmask: 255.255.255.0
Win2K machine: IP 10.10.10.20, Subnetmask: 255.255.255.0
For basic connectivity you can use any kind of hub/desktop-switch or
even a crossover-cable for direct pc-2-pc. Turn off firewalls and NOW
you can use ping to verify that machines talk to eachother.
For the ME computer to use a 2K resource, make sure the username used on
the ME machine exists on the 2K machine (with same password). The other
way around you can always "connect as" and authenticate that way.
I'd try to install NETBEUI as a protocol on both machines. It doesent
need any addresses, and its unroutable, so you dont have to worry about
securing that protocol outside your own lan.
If you still have connection-problems with this we're going to need more
information from you about what you've done, what you got and so on...
Hope this helps