Windows networking complications

[David O'Meara]

I have two machines running win2k.
One of them is a laptop that is connected to the network at work and has a static IP as well as defined gateway, dns and wins settings. I don't have priveledges to remove and add it to the work network, but I am the local (machine) admin.
The home machine is on its own workgroup and can have whatever settings I want.
I'm connecting the two with a crossover cable.
Now to the problem: I can't do it
I've tried TCP/IP, NetBeui, NetBios and all of them togther with a variety of settings, but I can't get them talking.
Anyone have a hint or a link to a doc on how to get started? I've searched and read other stuff but they assume that the laptop isn't part of a network that it isn't connected to...
Dave

[Sameer Jamal]

First of all you use "net view" command from the dos prompt to see the computers attached to your terminal, if it does not show any computer then check the other(second) system by using "ping <ip address>" of the other system if it shows reply from the other system then there is no problem in physical connectivity, if it shows no reply from the other system then there is problem in physical connectivity so check your cable or reinstall your Network Interface Card. If the system is pinging the other system but is not showing in networking neighbourhood then please congfigure your following network setting
goto networking neighbourhood --> properties and see whether following settings are correct or not
1 Configuration window must show your network card type and it shows NetBEUI and TCP/IP protocols pointing to your Network Interface card
if either of the protocol is absent then please add the missing protocol
You must add client for microsoft network for your client machine then you can add file and printer sharing from services in order to share your file and printer.
2.Check the properties of client for microsoft network and check whether you have selected the right option if you are logging on to any domain then please specify the domain name and if you are not then please check logon and restore network connection.
If you are logging on to aby domain then please open the account in server for your client machine and in access control please check the user level acess control
if you are not logging on to any domain then in access control you should check the share level access control.
This configuration was for client machine.

[David O'Meara]

Not significantly different to what I've tried, except for the MS Client thing and a bit of diagnostics, but I'll give it a go.
It still doesn't seem to address the problem of having the laptop, which is supposed to be part of a domain and is not, connecting to the desktop, which is in a workgroup.
Thoughts?