| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 30923 | 2003-03-07 01:57:00 | Network link load failure | Bolta (3305) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 126122 | 2003-03-07 01:57:00 | Question: I have created a peer to peer network using Windows ME and Windows 95 using Create 8139 PCI cards. Both devices show as being Realtek RTL 8139 (A/B/C/8130) PCI Fast Ethernet. The original drivers supplied on the accompanying diskette did not appear to work together and those which were downloaded from the Realtek site failed as well but eventually additional drivers supplied by the Intel Chipset Motherboard Utility supplied with the ME machine worked. The Realtek diagnostics program (1.7) defines these as Realtek 8139-series PCI NIC for the ME machine with that on the 95 machine as being NDIS4. Protocols loaded are TCP/IP using 169.254.x.x and NetBUI on both machines. Client is Microsoft for Networks and File and Printer Sharing for Microsoft Networks. The problem is that whenever either machine is started/restarted the link cannot be reestablished unless the cable is physically disconnected then re-connected on the 95 machine. The ME machine tries to connected as 'Detect Network Media' is checked (on) but the card in the 95 machine just will not. Any ideas? Peter |
Bolta (3305) | ||
| 126123 | 2003-03-07 02:34:00 | > eventually additional drivers supplied by the Intel Chipset Motherboard Utility supplied with the ME machine worked. another words the motherboard drivers where never installed. check both pc's have had the motherboard drivers installed. makes installing cards a whole lot easier. ip addy i normally use is 192.168.0.xxx i used to use NetBUI but had some trouble similer to what u have. i changed it over to ipx/spx (with netbios over ipx/spx enabled) for the fileshareing. http://www.wown1.com handy site :) |
tweak'e (174) | ||
| 126124 | 2003-03-07 09:52:00 | For the link lights not to show may indicate a speed mismatch.. Try adjusting the cards to both have 10megs at half duplex and work your way up from there...if it works at 10megs but not 100 there may be a cable issue. The only reason you should have ipx is for playing the original "Doom" game otherwise stick to tcp/ip...secondly if you insist on using 196.254.x.x make sure your subnet mask is 255.255.0.0 but this should not affect your link.. ==orac== |
Orac (656) | ||
| 126125 | 2003-03-07 10:18:00 | >The only reason you should have ipx is for playing the original "Doom" game otherwise stick to tcp/ip... there is actually a reason for running ipx or netbui instead of tcp/ip apart from games. i suspect bolta is already aware of it. |
tweak'e (174) | ||
| 126126 | 2003-03-07 11:05:00 | netbeui--yes IPX--na why would anyone still work with that? ==orac== |
Orac (656) | ||
| 126127 | 2003-03-07 11:48:00 | because netbeui is windows only and tends to flood larger networks, its not installed by default with XP (which says something about it as MS usually likes to shove MS standards down our throats) however is very easy to set up . ipx/spx is still fast can handle larger networks far better than netbeui . i just find its less troublesome than netbeui . it may be old but it still works very well . also other non-ms os's can use it . |
tweak'e (174) | ||
| 126128 | 2003-03-07 20:21:00 | i still fail to see why it is necessary to run multiple transmission protocols in a windows enviroment in todays age. Yes different protocols had there advantages and disadvantages but in reality TCP/IP is all you need and now runs across multiple os platforms including apple with release of osx . In a troubleshooting situation it is a lot easier to fault find if only one protocol is being used. ==orac== |
Orac (656) | ||
| 126129 | 2003-03-07 22:19:00 | Additional Info: NetBeui was purely due to the fact that it is recommended as it is the simplest and easiest protocol to use. As both machines contain modems I do not require "Internet Connection Sharing" hence the use of 169.254.x.x. addresses. Subnet used is 255.255.0.0 as recommended with this address range. Also use of 'static' addresses eliminates the requirement for priority starting of a DHCP server to allocate automatically assigned addresses. IPX can not be used as the ME machine returns "The following error occurred while loading protocol number 0. Error 254". Both cards auto negoiate @ 10megs/half duplex so I don't think this is an issue. Progress: After establishing the link via physical disconnection I removed the bindings for NetBeui on the 95 machine and then restarted. The link was was reinstated. I then removed the same on the ME machine and the link failed. Consequently I have therefore removed Netbeui from both machines. I now think that the problem probably is with the ME machine and not the 95 as first suspected. Thanks for the info to date, any more would be appreciated. |
Bolta (3305) | ||
| 126130 | 2003-03-07 22:51:00 | have a look here (support.microsoft.com) also with ipx you need to specify the frame type (802.3) and the network address has to be the same. the advantage of running dual protocols is if you hae a tweaked out net connection the tcp/ip lan speed can be limited to, for eg, 7kB/s. also ipx or netbeui will bypass any firewalls and is not routable over the net makeing the rather insecure windows networking a little bit more secure. i'm fairly sure those cards are 10/100 so you may have a crook cable which is why they would auto negoiate down to 10mb/s. |
tweak'e (174) | ||
| 1 | |||||