| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 32308 | 2003-04-15 05:03:00 | 2 network questions.. | rayonline (2134) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 135937 | 2003-04-15 05:03:00 | hey, I think i have isolated the network issues to the laptop. as when u changed the internal LAN to PCMCIA it works fine, without changing the other PC's configuration. now.. Q1. The internal card (hidden under keyboard) works using a straight cable without faults - superbly. When I use a crossover cable I get continous time-outs. I tried pinging and its says host destination time-out, 100% packet lost. It was able to ping itself OK. What is wrong here?? Is it the card or the RJ45 socket?? Q2. Does more $$ cards connect better than others?? PS. I have also tried changing drivers (6 abouts) and updating the firmware. Both of these were confirmed so they were gone via properly. Ray |
rayonline (2134) | ||
| 135938 | 2003-04-15 05:19:00 | Q1: A crossover cable swaps the transmit and recieve pairs. This will cause you to transmit packets to the transmit driver of a hub, and you won't gett any acknowledgements, because transmitters don't receive, and you are listening to the hub's receive input with your receive input --- receivers don't transmit. :D Pinging "localhost" or 127.0.0.1 tests the TCP/IP software. It doesn't test the hardware. You would need different test software, and a RJ45 loopback connector. Manufacturer's test software usually wants another card to talk to. Q2: Sometimes. :D |
Graham L (2) | ||
| 135939 | 2003-04-15 05:32:00 | If you're wanting to set it up P2P, then try rebooting, as sometimes PC's have a hard time going from using a crossover cable between 2 PC's to using a Straight-thru cable to a switch/Hub. The more expensive cards may have support for older OS's... but then again coz they're newer, they may need special drivers and all... My 2 cents worth :-) But really... I agree with Graham :-) |
Chilling_Silence (9) | ||
| 135940 | 2003-04-15 11:16:00 | i have tried those manufactuer's test to no success. i hooked up my desktop to the laptop via a cross-over cable. i have tried, win2k, winxp now and later will try win98se using the original recovery cd. i am not a 9x fan. i immediately put win2k on the 1st week i bought the laptop! i have tried endless amount of reboots, i have had this issue since last yr june. i have never used cross cable to success before. i have only used the straight cable at work, at home the modem. since i was unable to use cross cable at home, i have resorted to a cd writer with a cdrw disc and taken turns to engage the telephone line so i could go online and someone else could use the desktop when i was not using it. pple are puzzled incl a service centre who quoted me $120 per hr and cannot give me how many hrs needed. it was working at work and why not at home?? that is despite the diff cable design. i am pretty sure the settings are the same - hence that i installed a pcmcia card and it worked fine with the desktop. the issue is with the internal lan on laptop. |
rayonline (2134) | ||
| 135941 | 2003-04-15 22:05:00 | i have tried winxp to no success. exactly the same problems as b4 - timeouts even copying one 0.5MB file. It takes like 2minutes jus to browse the remote computer under network neighborhood. I am, not going to try win98se. i tried pining: laptop to desktop: i get host unreachable 100% packet loss. desktop to laptop: i get host time-out. 100% packet loss. when the laptop uses a PC Card; pinging works fine. the desktop is unchanged. i believe the faulty part is the laptop's lan card. the laptop is unable to search or locate the desktop. the desktop is working and has tried to contact the laptop since the laptop is faulty it is not getting a reply back so hence it gets a time-out signal when the laptop does not reply back. maybe it is the transmitters thingee that cross-over does diff with straight cable. this maybe is where the fault lies.... |
rayonline (2134) | ||
| 135942 | 2003-04-15 22:50:00 | im just making a shot in the dark here but.... is the IP on the laptop configured the same as the PC's? eg are they both set to Automatic?????, or have u assigned them? to put the Laptop and the PC in the same LAN i think u have to have ips with the same numbers eg... 192.168.0.69 and 192.168.0.45, the 0 being the same, and having the last 2 numbers different, (dont ask me who's those IP's addys are, i made em, up :) ), have u tryed just setting the TCP/IP settings to Automatic? try refreshing and renewing the IP's on both machines, CMD then type ipconfig (enter) then ipconfig /release (enter) then ipconfig /renew...., if im wrong then im wrong, but i have used these troubleshooting methods on my home network and woth crossovers, and it works.... most of the time :D |
Jams (1051) | ||
| 135943 | 2003-04-16 03:57:00 | yes i have tried auto and manual. every case was confirmed with ipconfig and winipcfg. the internal laptop lan card still failed. the pcmcia card worked great doing the same stuff as the internal lan. the ip addresses were the same with the last number different. same mask and gateway..... i am sure these settings are right. i also have all the protocols installed, again they were same as the pcmcia card which was working fine. they are on the same workgroup, diff comp name, something shared on each computer. i can see them takes like 2mins to access the other comp in network neighbourhood. when i copy like 0.5MB it times out. win2k consistently shows network cable disconnect/connect/discon.... repeatedly. then after some time the whole copying process of that 0.5MB just gives up. not saying it won't work, 0.5MB copying prob takes 5 tries to get one job done and takes about 3mins to be done. the issue has always been the crossover connection with the laptop internal lan. |
rayonline (2134) | ||
| 135944 | 2003-04-16 05:30:00 | Your first posting omitted the most important information ... the fact that you were moving the computer X miles between the two configurations and the other end of the straight and cross cables were going to two different computers/systems . ;-) Have you tried another crossover cable? There might be one broken wire in that cable ... and a cable with a broken wire might work for one Ethernet card and not for another. |
Graham L (2) | ||
| 135945 | 2003-04-16 05:54:00 | yap - tried 2nd cable already. same response... yes i have moved my laptop from one area to the next. ie.. work to home to work to home repeatedly. has always worked at work with straight cable. never at home with cross-over (the 2nd cable). the crossover cable worked with the pcmcia card i had for a while. i am looking in to fixing the internal card method... i only have one pcmcia slot - so they are precious rather keep it free ;) |
rayonline (2134) | ||
| 135946 | 2003-04-16 06:05:00 | A hub should fix this, but we shouldn't have to go that far. :D Are the crossover cables from a "reputable" source? If you hold the two plugs up side by side, with the cables down and the contacts facing you, the pin numbers go 1..8 (left.. right). You should be able to see the colours on the wires inside the plugs. pin 1 should be connected to pin 3 on the other plug; pin 2 to pin 6; pin 3 to pin 1; pin 6 to pin 2. Those are the only wires which matter. It is not unknown for people to make cables wrong. Such cables usually don't work (that's the good case). Sometimes they work some of the time (that's the bad case). |
Graham L (2) | ||
| 1 2 | |||||