HI,I'm trying to connection my Windows 7 laptop to my XP desktop with a crossover cable. These are the things I've done so far: I have manually assigned both of them IP addresses as many posts had suggested(xxx.xxx.xxx.1 on the laptop, 2 on the desktop, and the gateway is the opposite). I've renamed both computers with the same work group name(and rebooted). I've also created homegroup on the laptop. The Network and Sharing Center window displays a house icon labled 'Network3' . Finally, I've dissabled norton firewall on both computers. I was able to ping the desktop from the laptop, but neither computer show up in each other's network windows. What went wrong? Thanks in advance!

homegroup only works with other win 7 boxesand when you use a crossover or switch you do not input a gateway or DNS servers as you do not have one.and as showing up in the network windows that is a function of net bios over TCP /IP use the ip address not the name to access the shares.in the run box put //xxx.xxx.xxx.1 or 2 to access the PC's shares.

Try mapping the name of the pc instead of using it's IP, example under search program and files type the following \\Marryann-PC (make sure you get the correct name of the pc before mapping it) and next hit enter and bingo, you should be able to see the share printer and folders next

Thank you for the replies. Since I can only test the suggestions after I take the PC offline, I'll give some update before further tests. Generally speaking the comps still doesn't show up in eachother's network. For Bubba's comment I've left the home group on the window7 laptop and also tried to erase the "default gateway" entry on both comp. The later caused an 'yellow !' on the connection so I put their repective IP back on as before. Correct me if I'm wrong I thought you were suppose to fill out all three boxes in the 'use the following IP address', and the 'default gateway' is suppose to be the ip of the other comp you are trying to connect?So are you guys saying I'm not suppose to be able to see the two computers in the network windows like the window 7's network and sharing center? And instead have to search it like another hard drive? Also..there's another problem now. After I rebooted the XP pc, a 'yellow !' showed up in windows 7 between the name of the laptop and the gateway icon. I ran the troubleshooting tool and all its options it keep resulting 'couldn't find the problem'. Any thoughts on that? Is there a way to test if its the XP end is blocking the connection? and if one of the network card has crossover function and I used a crossover cable will it cause a problem and how do I check if it is such network card? If possible can someone post a step by step guide on connecting windows 7 to xp with a crossover cable?

With a crossover cable you do not have a gateway nor do you have a DNS server, if you tell the system you do it will look for them, as they are not there they will not be found get it..a 'yellow !' showed up in windows 7 between the name of the laptop and the gateway icon. with crossover you do not have a gatewayas for seeing the computers by name on network...You need to search google for netbios over tcp ipAs this not a windows 7 question but a networking how to, you should use google you will finds TONS of info.

Are the computers multi-homed computers? How many network adapters does each computer have? If there are more than one network adapters in one computer, please let us know if all of the network adapters are in the same network, such as 192.168.0.*. I suggest you turn on Network Discovery in Windows 7, also enable NetBIOS over TCP/IP on both computers. If the issue still occurs, temporary disable the firewall on both computers and check the result. Please note that Peer-to-peer connections via crossover cables are beyond of the scope of the 802.3 standard, therefore it may not work as expected. Using Crossover Cables in Home or Peer-to-Peer Networks Whether the behaviors are proper base on the design of the network adapter drivers. In your case we may not be able to change it. Purchasing a switch or a router will be a final solution. Arthur Xie - MSFT