Getting an IP Address



Pam
07-10-2005, 01:52 AM
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!

Star Fleet Admiral Q
07-10-2005, 01:52 AM
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@discussions.microsoft.com> wrote in message
news:6257E28A-6B0F-46FF-B7F6-2E77A5553D62@microsoft.com...
>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!

Scott M.
07-10-2005, 01:52 AM
....And, the router should be configured to act as a DHCP server. The PC
should be set to "Obtain IP Addresses Automatically".



"Star Fleet Admiral Q" <Star_Fleet_Admiral_Q(NO-SPAM)@(SPAM-NOT)hotmail.com>
wrote in message news:eE9r5RAXFHA.3092@TK2MSFTNGP10.phx.gbl...
> 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@discussions.microsoft.com> wrote in message
> news:6257E28A-6B0F-46FF-B7F6-2E77A5553D62@microsoft.com...
>>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!
>
>

Pam
07-10-2005, 01:52 AM
Actually, the Westell Versalink is a DSL Modem and a router. Ethernet, not
USB. It has wireless capability but I haven't even attempted to use that yet.
And I know that it works because I try connecting an old backup computer to
the Versalink - internet connection was fine and I was able to access the
router at 192.168.1.1.

So, I have phone line to Versalink. RJCAT 5 to ethernet port in the
installed NIC card in the Dell computer. I've also tried changing the cable
and switching the ends.

I've been through this set up three times with Verizon tech support - one of
the hung up on me (ok, I'm frustrated...) but they couldn't find anything
wrong with my setup.

Your response though makes me wonder if it would help to try running the
Versizon set program again...at this point I'm desperate for things to try.

Thanks for your response though, if you think of anything else, please let
me know! - and oh, I didn't try ICS yet - my next step once I get an IP
address on the router is to add in the backup computer and get my home
network back.

"Star Fleet Admiral Q" wrote:

> 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@discussions.microsoft.com> wrote in message
> news:6257E28A-6B0F-46FF-B7F6-2E77A5553D62@microsoft.com...
> >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!
>
>
>

Al Romanosky
07-10-2005, 01:52 AM
Have not really thought out your problem, however a few comments if I may:
Regarding the LinkSys - DHCP is enabled but not active e.g. no IP address.
Regarding the Wan interface - no DHCP enabled and subnet mask of
254.254.254.254 invalid.

--
--------------------------------------------------------------------------------------------------------------------------
AL(KB3U) & Darlene Romanosky N. Ft.
Myers, FL
--------------------------------------------------------------------------------------------------------------------------

Pam
07-10-2005, 01:53 AM
fyi - changing for dhcp to static addresses got me at least to a working lan
with an internet connection.

Thanks to those that tried to help - and if anyone knows what might cause
dhcp to simply not work I'd be interested to know.

"Pam" wrote:

> 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!

DAB
07-10-2005, 01:53 AM
Pam--

Beleive it or not, I have been having the identical problem. Also happened
after I replaced a motherboard. I am using the same Verizon Westell router
and that is working fine. No problem connecting to the internet. My
daughter's laptop connects to it with no problem and no special setup. But
the computer with the new motherbaord, which uses a wireless card to connect
to the Verizon router, won't. Same error message when I tried
ipconfig/renew. "RPC server is not available."

I'm not that experienced with networking problems. Could you explain in a
little more detail what you did to achieve "a working LAN with an internet
connection." That's all I really want to do, anyway.

FYI--I did email microsoft support last night about the problem. I tried
one thing they suggested which didn't work, but if something they suggest
works, I'll be sure to share it with you.
--
DAB

"Pam" wrote:

> fyi - changing for dhcp to static addresses got me at least to a working lan
> with an internet connection.
>
> Thanks to those that tried to help - and if anyone knows what might cause
> dhcp to simply not work I'd be interested to know.
>
> "Pam" wrote:
>
> > 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!

DAB
07-10-2005, 01:53 AM
Pam--

I got mine to work. Quick question--have you ever had Norton Utlities or
Norton AntiVirus installed and then removed them? If so, I found the answer
for why the DHCP may not be working. If you've never had Norton on your
system, this fix probably doesn't apply.

The fix involves editing the registry to remove a couple of things Norton
left behind when it was uninstalled. Once I did that everything worked fine.
I don't understand why things had worked with the old motherboard, but not
with the new. But all I really care is that DHCP now works and I can connect
to the internet. See the following web site for the details of this fix:

http://www.bl.com/moshe/text/quiddities/norton_errors.html

Hope it works for you too.
--
DAB


"Pam" wrote:

> fyi - changing for dhcp to static addresses got me at least to a working lan
> with an internet connection.
>
> Thanks to those that tried to help - and if anyone knows what might cause
> dhcp to simply not work I'd be interested to know.
>
> "Pam" wrote:
>
> > 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!

jen
07-10-2005, 01:54 AM
ok,
Fought with this for a week with Verizon, various college computer
hacks my kids are friends with and my husband. (Didn't fight WITH them
just tried fighting the problem with them.) Due to the last message
above, we visited that website and it triggered something in hubby's
brain. Here is how we finally solved the problem, hope it works for
you!

go to START, CONTROL PANEL, ADMININSTRATIVE TOOLS, SERVICES, find DHCP
Client. Right click on it and hit Properties. You can select START
under Service Status and that will get you on the internet right away.
But you need to have this going when you power down/up so... Go to
"Startup type" click on the arrow down and select "Automatic". Hit ok
then restart your computer.

Problem solved for me. Yeah!



--
jen
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1622099.html

winchester
07-10-2005, 01:54 AM
Jen, if you're ever in Fremont, Ohio, I owe you a drink.

Same problem as described above, detailed right down to the part about
the Verizon people hanging up after not being able to fix it.

Dealing with this for several days, and your fix did it for me in
seconds. Thank you.

I registered to forum just to say thanks.

jen wrote:
> *ok,
> Fought with this for a week with Verizon, various college computer
> hacks my kids are friends with and my husband. (Didn't fight WITH
> them just tried fighting the problem with them.) Due to the la, st
> message above, we visited that website and it triggered something in
> hubby's brain. Here is how we finally solved the problem, hope it
> works for you!
>
> go to START, CONTROL PANEL, ADMININSTRATIVE TOOLS, SERVICES, find
> DHCP Client. Right click on it and hit Properties. You can select
> START under Service Status and that will get you on the internet
> right away. But you need to have this going when you power down/up
> so... Go to "Startup type" click on the arrow down and select
> "Automatic". Hit ok then restart your computer.
>
> Problem solved for me. Yeah! *



--
winchester
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message1622099.html


Getting an IP Address