mikebomb
asked on
Problem with TCP/IP on IEEE 1394 in Windows XP
I have two computers with IEEE 1394 adapters and liked the idea of networking them at 400 Mbps. I bought an IEEE 1394 cable, connected it to both computers, and was in business.
A few weeks ago, something got messed up with one of the computers. The 1394 Connection Status in Network Connections says that it is connected at 400 Mbps, but on the support tab there is no IP address. If you try to repair the connection, you get the message:
Windows could not finish repairing the problem because the following action cannot be completed:
TCP/IP is not enabled for this connection. Cannot proceed.
When you check the connection properties, however, TCP/IP is enabled and is properly set up. I tried running ipconfig /all, and the adapter is not even listed. I tried removing the hardware from the Device Manager and letting Windows find it again, but that did not work. I tried using the command netsh int ip reset [log_file_name] (from the Microsoft KB article 299357) but it did not help. I tried using a utility called WinsockXPFix but it did not help.
I am out of ideas. Does anyone have a solution for me?
A few weeks ago, something got messed up with one of the computers. The 1394 Connection Status in Network Connections says that it is connected at 400 Mbps, but on the support tab there is no IP address. If you try to repair the connection, you get the message:
Windows could not finish repairing the problem because the following action cannot be completed:
TCP/IP is not enabled for this connection. Cannot proceed.
When you check the connection properties, however, TCP/IP is enabled and is properly set up. I tried running ipconfig /all, and the adapter is not even listed. I tried removing the hardware from the Device Manager and letting Windows find it again, but that did not work. I tried using the command netsh int ip reset [log_file_name] (from the Microsoft KB article 299357) but it did not help. I tried using a utility called WinsockXPFix but it did not help.
I am out of ideas. Does anyone have a solution for me?
RPPreacher
Can you uninstall the TCP/IP stack and reinstall? Shot in the dark
Did you you previously configure each computer with a static address or one of the two is running a DHCP service?
One system has an Ip address, but the other does not. Check the configuration of the system that has an IP address on the IEEE1394 interface. Is it manually configured? Do the same for the other and you should have the issue resolved.
One system has an Ip address, but the other does not. Check the configuration of the system that has an IP address on the IEEE1394 interface. Is it manually configured? Do the same for the other and you should have the issue resolved.
ASKER
RPPreacher: You cannot uninstall and reinstall TCP/IP in Windows XP
Arnold: They are both configured for DHCP, but it does not matter if I try to assign an address myself. I can assign the address in the TCP/IP properties for the 1394 Connection, but after I do so, if I go to the connection status and clck the support tab, it still shows that the connection has no IP address.
Arnold: They are both configured for DHCP, but it does not matter if I try to assign an address myself. I can assign the address in the TCP/IP properties for the 1394 Connection, but after I do so, if I go to the connection status and clck the support tab, it still shows that the connection has no IP address.
Something does not jel.
Try the following experiment:
on one computer set the ip of 172.16.1.3 netmask 255.255.255.0 no default gateway.
On the second computer set the IP of 172.16.1.4 netmask 255.255.255.0 no default gateway.
Can you now access the other system from each?
It does not sound as either computer has a DHCP server running, so not sure how you are expecting an IP allocation.
Try the following experiment:
on one computer set the ip of 172.16.1.3 netmask 255.255.255.0 no default gateway.
On the second computer set the IP of 172.16.1.4 netmask 255.255.255.0 no default gateway.
Can you now access the other system from each?
It does not sound as either computer has a DHCP server running, so not sure how you are expecting an IP allocation.
ASKER
Arnold: When there is no DHCP server running, and a connection is set to use DHCP, Windows auto-assigns a private IP address IF TCP/IP IS WORKING CORRECTLY FOR THAT CONNECTION.
You seem to think I am having a problem connecting two computers, the sort that can be fixed by changing IP addresses or netmasks. I am not. The problem I am having is that TCP/IP is NOT working properly for this connection.
Please direct an answer toward the problem I am having, not the one you are imagining I am having.
You seem to think I am having a problem connecting two computers, the sort that can be fixed by changing IP addresses or netmasks. I am not. The problem I am having is that TCP/IP is NOT working properly for this connection.
Please direct an answer toward the problem I am having, not the one you are imagining I am having.
Mike,
Due to lack of information all I and possibly the others who attempt to assist you with your predicament is suggest alteration/adjustments to determine what happens and what to attempt next. Imagination and trial and error is part of troubleshooting. You are the person who has direct access to the systems and the one who can detail the situation. Please do so. Do your systems have windows firewall enabled?
As to your response RPPreacher's suggestion to uninstall and reinstall TCP/IP, all you need to do is remove the TCP/IP from the IEEE 1394 connection i.e. uncheck tcp/IP.
When the DHCP configured windows client is unable to get a DHCP response, they would usually get an IP on the 169.254.x.x IP block. I do not believe the 169.254.x.x segment is a routable private IP block.
Illucidate the issue. Would setting a static IP on the IEEE 1394 interface resolve your problem? Is it not the case that what you are trying to get at is to get your IEEE 1394 connected computers to be able to exchange files?
Due to lack of information all I and possibly the others who attempt to assist you with your predicament is suggest alteration/adjustments to determine what happens and what to attempt next. Imagination and trial and error is part of troubleshooting. You are the person who has direct access to the systems and the one who can detail the situation. Please do so. Do your systems have windows firewall enabled?
As to your response RPPreacher's suggestion to uninstall and reinstall TCP/IP, all you need to do is remove the TCP/IP from the IEEE 1394 connection i.e. uncheck tcp/IP.
When the DHCP configured windows client is unable to get a DHCP response, they would usually get an IP on the 169.254.x.x IP block. I do not believe the 169.254.x.x segment is a routable private IP block.
Illucidate the issue. Would setting a static IP on the IEEE 1394 interface resolve your problem? Is it not the case that what you are trying to get at is to get your IEEE 1394 connected computers to be able to exchange files?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Arnold:
1) Unchecking the TCP/IP does nothing. At some point, I have to re-check it to enable TCP/IP, and when I do, the problem remains.
2) Windows has stopped assigning an IP address to the connection, on the 169.254.x.x block or any others.
3) As I told you in an earlier post, I have tried setting a static IP address. It looks okay in the TCP/IP properties, but when you go to the Status for the connection, on the "Support" tab, all the fields are blank, including IP address. (See http://www.mikebomb.com/imgshare/1394Connection.png for a screenshot of the 1394 Connection Status "Support" tab.) If you try to repair the connection, you get the error message in my original question.
The problem is not with the IP address, but with the fact that Windows is falsely claiming that TCP/IP is not enabled for the connection.
In any case, as my next post will tell you, I have resolved the problem.
1) Unchecking the TCP/IP does nothing. At some point, I have to re-check it to enable TCP/IP, and when I do, the problem remains.
2) Windows has stopped assigning an IP address to the connection, on the 169.254.x.x block or any others.
3) As I told you in an earlier post, I have tried setting a static IP address. It looks okay in the TCP/IP properties, but when you go to the Status for the connection, on the "Support" tab, all the fields are blank, including IP address. (See http://www.mikebomb.com/imgshare/1394Connection.png for a screenshot of the 1394 Connection Status "Support" tab.) If you try to repair the connection, you get the error message in my original question.
The problem is not with the IP address, but with the fact that Windows is falsely claiming that TCP/IP is not enabled for the connection.
In any case, as my next post will tell you, I have resolved the problem.
ASKER
M. Saeedi:
As I wrote in my original question, I had tried the command <b>netsh int ip reset [log_file_name]</b> to no avail, but I had not previously known of the command <b>netsh winsock reset catalog</b>. Since I had run <b>netsh int ip reset [log_file_name]</b> previously, I tried just running <b>netsh winsock reset catalog</b> (and restarting) but that did not resolve the problem. Since it did not resolve the problem on its own, I do not know if it is that command that did the trick, but the problem is now resolved. Here is what finally fixed it:
1) I uninstalled the <b>1394 Net Adapter</b> from Device Manager.
2) I ran the command <b>netsh int ip reset [log_file_name]</b>.
3) I ran the command <b>netsh winsock reset catalog</b>.
4) I restarted my computer.
When the computer restarted, it reinstalled the 1394 Net Adapter and assigned it an IP address in the 169.254.x.x block, as it was supposed to. Since my other computer also has an address on that block, and since both computers have the netmask of 255.255.0.0, the two are able to communicate over the IEEE 1394 cable, as they are supposed to.
Since your answer was closest, and since you provided me with a step that I had not previously known about, I am giving you the points.
Thanks!
Mike Bomb
As I wrote in my original question, I had tried the command <b>netsh int ip reset [log_file_name]</b> to no avail, but I had not previously known of the command <b>netsh winsock reset catalog</b>. Since I had run <b>netsh int ip reset [log_file_name]</b> previously, I tried just running <b>netsh winsock reset catalog</b> (and restarting) but that did not resolve the problem. Since it did not resolve the problem on its own, I do not know if it is that command that did the trick, but the problem is now resolved. Here is what finally fixed it:
1) I uninstalled the <b>1394 Net Adapter</b> from Device Manager.
2) I ran the command <b>netsh int ip reset [log_file_name]</b>.
3) I ran the command <b>netsh winsock reset catalog</b>.
4) I restarted my computer.
When the computer restarted, it reinstalled the 1394 Net Adapter and assigned it an IP address in the 169.254.x.x block, as it was supposed to. Since my other computer also has an address on that block, and since both computers have the netmask of 255.255.0.0, the two are able to communicate over the IEEE 1394 cable, as they are supposed to.
Since your answer was closest, and since you provided me with a step that I had not previously known about, I am giving you the points.
Thanks!
Mike Bomb