?
Solved

Crossover Cable with NETBEUI and with TCP/IP

Posted on 2004-03-21
21
Medium Priority
?
583 Views
Last Modified: 2013-12-23
Is it possible for a crossover cable connecting 2 Windows98 SE computers to work correctly with NETBEUI and be faulty for connecting with TCP/IP? With NETBEUI as the protocol everything works OK and with no problem setting it up. With TCP/IP each machine sees itself as on the workgroup but does not see the other machine in Network Neighbourhood. Each machind can ping itself, but not the other machine. Neither machine has any Internet connection, ICS is not activated on ether machine.
0
Comment
Question by:specsol
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 10
  • 6
  • 3
  • +1
21 Comments
 
LVL 32

Expert Comment

by:LucF
ID: 10643603
Hi specsol,

Could be that the TCP/IP stack or winsock is corrupt on one of the computers, use this tool to reset it.
http://www.bu.edu/pcsc/internetaccess/winsock2fix.html

Also, check if you have any firewalls running, you might have to reconfigure it so you build a trusted zone.

Greetings,

LucF
0
 

Author Comment

by:specsol
ID: 10643674
Thanks LucF. There are no firewalls running, (no internet connections), both machines had a clean install of Windows 98 SE and I have removed and re-installed the TCP/IP on both machines. They behave as if the cable is not there -- if I remove it, both computers still give same results. Suspected the cable faulty, but it works fine with NETBEUI and no TCP/IP. So wanted to know if TCP/IP uses a different set of the cable wires from NETBEUI?

Specsol
0
 
LVL 32

Expert Comment

by:LucF
ID: 10643678
specsol,
Nope they both use exactly the same cable, that's why I suspect a mistake in the tcp/ip stack.
What adresses have you used?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:specsol
ID: 10643902
I have tried just about every combination. Currently, one machine is on "Get IP Adress automatically -- setting 169.254.179.92, wwith the other a fixed address set at 192.168.0.2. Previously tried thev addresses set at 192.168.0.1 and 192.168.0.2 This last gave (for one occasion) the 192.168.0.2 machine listing both machines in Network Neighbourhood but unable to reach the other while the 192.168.0.1 machine only saw itself. Thanks for the info about the cable use in NETBEUI & TCP/IP -- I was gradually coming to that conclusion myself. Will try your tool & see what happens

Specsol
0
 
LVL 32

Expert Comment

by:LucF
ID: 10643924
Ok, good luck.

btw, the settings you posted above: 192.168.0.1 and 192.168.0.2 is the right one. Both with a subnet mask of 255.255.255.0
0
 

Author Comment

by:specsol
ID: 10644018
The Win2Fix tool does not do the trick. In using the 192.168.0.1 & 192.168.0.2 I presume this implies setting both machines to have a fixed IP address. What should be the settings for DNS configuration? I had set DNS enabled with the Host as the machines own name but put 192.168.0.1 as the DNS search order. Also put 192.168.0.1 in the Gateway. Each machine had its own IP addess in the IP Address tab.

Specsol
0
 
LVL 32

Expert Comment

by:LucF
ID: 10644029
As there are no internet connections, you don't have to fill in the DNS servers, so set it up not to use DNS.

I'm wondering why you can't ping the other computer... :(
0
 

Author Comment

by:specsol
ID: 10644094
So am I! That is what originally made me think the cable was to blame. Will set it to not use DNS on both machines

Specsol
0
 
LVL 32

Expert Comment

by:LucF
ID: 10644106
Please doublecheck if you don't have any firewalls running. Zonealarm/Norton internet security/ whatever.
0
 

Author Comment

by:specsol
ID: 10644331
Definitely no firewalls, nothing installed. Also system is not stable. If I alter some parameters then go back to previous settings, the machines behave differently. Currently, with addresses 192.168.0.1 and 192.168.0.2 the 192.168/0/1 mamhine sees both machines in Netwoek Neighbourhood, cannot access 192.168.0.2 (gives message \\Mcl2 is not accessible, the computer or sharename could not be found) while the 192.168.0.2 machine cannot see anything (even itself) in Network Neighbourhood (message Unable to browse the network, when clicking on Entire Network). Previously with same settings as now, each could see itself but not the other. As regards the "Unable to browse the network" message, I am familiar with the Microsoft Knowledge  Base Article 193938 on this message. Been through with no result

Specsol

0
 

Author Comment

by:specsol
ID: 10644581
Further information. I got past the "Unable to browse the network" by removing and then replacing the TCP/IP. 192.168.0.2 now sees itself but not 192.168.0.1

Specsol
0
 
LVL 11

Expert Comment

by:kabaam
ID: 10646225
Network neighborhood requires the use of netbios namesin win9x machines.  are you attempting to ping by IP or NetBios names?  you can try adding the computers and IP addresses to the other computers lmhost file to resolve name to IP.
0
 

Author Comment

by:specsol
ID: 10656015
Thank you kabaam

I have tried both the IP addresses and the names, with & without LMHOST files to resolve the names. No joy in any case

specsol
0
 
LVL 11

Expert Comment

by:kabaam
ID: 10659155
from both machines
ping 192.168.0.1
ping 192.168.0.2
ipconfig /all

Do you have any type of antivirus running?  I have seen some that have a basic firewall service that blocks these type of comms.
check the workgroup names on both computers.  They need to be the same
0
 

Author Comment

by:specsol
ID: 10665268
No antivirus. Neither machine connects to anything except the other machine -- except even that does not happen!

specsol
0
 

Author Comment

by:specsol
ID: 10665274
I should add that I have now had the crossover cable tested and that is OK

specsol
0
 

Author Comment

by:specsol
ID: 10676499
I have now solved the problem. I had to remove the network adaptor (RealtekRTL8139/810X) from the Device Manager of both machines, remove the driver from Windows/system and the Information file from Windows/Inf/Other. Rebooting then autodetected the cards and installed drivers. System then worked.

My thanks to  LucF and Kabaam for their help

specsol
0
 
LVL 32

Expert Comment

by:LucF
ID: 10676778
Hmm, a forrest through the trees thingy ;-)

Glad you solved your problem.

LucF
0
 
LVL 11

Expert Comment

by:kabaam
ID: 10679254
ditto, glad to hear that you now have you network working like it should.
If you would like a refund of your points, post a zero point question to the Community support Topic area.
Asking for a PAQ/refund as you solved the problem yourself.  Include a link to this question.
good luck,
CHAD
0
 
LVL 1

Accepted Solution

by:
Computer101 earned 0 total points
ID: 11113502
PAQed, with points refunded (125)

Computer101
E-E Admin
0

Featured Post

Turn your laptop into a mobile console!

The CV211 Laptop USB Console Adapter provides a direct Laptop-to-Computer connection for fast and easy remote desktop access with no software to install.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
Michael from AdRem Software explains how to view the most utilized and worst performing nodes in your network, by accessing the Top Charts view in NetCrunch network monitor (https://www.adremsoft.com/). Top Charts is a view in which you can set seve…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question