Cross over cabling & w2k

[confus-ed]

had two pc's networked using a cross over cable, using 95 and 98se everything ok, now want to use exectly the same under win 2k, thought all I needed was the same setup in win2k. Seem to be having loads of problems, blow by blow instructions in words of 3 syllables or less please!

[Deity]

What kind of problems are you having? What type of network? NICs? Protocols? More info please...

[confus-ed]

First see if you think this crossover cable is faulty, I get a connected signal in win 2k (but only sending packets none received), ping doesn't fail but times out. When I log the 95 machine off I get cable uplugged (which I should) so what else can be amiss? Both machines have the same workgroup name, IP address's set, and TCP/IP installed. I intermittently get mqsvc service errors saying it can't connect to its host. I think win 2k is expecting either a DNs or wins server somewhere, but since I'm using w2k pro I don't have those services do I?

[Deity]

Win 2K Pro should be able to run fine in a peer-to-peer environment. I would think, as long as you have the correct settings (IP add, subnet, gateway, etc.) that your network should function fine whether it be through a hub, switch or crossover cable. To my knowledge also, 2K Pro does not need to communicate with a DNS, WINS, or any other type of server/service to operate. I have a friend who setup a small home network with 2K Pro and Win98se. He was using a hub, but I refuse to believe that 2K doesn't allow connection without a hub.

[Humilliation]

On the W2K Pro machine have you set the share to $IPC instead of $C? Right click on my computer and check it out under sharing. Can your Win98 machine see the W2K machine when you do a search for Computers? Can the W2K machine see the Win98 machine? Make sure the protocols are set all the same and that File and Printer sharing is set on both machines. The cable sounds to be alright if it worked previously and is still sending packets, if you want to be sure just switch the cable around and see if the W2K system still tries to send packets, if it does the cable's still good because it's detecting a connection. Make sure you disable File and Printer sharing in the properties of TCP/IP or you'll be sharing files with the rest of the world if your not passworded. You will also want to change the computer names and workgroup names on each system, different names make it less confusing for the system, same names tend to make communicating between computers not want to work. There must be different names. If you named one computer Sam1 and it already found one Sam1 it won't look for another Sam1, maybe Sam1 and Sam2.

[ibennetch]

Sounds like a compatablility problem. I'm not sure how to fix it; if security isn't an issure try enabling the guest account on the win98 box; i think that's how I finally got one I was playing with to work. Also, someone suggested having the same login/password on the win98 machine network login as you have set up to access the w2k box. Good luck; i'm interested in this because it's an issue I haven't totally sorted out yet

[Dr Jam]

Agree with what everyone said so far

Just want to add - dont forget to add your user names to both win2k pc's when they can see each other in order to be able to access file share's between them

Good Luck !

[confus-ed]

Still getting time out on ping. Which genius decided you can't delete your local area connection. Does anyone know what msqvc.exe is doing because I'm still getting this service error.

Lastly what's the equivalent of ipconfig for a 95 machine(so I can check my settings), and isn't there a whole load of net "type" commands you can use to check connections.

I'm still no further forward. <IMG SRC="smilies/mad.gif" border="0">

[confus-ed]

Sorry what is MQSVC not msqvc!?

[ibennetch]

winipcfg

[confus-ed]

Twas a faulty cable! But because net bios is automatically enabled for tcp/ip then win 2k sees the faulty connection as a null modem. Hence why only one end was sending packets. <IMG SRC="smilies/rolleyes.gif" border="0">

[WesFlash]

I know that most people tend to shy away from IPX/SPX, but I found it helpful to just make sure the dang computer could see the other one when I didn't know how to set up TCP/IP properly. I say to set it up to see if things work. If you can see the other computer but can't ping or get TCP/IP games towork, then work on the TCP/IP side. Just my 2 cents, but that is what I went through when I tried to learn networking the first time. I had a x-over cable, 2 NIC's and 2 computers. I got them all working on the network, it took over two weeks to finaly get the missing subnet information I needed.