Billc13
asked on
local area connection will not send or receive
I just reformated my friends laptop. It's a CTX EXBook 700e series. She was running winme before and I put winxp pro on it. The whole install went fine and everything works fine exept for it not being able to connect to the internet or my network in my house.
When I look at the local area connection, send and receive are both at 0 and never move. The ip address seems to be locked on the 196.x.x.x. If I put a static ip in it still does not work, but it does show the ip and everything else when i look in the local area connection. The ip, gateway, subnet mask, and dns are right because i've set other computer up on the network using the same ones.
Does anyone have any idea on how i can get it to start sending and receiving?
When I look at the local area connection, send and receive are both at 0 and never move. The ip address seems to be locked on the 196.x.x.x. If I put a static ip in it still does not work, but it does show the ip and everything else when i look in the local area connection. The ip, gateway, subnet mask, and dns are right because i've set other computer up on the network using the same ones.
Does anyone have any idea on how i can get it to start sending and receiving?
also try this winsock fix
http://www.spychecker.com/program/winsockxpfix.html
and check for any firewalls, and make sure they are configured correctly (including the built in one on xp and any included with the anti virus program)
http://www.spychecker.com/program/winsockxpfix.html
and check for any firewalls, and make sure they are configured correctly (including the built in one on xp and any included with the anti virus program)
all that said.. it could be something simple..
you say the IP is the same as the others.. you have the host address different that the other computer right?
You said 'exept for it not being able to connect to the internet or my network in my house' ... so you dont even get a connection?
do you have a dhcp server (router/server, etc?) that gives out IP's? or as you said, just setting static for all the computers?
Because if you are setting a static address of 196.x.x.x, that is a public IP address.. do you mean to set it up as 192.168.x.x?
you say the IP is the same as the others.. you have the host address different that the other computer right?
You said 'exept for it not being able to connect to the internet or my network in my house' ... so you dont even get a connection?
do you have a dhcp server (router/server, etc?) that gives out IP's? or as you said, just setting static for all the computers?
Because if you are setting a static address of 196.x.x.x, that is a public IP address.. do you mean to set it up as 192.168.x.x?
ASKER
Thanks for the fast replys. I will try the winsock fix tomorrow.
I have a linksys router that has dhcp enabled on it, but the computer in my network are all assigned static ip's. 192.168.1.100 up to .104. So the laptop should get the address 192.168.1.105, but it's getting a address like: 192.254.254.1. Something like that, I can't remember the exact address off hand. When i put that address in staticly it stays set, but it will not connect to the internet or to the lan. The only thing i can ping is the loop-back address. No internet address or any address's on my network will work.
Like I said, tomorrow when i get the laptop back i will run the winsock fix and if that doesn't work i will try resetting the tcp/ip stack.
Thanks again for your time
I have a linksys router that has dhcp enabled on it, but the computer in my network are all assigned static ip's. 192.168.1.100 up to .104. So the laptop should get the address 192.168.1.105, but it's getting a address like: 192.254.254.1. Something like that, I can't remember the exact address off hand. When i put that address in staticly it stays set, but it will not connect to the internet or to the lan. The only thing i can ping is the loop-back address. No internet address or any address's on my network will work.
Like I said, tomorrow when i get the laptop back i will run the winsock fix and if that doesn't work i will try resetting the tcp/ip stack.
Thanks again for your time
This really sounds like a driver problem. I believe the laptop has assigned an automatic external IP as it cannot get to the LAN.
Does the automatic address begin with 169.254? If so, you should try the latest driver for the network card/laptop. IP addresses in the 169.254 range are being assigned to the machine by XP when it can't communicate with the DHCP server.
Other things to check are the network cable and to try a different network port on the linksys (preferably one you know works)
Does the automatic address begin with 169.254? If so, you should try the latest driver for the network card/laptop. IP addresses in the 169.254 range are being assigned to the machine by XP when it can't communicate with the DHCP server.
Other things to check are the network cable and to try a different network port on the linksys (preferably one you know works)
ASKER
Your right, I just doubled checked with my friend on the ip and it does start with 169.254.x.x.
I've tried every driver I could find for the nic with no luck.
The nic she has is the linksys pcm100. It's not the new version. I also have a PCMPC100 linksys card that is brand new with the driver disk and that doesn't work as well. My thought was that the problem might have been with the pcmcia drivers. Winxp most have installed them my it's selft. In device manager it says Texas Instruments PCI-1131. Does any one know if these are the right drivers for the CTX EZ-Book 700e series?
The linksys router i have works fine. All the ports work and it is assigning ip address to dhcp clients perfectly.
I still haven't tried the winsock fix or resetting the tcp/ip stack, but will later.
Any more idea's would be greatly appreciated.
Thanks again
I've tried every driver I could find for the nic with no luck.
The nic she has is the linksys pcm100. It's not the new version. I also have a PCMPC100 linksys card that is brand new with the driver disk and that doesn't work as well. My thought was that the problem might have been with the pcmcia drivers. Winxp most have installed them my it's selft. In device manager it says Texas Instruments PCI-1131. Does any one know if these are the right drivers for the CTX EZ-Book 700e series?
The linksys router i have works fine. All the ports work and it is assigning ip address to dhcp clients perfectly.
I still haven't tried the winsock fix or resetting the tcp/ip stack, but will later.
Any more idea's would be greatly appreciated.
Thanks again
ASKER
The winsock fix and resetting the tcp/ip stack did no work. Still the same problem, send and receive are at 0.
If you think the drivers still could be a problem, the up to date drivers for both cards are at these sites..
For yours - http://www.linksys.com/download/driver.asp?dlid=19
For hers - http://www.linksys.com/download/driver.asp?dlid=28
Otherwise.. If you set everything to default, (TCP/ip - all IP's set to obtain automatically..) what do you get when you do an ipconfig in cmd prompt? is that when you get an ip of 169.x.x.x? or do you get that as well when you have a static ip set to 192.168.x.x?
sorry just trying to understand exactly when you get the ip of 169..
For yours - http://www.linksys.com/download/driver.asp?dlid=19
For hers - http://www.linksys.com/download/driver.asp?dlid=28
Otherwise.. If you set everything to default, (TCP/ip - all IP's set to obtain automatically..) what do you get when you do an ipconfig in cmd prompt? is that when you get an ip of 169.x.x.x? or do you get that as well when you have a static ip set to 192.168.x.x?
sorry just trying to understand exactly when you get the ip of 169..
ASKER
Sorry for not being to clear on my problem.
I have the updated drivers from the linksys site and neither of them worked. I think the drivers for the NIC are ok.
I get the 169.x.x.x address when it's set to obtain automatically. When I set a static ip, the static ip I set (192.168.1.105) shows up in cmd when i do ipconfig. The default gateway and dns are also right when i do ipconfig.
The network card plugs into the pcmcia slot. Do you think the drivers for that could be wrong? I stated the drivers that winxp installed on it's own above.
(at least I believe it's called the pcmcia slot?)
I have the updated drivers from the linksys site and neither of them worked. I think the drivers for the NIC are ok.
I get the 169.x.x.x address when it's set to obtain automatically. When I set a static ip, the static ip I set (192.168.1.105) shows up in cmd when i do ipconfig. The default gateway and dns are also right when i do ipconfig.
The network card plugs into the pcmcia slot. Do you think the drivers for that could be wrong? I stated the drivers that winxp installed on it's own above.
(at least I believe it's called the pcmcia slot?)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ok, i know this might seem like going back to what was said before..
but what happens to the other computers if you set it to get an address automatically?
eg, comp 1 is the problem PC, what happens if you set comp 2 (which is working fine) to obtain IP via dhcp?
If it gets an IP no problem, then we can say that DHCP is working fine... if not, then you know the problem is with DHCP...
but what happens to the other computers if you set it to get an address automatically?
eg, comp 1 is the problem PC, what happens if you set comp 2 (which is working fine) to obtain IP via dhcp?
If it gets an IP no problem, then we can say that DHCP is working fine... if not, then you know the problem is with DHCP...
ASKER
All the other computer can receive a dhcp address fine if set to do so. I think avpwest might be right about it not being able to support winxp. I don't think it supports win2000 either because I tried that and had the same problems.
Tomorrow i'm going to get my hands on a usb ethernet card and give that a shot. If that doesn't work I guess it's back to winme.
Thanks again
Tomorrow i'm going to get my hands on a usb ethernet card and give that a shot. If that doesn't work I guess it's back to winme.
Thanks again
dear are you able to ping 127.0.0.1 and ur ip address of the PC itself if yes then the NIC is ok
next check the physical link of the PC i mean the wire may be thats the problem though silly
next remove the cable and put it back again
still if no luck
check the power setting on th NIC sometimes its set to Auto Power save in the properties of the NIC u will find them
let me know i will advise u further
next check the physical link of the PC i mean the wire may be thats the problem though silly
next remove the cable and put it back again
still if no luck
check the power setting on th NIC sometimes its set to Auto Power save in the properties of the NIC u will find them
let me know i will advise u further
ASKER
Yes I can ping the loop back address and 192.168.1.105 if i set it staticly.
The cable is good because I checked it on a working box.
The nic is getting power because all the lights are on.
I'm going to try a usb card later today to see if that helps.
I really think avpwest is right about the ctx 700 series not being able to support xp or win2000.
Thanks again guys for all the replys, it's greatly appreciated.
The cable is good because I checked it on a working box.
The nic is getting power because all the lights are on.
I'm going to try a usb card later today to see if that helps.
I really think avpwest is right about the ctx 700 series not being able to support xp or win2000.
Thanks again guys for all the replys, it's greatly appreciated.
ASKER
Got a USB card and things are running good now. Thank you all for trying to help.
I assume that is not the correct network?
try rebuilding the tcp stack
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q299357
How to Reset Internet Protocol (TCP/IP) in Windows XP
View products that this article applies to.
This article was previously published under Q299357
For a Microsoft Windows Server 2003 version of this article, see 317518.
SUMMARY
When viewing the list of components for a network interface, you may notice that the Uninstall button is disabled when Internet Protocol (TCP/IP) is selected. In Windows XP, the TCP/IP stack is considered a core component of the operating system; therefore, it is not possible to uninstall TCP/IP in Windows XP.
In extreme cases, reinstalling the Internet Protocol stack may be the most appropriate solution. With the NetShell utility, you can now reset the TCP/IP stack back to a pristine state, to the same state as when the operating system was installed.
MORE INFORMATION
The NetShell utility (netsh) is a command-line scripting interface for the configuring and monitoring of Windows XP networking. This tool provides an interactive network shell interface to the user.
In Windows XP, a reset command is available in the IP context of the NetShell utility. When this command is executed, it rewrites pertinent registry keys that are used by the Internet Protocol (TCP/IP) stack to achieve the same result as the removal and the reinstallation of the protocol.
SYSTEM\CurrentControlSet\S
SYSTEM\CurrentControlSet\S
Command Usage
netsh int ip reset [log_file_name]
To successfully execute the command, you must specify a log file name where actions taken by netsh will be recorded. For example, typing either of the examples that are listed in the "Command Samples" section later in this article at a command prompt would reset the TCP/IP stack on a system and record the actions that were taken in the log file, Resetlog.txt. The first sample creates the log file in the current directory, while the second sample demonstrates the use of a path where the log will be created. In either case, where the specified log file already exists, the new log will be appended to the end of the existing file.
Command Samples
netsh int ip reset resetlog.txt
netsh int ip reset c:\resetlog.txt
Sample Log File for NETSH INT IP RESET
The following is a sample of the log file that is generated by netsh when an IP reset command is issued. The actual log file may vary depending on the configuration of the system on which the command is issued. In some cases, there may be no actions logged in the file, which typically is the case when the TCP/IP registry keys have not been altered from their original configuration.
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
SYSTEM\CurrentControlSet\S
SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
10.1.1.2
deleted SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
reset SYSTEM\CurrentControlSet\S
old REG_DWORD = 0
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
reset SYSTEM\CurrentControlSet\S
old REG_DWORD = 0
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
12.12.12.12
deleted SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
0
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
255.255.255.0
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
0
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
0
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
reset SYSTEM\CurrentControlSet\S
old REG_DWORD = 0
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
added SYSTEM\CurrentControlSet\S
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
10.1.1.2
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
0
added SYSTEM\CurrentControlSet\S
reset SYSTEM\CurrentControlSet\S
old REG_DWORD = 0
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
10.1.1.1
deleted SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
reset SYSTEM\CurrentControlSet\S
old REG_SZ = 10.1.1.2,10.1.1.3
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
0
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
255.255.255.0
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
0
reset SYSTEM\CurrentControlSet\S
old REG_MULTI_SZ =
0
deleted SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
deleted SYSTEM\CurrentControlSet\S
<completed>
method 2
Had to point the Install to the "nettcpip.inf" in the windows/inf directory. That allows TCP/IP to install over the top of the TCP/IP required for operation of Windows XP.