[detoxdsl]

Well first thing first, your getting a 169 ip address from windows because its not recognizing your nic or a cable is bad or something is wrong in your winsock registry.
I noticed in another post you are using winxp sp1 so you could try a winsock fix.

Steps to Perform Winsock Fix (Windows XP)



1) Open Regedit, Start > Run "Regedit".

2) Remove the Following Registry Keys located in "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\"

3) "\Winsock"

4) "\WinSock2"

5) Restart the PC

6) Reinstall TCP/IP on top of itself > In Network Properties click “Install” > Select “Protocol” and click “Add” > Choose “Have Disc” and point the location to the “C:\windows\inf” folder > click “OK”.

7) Restart the PC

**Note: If you upgraded from Windows NT or Windows 2000 point the location to the “c:\winnt\inf” folder.

**Note: The “c:\windows\inf” and the “c:\winnt\inf” folders are hidden.

Does it do this on any other computer ? The default gateway for the 660 is 192.168.2.1 and the default ip from a 660 mea1 is 192.168.2.2 and from a 660r 192.168.2.3. These are the ip address' that you want to recieve.

[TRS-80 vet]

Originally Posted by detoxdsl

Well first thing first, your getting a 169 ip address from windows because its not recognizing your nic or a cable is bad or something is wrong in your winsock registry.
I noticed in another post you are using winxp sp1 so you could try a winsock fix.

Steps to Perform Winsock Fix (Windows XP)



1) Open Regedit, Start > Run "Regedit".

2) Remove the Following Registry Keys located in "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\"

3) "\Winsock"

4) "\WinSock2"

5) Restart the PC

6) Reinstall TCP/IP on top of itself > In Network Properties click “Install” > Select “Protocol” and click “Add” > Choose “Have Disc” and point the location to the “C:\windows\inf” folder > click “OK”.

7) Restart the PC

**Note: If you upgraded from Windows NT or Windows 2000 point the location to the “c:\winnt\inf” folder.

**Note: The “c:\windows\inf” and the “c:\winnt\inf” folders are hidden.

Does it do this on any other computer ? The default gateway for the 660 is 192.168.2.1 and the default ip from a 660 mea1 is 192.168.2.2 and from a 660r 192.168.2.3. These are the ip address' that you want to recieve.

Embarq techie took me through winsock reg re-config, EXCEPT, he at #6 said re-install Microsoft TCP/IP v.6. - not TCP/IP.

Even after installing MS TCP/IP v. 6, it did not appear on the list of protocols, in LAN properties. This did not bother him...

[JohnWill]

The modem/router should work at the factory default settings as a rule. If someone fooled with it, you may need to reset it to factory defaults.

[detoxdsl]

Yeah, did they have you access any of the internal router configuration through internet explorer or through telnet ? And when you reinstalled tcp/ip it didn't list it in the properties ?????

[TRS-80 vet]

Originally Posted by detoxdsl

Yeah, did they have you access any of the internal router configuration through internet explorer or through telnet ? And when you reinstalled tcp/ip it didn't list it in the properties ?????

Not that I'm aware, did we attempt router/modem reconfig.

Yes, TCP/IP was already on the list of protocols. We did not re-install TCP/IP. We re-installed Microsoft TCP/IP v. 6. And no, after re-installation, of MS TCP/IP v. 6, it did not appear on the list of protocols in LAN properties...

[detoxdsl]

So does it show MS TCP/IP at all ? If so then your good, because it won't show the version of TCP/IP, just as long as it is installed. If after a winsock you still get the 169 ip I would almost definately agree and say that the nic is either acting up or that the cable is bad, if you need a replacement cross-over cable you can call embarq tech support at
877-646-3282 and request a new cross over cable, there won't be a charge or shipping. If you would like, email me at my work address w/ your phone number and i can look into this more if you feel comfortable in doing so

scott.c.cover@embarq.com is my email ... im here for another 3 hours so if you want me to look more into the info i can

This will also grant me access to the other techs notes to see what they had written down for notations about what they thought the possible issue / issues were

[TRS-80 vet]

Originally Posted by detoxdsl

So does it show MS TCP/IP at all ? If so then your good, because it won't show the version of TCP/IP, just as long as it is installed. If after a winsock you still get the 169 ip I would almost definately agree and say that the nic is either acting up or that the cable is bad, if you need a replacement cross-over cable you can call embarq tech support at
877-646-3282 and request a new cross over cable, there won't be a charge or shipping. If you would like, email me at my work address w/ your phone number and i can look into this more if you feel comfortable in doing so

scott.c.cover@embarq.com is my email ... im here for another 3 hours so if you want me to look more into the info i can

This will also grant me access to the other techs notes to see what they had written down for notations about what they thought the possible issue / issues were

I've sent the phone # to the embarq email address.

Thanks!

[TerryNet]

OK, I think you answered my PPP question--it's part of your dial-up connection. Shouldn't be having any impact on your problem.

A cross-over cable? A regular (patch, straight) cable is used between computer and router or modem.

[TRS-80 vet]

No one got any other ideas on this modem-to-NIC non-communication issue?

Even the far-fetched stabs in the dark from left field???

[TRS-80 vet]

I uninstalled the driver, re-started, and didn't get a wizard to re-install for a newly detected device (as help and support indicated).

The NIC was already back in my pc/device manager. I opened IE, and got onto the net.

How did this problem get fixed?

[JohnWill]

Don't look a gift horse in the mouth!

[TRS-80 vet]

Originally Posted by JohnWill

Don't look a gift horse in the mouth!

Good words of wisdom.

Knowledge, however, is far more valuable, than net access. And I've no clue what I did.


btw JW... You said this modem is also a router. W/wireless capability?

[JohnWill]

It's a router, I don't believe it's wireless from the net description.

[TRS-80 vet]

What this means is that you can't connect to the internet with your DSL modem...

[stepetroni]

I had the old Embarq modem (645) and it worked with all three of my computers. Today, I switched to their new modem, the 660 series and it would not work with my vista equipped Qosmio laptop. It worked with my older Satellite running XP without a problem.

The modem did , however, install software on the XP machine first (no disc, the software is loaded by the modem itself) and I believe that when the later, Vista computer sees the software being loaded it shuts off the connection. You get "network cable unplugged" when it is NOT unplugged. When you first turn the computer on, the Ethernet light on the modem lights BUT goes out when Windows loads beyond a certain point, leading me to believe Vista is blocking the software installation DURING startup and the actual Ethernet connection is disabled as if a cable is unplugged. It shows the Ethernet connection as enabled BUT disconnected.

Embarq was unable to help with this and implied the problem is with the computer BUT reverting to the old modem....no problem. Either it is a glitch in Vista or a problem with them trying to load their software for the modem as Windows starts. No solution so far so, I just re attached the old modem and I'm good. BTW, my old modem was reprogrammed by another Embarq tech rep to the new "language" they are using over the phone with me being prompted through the steps on my laptop. I see no downside to just keeping the old modem with the new as backup since it works on my two XP computers.

SteP