XP Networking

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hope someone out there can shine a bit of light on this problem

I am trying to get two system to share files via a cross over cable, I run
the network setup wizard giving each system a different name, but putting
each in the same workgoup.
Windows genirates an IP on each system, but they can't talk to each other
(169.254.93.130 & 169.254.164.224)
The cable is OK, the system are clean re-builds, file sharing is enabled.
Any thoughts???
 
In Narked <[email protected]> had this to say:

My reply is at the bottom of your sent message:
Hope someone out there can shine a bit of light on this problem

I am trying to get two system to share files via a cross over cable,
I run the network setup wizard giving each system a different name,
but putting each in the same workgoup.
Windows genirates an IP on each system, but they can't talk to each
other (169.254.93.130 & 169.254.164.224)
The cable is OK, the system are clean re-builds, file sharing is
enabled. Any thoughts???
Click to expand...

I just went through this on a 2k box. The 169.254 usually indicate corrupted
Winsock. Have you tried assigning one an IP address of 192.168.0.1 and the
other as 192.168.0.2? If not you can try that. There's an easy method to fix
Winsock with XP SP2 but just in case here's the hard way.

Start
Run
Type "regedit" without the quotes
Hit Enter
Delete both of these keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2

Reboot.

Start
Settings
Control Panel
Classic View
Network Connections
Right click on your LAN
Select Properties
Click Install
Protocol
Select TCP/IP
Click okay a couple of times.
Reboot.

This should do the trick for you.

Galen
--

"And that recommendation, with the exaggerated estimate of my ability
with which he prefaced it, was, if you will believe me, Watson, the
very first thing which ever made me feel that a profession might be
made out of what had up to that time been the merest hobby."

Sherlock Holmes
 
"Galen" said:
In Narked <[email protected]> had this to say:

My reply is at the bottom of your sent message:


I just went through this on a 2k box. The 169.254 usually indicate corrupted
Winsock. Have you tried assigning one an IP address of 192.168.0.1 and the
other as 192.168.0.2? If not you can try that. There's an easy method to fix
Winsock with XP SP2 but just in case here's the hard way.

Start
Run
Type "regedit" without the quotes
Hit Enter
Delete both of these keys:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Winsock2

Reboot.

Start
Settings
Control Panel
Classic View
Network Connections
Right click on your LAN
Select Properties
Click Install
Protocol
Select TCP/IP
Click okay a couple of times.
Reboot.

This should do the trick for you.

Galen
Click to expand...

I don't think that the 169.254x.x addresses mean that anything is
wrong. Those addresses indicate that:

1. The network connections are configured to obtain an IP address
automatically, and:

2. There isn't a DHCP server on the network to assign an IP address.

That situation is quite common. A DHCP server would only be present
in Narked's crossover cable network if he has enabled Internet
Connection Sharing on one of the computers.

The most likely reason that the computers can't talk to each other is
that a firewall is blocking access.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
In Steve Winograd [MVP] <[email protected]> had this to say:

My reply is at the bottom of your sent message:
I don't think that the 169.254x.x addresses mean that anything is
wrong. Those addresses indicate that:

1. The network connections are configured to obtain an IP address
automatically, and:

2. There isn't a DHCP server on the network to assign an IP address.

That situation is quite common. A DHCP server would only be present
in Narked's crossover cable network if he has enabled Internet
Connection Sharing on one of the computers.

The most likely reason that the computers can't talk to each other is
that a firewall is blocking access.
Click to expand...

I'd like to hope you're right on that. It's one of those cases where I had
hoped the OP would post back, those cases seem to be getting more and more
rare these days. In this day and age I've become sadistic in my thinking, or
fatalistic if you will. It seems more and more problems crop up due to
malware and, unfortunately, Winsock is one of the innocent bystanders
commonly shot in the battle of good vs. evil. Perhaps they'll post back soon
and let us know what worked and what did not.

Galen
--

"And that recommendation, with the exaggerated estimate of my ability
with which he prefaced it, was, if you will believe me, Watson, the
very first thing which ever made me feel that a profession might be
made out of what had up to that time been the merest hobby."

Sherlock Holmes
 
Back
Top