I am connecting two computers with Linksys 10/100 network cards and a crossover cable.Using netbeui protocol i can share files.If i use only tcp/ip i cannot share files(or see each other in network neighborhood)When running WINIPCFG both computers show the ip address and the subnet mask.however i cannot ping the other computer.Linksys support site says that using a crossover cable in a no no.Is there anyone that has a work around or must i invest in a router?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ping while using crossover cable?
- Thread starter mrfixall
- Start date
General information in another thread indicated that the problem comes about because tcpip doesn't identify the machine it is running on so the machines don't see each other. And the solution was to also use netbui as an additional protocol because it sends out identifying information. I can't vouch for the information, but I can relate that I have used the solution.
You might also want to use the utilities that are available for the cards to have them self test and network test to see what they think.
But even if they can't share data, they should at least be able to ping each other. And the crossover cable shouldn't affect that. Ed Fair
unixstuff@juno.com
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
You might also want to use the utilities that are available for the cards to have them self test and network test to see what they think.
But even if they can't share data, they should at least be able to ping each other. And the crossover cable shouldn't affect that. Ed Fair
unixstuff@juno.com
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
You might also want to see if the ip address is settable on the card. If so, the address you set via the network settings may not match.
Ed Fair
unixstuff@juno.com
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
Ed Fair
unixstuff@juno.com
Any advice I give is my best judgement based on my interpretation of the facts you supply. Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.
mrfixall
If you want to use TCP/IP be sure both your computers are belongs to the same network. It can be done with setting different IP addresses and the same subnet in the TCP/IP protocol's properties of both computers.
For example:
1st computer: IP 10.0.0.1 mask 255.255.255.252
2nd computer: IP 10.0.0.2 mask 255.255.255.252
To set TCP/IP properies find out the Network Neighbourhood icon on the desktop of each computer, right-click on it and select Properties. In the window appeared find the TCP/IP protocol and click Properties button. On the IP address tab of the properties window set the IP (for example as above) and netmask. Click OK. After rebooting both computers you will be able to ping each other and share resources via TCP/IP protocol.
If you want to use TCP/IP be sure both your computers are belongs to the same network. It can be done with setting different IP addresses and the same subnet in the TCP/IP protocol's properties of both computers.
For example:
1st computer: IP 10.0.0.1 mask 255.255.255.252
2nd computer: IP 10.0.0.2 mask 255.255.255.252
To set TCP/IP properies find out the Network Neighbourhood icon on the desktop of each computer, right-click on it and select Properties. In the window appeared find the TCP/IP protocol and click Properties button. On the IP address tab of the properties window set the IP (for example as above) and netmask. Click OK. After rebooting both computers you will be able to ping each other and share resources via TCP/IP protocol.
ITschoolGuy
Instructor
Mrfixall,
Theoretically (and I stress theoretically) the use of a crossover cable should have no effect on the performance of your chosen communication protocol. Keep in mind, however, that TCP/IP is a whole suite of protocols inter-operating at different levels...if any component at any layer is not functioning you'll have problems.
TyrantSSV makes a good point about where you should start. Once you're sure that the IP configuration of both PCs puts them within the same network, you should be able to PING each system from the other. But PINGing only verifies network connectivity...it doesn't guarantee that you'll be able to share files, etc. For network browsing and file sharing (under Windows) the NetBIOS component must be working properly. To check this, you can do the following:
Right-click Network Neighborhood and select Properties from the menu. Select TCP/IP from the component list and click the Properties button. Click the "NetBIOS" tab and make sure there is a check in the box that says "I want to enable NetBIOS over TCP/IP". Close the Network Properties sheet and get out to a DOS prompt.
From the DOS prompt, type nbtstat -s. If you see your computer name and the word "Listening" you're in good shape. If you get any kind of an error, you'll have to remove and re-install TCP/IP.
This is really only scratching the surface of TCP/IP configuration and troubleshooting. There's an awful lot to it.
Of course, now that I've gone through this whole explanation, it occurs to me to ask why you need to use TCP/IP? If you're connecting two systems directly (ie. without any connections to other networks or the Internet) why not can TCP/IP and just use NetBEUI or IPX exclusively?
Anyway, I hope you can get some use out of all this info.
Chris
Theoretically (and I stress theoretically) the use of a crossover cable should have no effect on the performance of your chosen communication protocol. Keep in mind, however, that TCP/IP is a whole suite of protocols inter-operating at different levels...if any component at any layer is not functioning you'll have problems.
TyrantSSV makes a good point about where you should start. Once you're sure that the IP configuration of both PCs puts them within the same network, you should be able to PING each system from the other. But PINGing only verifies network connectivity...it doesn't guarantee that you'll be able to share files, etc. For network browsing and file sharing (under Windows) the NetBIOS component must be working properly. To check this, you can do the following:
Right-click Network Neighborhood and select Properties from the menu. Select TCP/IP from the component list and click the Properties button. Click the "NetBIOS" tab and make sure there is a check in the box that says "I want to enable NetBIOS over TCP/IP". Close the Network Properties sheet and get out to a DOS prompt.
From the DOS prompt, type nbtstat -s. If you see your computer name and the word "Listening" you're in good shape. If you get any kind of an error, you'll have to remove and re-install TCP/IP.
This is really only scratching the surface of TCP/IP configuration and troubleshooting. There's an awful lot to it.
Of course, now that I've gone through this whole explanation, it occurs to me to ask why you need to use TCP/IP? If you're connecting two systems directly (ie. without any connections to other networks or the Internet) why not can TCP/IP and just use NetBEUI or IPX exclusively?
Anyway, I hope you can get some use out of all this info.
Chris
OK about NetBIOS support by TCP/IP. But it is usially enabled by default (enabled and grayed for example in my system with 98SE and 3Com 3C905C-TX-M NIC).
And I agree with ITschoolGuy about NetBEUI or IPX for two-computer network. It is easier. mrfixall do you have any software demanding TCP/IP?
And I agree with ITschoolGuy about NetBEUI or IPX for two-computer network. It is easier. mrfixall do you have any software demanding TCP/IP?
- Thread starter
- #7
TyrantSSV,Yes,I want to use Wingate to be able to share the dial-up internet connection.Both it and the Windows Connection Shareing(ICS) programs need TCP/ip to connect.I have tried both of these programs and failed because of the failure to be able to Ping.As I wrote before,there is no problem to share files using NETBEIU PROTOCOL but it can't replace TCP/ip for the ICS programs.
ITschoolGuy
Instructor
Mrfixall,
If I remember correctly, Windows ICS (Internet Connection Sharing) will automatically assign IP configuration to the client computer. So, as long as your TCP/IP settings on the host computer are viable you can set the client to obtain its IP address automatically. Have you tried it this way...and, if so, what was the result?
Chris
If I remember correctly, Windows ICS (Internet Connection Sharing) will automatically assign IP configuration to the client computer. So, as long as your TCP/IP settings on the host computer are viable you can set the client to obtain its IP address automatically. Have you tried it this way...and, if so, what was the result?
Chris
- Thread starter
- #10
TyrantSSV, When I tried the Windows ICS after setting up the host server and doing the "reboot dance" I then attempted to set up the client computer,I say attempted because the program was not able to find a server host.This is because the TCP/IP is not working properly on the NIC.The TCP/IP dial-up adaptor works fine to connect to the ISP and browse the internet.If I can ping the computers fom each other I will have what I want.At this point in time,before I become old and dried up,if I wish to be able to share the internet connection,I will have to spring for a HUB.Linksys says that the crossover cable is NOT the way to go and I guess that they are correct.At first I thought that they just want to sell more hardware since I was able to share files using the NETBEUI protocol,but now I believe that the TCP/IP protocol is much more complicated to use.
mrfixall
I just have disconnected the my machine and one more from a network (both of them have TCP/IP and works fine) and have connected them via crossover cable right now. TCP/IP works, and I can see each other in a network environment and use resources of other computer. It works!
A problem in the other thing.
If you use the dial-up adapter for Internet connection, but want to share this connection with other computer through a network, you need to establish the routing between dial-up adapter and NIC on "server" (the machine having an internet access). This can be done with Wingate running on machine having an internet access. Any wrong in Wingate settings?
I just have disconnected the my machine and one more from a network (both of them have TCP/IP and works fine) and have connected them via crossover cable right now. TCP/IP works, and I can see each other in a network environment and use resources of other computer. It works!
A problem in the other thing.
If you use the dial-up adapter for Internet connection, but want to share this connection with other computer through a network, you need to establish the routing between dial-up adapter and NIC on "server" (the machine having an internet access). This can be done with Wingate running on machine having an internet access. Any wrong in Wingate settings?
- Thread starter
- #12
TyrantSSV, Maybe it is a problem that is caused by the NIC cards that are made by Linksys.I have been told by others that they have no problems with cards from other mfgs.As to Wingate,it is OK but cannot work without the functioning TCP/IP on the NIC.
- Status
Similar threads
- Locked
- Question