LAN etc.

[JimL]

After surviving a multi-headed attack from the nether worlds (ZLOB, and several others) I ended up with both my LAN and my wireless non-functional. Both computers say everything is installed right, but neither can find the network path to the other. On a networking newsgroup all I can get is confusing instructions on how to dig around in winsock whatever that is, etc., etc., something that I've never been able to get.

Has the method of un-installing networking completely and letting the system install networking pretty much automatically been eliminated at the XP Pro level? I can't even find a place where the IP address is stored - easy enough in Win98.

TIA

[sjthinkpader]

May be the firewall is enabled in the network connection properties?

[JimL]

May be the firewall is enabled in the network connection properties?

I knew I had made some changes in firewall configurations so the first thing I did after the networks disappeared was to turn off the firewall.

The LAN and Wireless had worked before with the firewall on, but now neither works with the firewall either on or off.

I get messages saying this and that is working fine - from both the TP and the desktop, but both computers say they can't find the network path now.

I went to see if the IP addresses were correct and I can't even find anything with IP addresses listed, let alone being editable. Either XP is very, very different from Win98 or some features have disappeared.

Hmmmmmmm. I decided to double check the firewall. It turned out that something had messed with the Windows firewall. The primary security notifier said it was off, but 3 different things were firewall protected in advanced settings. I turned those off, but still nothing. I turned off my own firewall at the same time - still nothing. Path still not found.

[sjthinkpader]

From the Start menu, select Connect To, then Show all connections.

Right click on the Connection icon you want and select Properties.

In the scroll list select TCP/IP then click Properties.

[ThaDon]

I've seen a similar issue, I'd recommend running the following command from the command line [START -> RUN -> CMD]

netsh int ip reset c:\resetlog.txt

You will need to restart your PC immediately after.

REF: http://support.microsoft.com/default.aspx/kb/299357

[JimL]

From the Start menu, select Connect To, then Show all connections.

Right click on the Connection icon you want and select Properties.

In the scroll list select TCP/IP then click Properties.

Thank you very much.

Interestingly, when I select TCP/IP the Properties button is grayed out. Assuming this means it is not installed, I click Install.

From there I get questions asking what I want to install - as if I hadn't already selected TCP/IP. I select Protocol and get one item on the pick list - Microsoft Network Monitor Driver. I have no clue what this is or means, my typical problem when dealing with networking - its cryptic screen choices.

[ThaDon]

The screen option you're getting is perfectly normal.

Tell you what, go to Command Prompt, then type:

IPCONFIG /ALL

Please paste your response on here.

TIP: To copy, right click on Command screen, choose SELECT ALL, then press ENTER on your keyboard. That saves it into memory, then RIGHT CLICK into here, or CTRL + V.

[JimL]

I've seen a similar issue, I'd recommend running the following command from the command line [START -> RUN -> CMD]

netsh int ip reset c:\resetlog.txt

You will need to restart your PC immediately after.

REF: http://support.microsoft.com/default.aspx/kb/299357

Thanks. Interestingly enough, there was no c:\resetlog.txt in existance, but I ran the line you suggested and one appeared. However - no joy.

[JimL]

The screen option you're getting is perfectly normal.

Tell you what, go to Command Prompt, then type:

IPCONFIG /ALL

Please paste your response on here.

C:\Documents and Settings\Jim LaLone>IPCONFIG /ALL

Windows IP Configuration

Host Name . . . . . . . . . . . . : LAPTOP
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

PPP adapter isp.com:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 12.77.184.7
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 12.77.184.7
DNS Servers . . . . . . . . . . . : 205.208.227.13
205.208.227.14
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%4
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6to4 Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 0C-4D-B8-07
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 2002:c4d:b807::c4d:b807
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 0C-4D-B8-07
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:12.77.184.7%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Documents and Settings\Jim LaLone>


Thanks.

What is that IP address? It is DEFINITELY not either the laptop or the desktop address I used previously. That's a puzzle. I've never found a place to actually check up on whether the IP address is the same as my desktop. If it is wrong that would seem to me to explain why the path cannot be found. But I find no place to edit it.

I'm not conversant on protocols, but it looks odd the see NetBIOS on TCP/IP disabled.

[JimL]

The screen option you're getting is perfectly normal.

Are you saying it is normal for the TCP/IP properties to be grayed out?

Thanks

[ThaDon]

The properties button should not be greyed out.

How are you connecting to the internet via ISP.COM? If you go to www.whatismyip.com does the IP address you're presented with correspond with 12.77.184.7?

[JimL]

The properties button should not be greyed out.

How are you connecting to the internet via ISP.COM? If you go to www.whatismyip.com does the IP address you're presented with correspond with 12.77.184.7?

I connect on dial-up.

You're right. That was my internet IP, apparently assigned by isp.com. (It is currently slightly different) I just don't understand why that is even coming up when the problem is LAN - specifically, "The network path was not found."

I've had no problem connecting with the internet.

Hm, my bad? I just did IPCONFIG /ALL again, but without being connected to the internet. All I get that way is:

"Windows IP Configuration," one line.

I've tried PINGing my desktop address and, according to my firewall software (Zone Alarm) it is looking for it on the internet. The same is true of my FTP program which I often used in the past to transfer files to the laptop from the desktop. When I tell it to connect to the desktop IP address (via previously functional setup), I immediately get word from the firewall that it is trying to connect to the internet, then the FTP program tells me "Failed to connect", whether I permit or deny via the firewall.

Thanks again.

[sjthinkpader]

Are you connected directly to the DSL modem or thru a router in between?

If you are directly connected, then the carrier DSLAM and BRAS will assign the IP address. This will appear as PPPoE connection and your PC will be the public (WAN) IP address holder.

Normally either the DSL modem or the router will be the public (WAN) IP address holder (DNS server addresses too).

Your LAN side either has to have a DHCP server or a fixed IP address assigned in the NIC TCP/IP profile to work.

[JimL]

Are you connected directly to the DSL modem or thru a router in between?

I'm on dial-up. My network hardware consists of nothing but a crossover cable between the laptop and the desktop and which worked fine for a couple years.

Your LAN side either has to have a DHCP server or a fixed IP address assigned in the NIC TCP/IP profile to work.

I'm not at all certain what you just said. As fas as I know I have never had DHCP. While the LAN was working the desktop on the other end of the crossover cable was 192.168.1.1 and I seem to recall that the laptop was 192.168.1.2, but as I have said, I can't even find a place where there are any IP addresses listed (or settable) as they were in Win98. And no one has ever suggested where such settings might be found in XP.

As for NIC TCP/IP profile, quite frankly I have yet to see any kind of profile on any part of this LAN. The only thing about networking in Control Panel merely installs something with no configuration input that I have ever noted. (If someone suggests configuring via command line I may have to hire Dr. Kavorkian)

On my 770 with win98 I could go through Device Manager and find all kinds of network/LAN settings, but not with XP on this T42.

Thank you

[sjthinkpader]

Ok, I had to go back and re-read what you said.

...
Interestingly, when I select TCP/IP the Properties button is grayed out. Assuming this means it is not installed, I click Install.

From there I get questions asking what I want to install - as if I hadn't already selected TCP/IP. I select Protocol and get one item on the pick list - Microsoft Network Monitor Driver. ....

What I do this same procedure on my computer, along with Microsoft Network Monitor Driver, it shows Microsoft TCP/IP version 6 in the list. But you are missing this entry.

I would suggest to delete the NIC driver from system properties, then reboot and let the system install the NIC driver again. Download the latest ethernet NIC driver and have it in the c:\drivers directory before you start.

[ThaDon]

Have you tried looking in Device Manager -> Network Adapters -> Intel Pro/1000? Anything listed here?

If not anything under Other Devices?

[JimL]

I would suggest to delete the NIC driver from system properties, then reboot and let the system install the NIC driver again. Download the latest ethernet NIC driver and have it in the c:\drivers directory before you start.

Could you suggest what "latest" might mean and where to get it?

At the IBM/Lenovo site the latest driver was dated 2005, one year newer than what I had. I found another site with one marked 2007. I got that and ran the installation.

Now there is no longer one line in the TCP/IP -> Install -> Protocol -> Add list. In fact I don't get a list now. I get a message saying there are no drivers at all for Protocols.

Also now, running Network Install Wizard ends with:

"An error occurred during configuration of the network on this computer" and the suggestion that I install it manually.

I ran the Repair option and got:

"Renewing your IP address."

"Following action cannot be completed"

"Renewing your IP address."


Thanks

[JimL]

Have you tried looking in Device Manager -> Network Adapters -> Intel Pro/1000? Anything listed here?

If not anything under Other Devices?

I can't tell for sure what you are referring to - no quote.

But since I've been looking for a way to set my IP addresses, yes. When I said I couldn't find those settings via the Device Manager that's exactly what I meant.

I get properties with 6 tabs: General, Advanced, Driver, Details, Resources and Power Management.

Under win98 there were at least a dozen tabs and had to do with DHCP, various protocols and options, etc.

I'm starting to wonder if all this boils down to a broken crossover cable.

Thanks

[sjthinkpader]

I would suggest to delete the NIC driver from system properties, then reboot and let the system install the NIC driver again. Download the latest ethernet NIC driver and have it in the c:\drivers directory before you start.

Could you suggest what "latest" might mean and where to get it?

At the IBM/Lenovo site the latest driver was dated 2005, one year newer than what I had. I found another site with one marked 2007. I got that and ran the installation.

Now there is no longer one line in the TCP/IP -> Install -> Protocol -> Add list. In fact I don't get a list now. I get a message saying there are no drivers at all for Protocols.
...

It is nice to get the latest but I think version is not relevant to your problem.

http://www-307.ibm.com/pc/support/site. ... MIGR-62922
The overview doesn't include T40 but the .txt file indicate T40 is supported.

For some reason your IPv6 stack is damaged. In lieu of reinstalling Windows again, try this link to an update that includes IPv6.

http://www.microsoft.com/downloads/deta ... laylang=en

[sjthinkpader]

....
I'm starting to wonder if all this boils down to a broken crossover cable.

Thanks

If the cable is broken, you will not get a link. Is the link LED on at the ethernet port?

[JimL]

It is nice to get the latest but I think version is not relevant to your problem.

I think you're right. If it were a driver problem it wouldn't have been working fine for two years, seems to me. I did a restore to before the "update."

For some reason your IPv6 stack is damaged. In lieu of reinstalling Windows again, try this link to an update that includes IPv6.

http://www.microsoft.com/downloads/deta ... laylang=en

Everything on that page apparently refers to SP1. I have SP2. Is that a problem?

I'm not sure I can even do the IPv6 thing. It seems to be a bunch of stuff you have to fit together in order as opposed to running a setup program. Putting bits and pieces together has always been been more than I can get through my head and it's gotten worse instead of better.

Thanks

[JimL]

....
I'm starting to wonder if all this boils down to a broken crossover cable.

Thanks

If the cable is broken, you will not get a link. Is the link LED on at the ethernet port?

I don't really know. By the RJ-45 there is a very small LED that's always on, even if I pull the plug. (That makes no sense to me.) There may be another one right below it. It's hard to tell, because it's so tiny. And the PDF on it doesn't even mention any LED there. But I'm guessing if it were lighting it would be obvious.

On the other hand, how can you tell a broken cable from a fault on the other computer?

Thanks

[sjthinkpader]

If the cable is broken, you will not get a link. Is the link LED on at the ethernet port?

I don't really know. By the RJ-45 there is a very small LED that's always on, even if I pull the plug. (That makes no sense to me.) ...

Thanks

The LED should go out when you pull the cable. That port may have a problem. Take a close look to see if any wires in the port is out of place. If it doesn't work, disable it in the System Properties and use a PCMCIA or USB ethernet NIC and see if it ill work.

[JimL]

The LED should go out when you pull the cable. That port may have a problem. Take a close look to see if any wires in the port is out of place. If it doesn't work, disable it in the System Properties and use a PCMCIA or USB ethernet NIC and see if it ill work.

I got out a magnifying glass. Nothing broken or out of place. There ARE two tiny LEDs there. Does anyone have something that describes the LEDs in detail?

Thanks

[bill bolton]

By the RJ-45 there is a very small LED that's always on, even if I pull the plug.

That shouldn't happen.

A LAN port nothing plugged into it should have nothing illuminated next to the port.

A correctly wired cable plugged into the LAN port which has nothing on the other end should also result in having nothing illuminated next to the port.

A correctly wired cable plugged into the LAN port which has an active Ethernet device at the other end should give you a solid green light when the Thinkpad is powered, even before any device drivers load.

Once the device drivers are loaded, a correctly wired cable plugged into the LAN port which has an active Ethernet device at the other end should give you a solid green light and a flashing orange light below it.

On the other hand, how can you tell a broken cable from a fault on the other computer?

With a cable tester, or with a bit more patience using a multi-meter to check each wire end-to-end, one at a time.

Cheers,

Bill

[JimL]

By the RJ-45 there is a very small LED that's always on, even if I pull the plug.

That shouldn't happen.

A LAN port nothing plugged into it should have nothing illuminated next to the port.

Bill

Looks like I'm going to need a hardware geek.

Thanks