Re: Getting an IP Address
- From: "Star Fleet Admiral Q" <Star_Fleet_Admiral_Q(NO-SPAM)@(SPAM-NOT)hotmail.com>
- Date: Wed, 18 May 2005 19:51:09 -0400
Looking at what you've provided, it appears you have both a "network card"
(NIC) and the Verizon DSL Modem connected, maybe via a USB port? Off course
the NIC is going to error out because it has no connection.
A normal home network connection with a router goes like this:
Wall Jack to DSL Modem (normal phone wire connection without the DSL
filter),
DSL Modem to Router (RJ45 CAT 5 cable, normally ethernet to uplink)
Router to Computer via one of these methods:
a) Wireless Card - if your router is capable, requires compatible
Wireless card in PC/Laptop
b) NIC (again normally RJ45 CAT 5, from router to NIC)
c) USB NIC (again an RJ45 CAT 5 cable, from router to USB NIC, then USB
NIC is plugged into one of the computer's USB ports - I recommend against
these).
The router will be need to be configured to use PPPOE and store the DSL
Login/Password for the DSL account - it can also be configured to stay
active on the account at all times, or only when there is a request and
logoff after xxx minutes of activity.
Did you try to setup ICS (Internet Connection Sharing), where the phone line
connects to the DSL Modem, the DSL Modem to the computer via a USB
connection, then connecting a CAT 5 cable to the computer's NIC and running
to the router and/or another computer? If so, then you would have needed to
setup ICS, and although it will work, it is more problematic to keep
everything setup correctly and not to mention the PC with the DSL Modem has
to always to be on before the router/other computer can access the internet.
--
Star Fleet Admiral Q @ your Service!
http://www.google.com
Google is your "Friend"
"Pam" <Pam@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6257E28A-6B0F-46FF-B7F6-2E77A5553D62@xxxxxxxxxxxxxxxx
>I posted about a week ago and followed everyone's advice - I didn't solve
>it
> yet - been down many roads - but I realize I was biting off too much.
> Walk,
> then run.
>
> I'm trying to take a simple step and connect one computer to a router and
> get an IP address. I get a status of 'acquiring network address' on the
> lan
> connection. The router is a Westell Versalink from Verizon for DSL. The
> DSL
> connection works fine.
>
> ipconfig/all looks like this:
>
>
> Windows IP Configuration
>
>
>
> Host Name . . . . . . . . . . . . : Delldesktop
>
> Primary Dns Suffix . . . . . . . :
>
> Node Type . . . . . . . . . . . . : Hybrid
>
> IP Routing Enabled. . . . . . . . : No
>
> WINS Proxy Enabled. . . . . . . . : No
>
>
>
> Ethernet adapter Local Area Connection 5:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : Linksys LNE100TX Fast Ethernet
> Adapter(LNE100TX v4)
>
> Physical Address. . . . . . . . . : 00-0C-41-24-B7-94
>
> Dhcp Enabled. . . . . . . . . . . : Yes
>
> Autoconfiguration Enabled . . . . : Yes
>
> IP Address. . . . . . . . . . . . : 0.0.0.0
>
> Subnet Mask . . . . . . . . . . . : 0.0.0.0
>
> Default Gateway . . . . . . . . . :
>
> DHCP Server . . . . . . . . . . . : 0.0.0.0
>
>
>
> PPP adapter Verizon Online 2:
>
>
>
> Connection-specific DNS Suffix . :
>
> Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
>
> Physical Address. . . . . . . . . : 00-53-45-00-00-00
>
> Dhcp Enabled. . . . . . . . . . . : No
>
> IP Address. . . . . . . . . . . . : 70.111.181.160
>
> Subnet Mask . . . . . . . . . . . : 255.255.255.255
>
> Default Gateway . . . . . . . . . : 70.111.181.160
>
> DNS Servers . . . . . . . . . . . : 151.197.0.39
>
> 151.198.0.39
>
> NetBIOS over Tcpip. . . . . . . . : Disabled
>
> An ipconfig/renew command produces:
>
>
> Windows IP Configuration
>
>
>
> An error occurred while renewing interface Local Area Connection 5 : The
> RPC
> server is unavailable.
>
> I have tried using a linksys wrt54g rounter instead of the Westell - same
> result
> I have tried using the integrated NIC in my motherboard (that was the
> first
> try, disabling it and installing the curent linksys nic card was after
> that)
> - same result
>
>
> TCP/IP properties are:
> - optain ip address automatically
> - optain dns server address automatically
>
> I have tried winsockxpfix and netsh winsock reset catalog
>
> It may be useful to know that the motherboard was recently replaced - but
> everything else works fine!
.
- Follow-Ups:
- Re: Getting an IP Address
- From: Pam
- Re: Getting an IP Address
- From: Scott M.
- Re: Getting an IP Address
- References:
- Getting an IP Address
- From: Pam
- Getting an IP Address
- Prev by Date: Error 800:
- Next by Date: Networking, XP home, '... Not accessible ...' etc
- Previous by thread: Getting an IP Address
- Next by thread: Re: Getting an IP Address
- Index(es):
Relevant Pages
|