Vista does not connect to internet at start

Hello,

I'm desperately trying to solve a network problem with Vista to a internet
provider.
Nearly brand new PC with nVidia Forceware ethernet controller.
After booting the PC, the network ICON in right bottom bar becomes blue.
For 1 - 2 seconds the blue bell is visible, then disappears.
It shows the PC is connected locally, but not to internet.
According to IPCONFIG/all required IP addr, DNS, Default GW etc is set
correctly.

I found several ways to get the Internet connection active.
- disconnect and reconnect the modem, or
- use the network repair function, or
- wait for about 15 minutes or
- change on of the configuration parameters in the network card or protocol
properties.

Another Laptop with WIN-XP connects without problems.
I could not yet try another Vista PC, but will do to compare.

I have;
- gone through all network settings - no issues found
- switched off IPv6
- reinstalled ethernet card drivers (latest version of nVidia)
- changed the DHCP Broadcast Flag in the register
- checked the network connection is for privat LAN

Remarks:
The PC had earlier two ethernet cards, I removed one,
now only the motherboard's ethernet controller is active.
The network provider say's he sees a router at the PC side, but the
PC is directly connected to the Providers modem, no router installed??

Any suggestion to troubleshoot or even solve the problem is welcome.

Cheers JaapV

Interesting problem. First, can you do an "ipconfig /all" from the command
prompt and provide a cut and paste copy to us please.

A clue exists when you said you removed another card. And with your
provider's observation because there actually is a trivial router in your
computer. You can see some of the setup parameters by going to command
prompt and type "route". But this table gets reset/updated at each boot
time. It then gets built during a session as you use it, and it discovers
ports. I am thinking that somehow with the other Ethernet card something in
this routing table got stuck, but I can't tell you where. I am speaking out
load here, if for no other reason then to prompt others to jump in and help
from here.

--
Regards, BobF.
"veneman" <register@jveneman(nospam).nl> wrote in message
news:469457A3-0013-4536-BB4B-E1E147F168E8@microsoft.com...

> Hello,
>
> I'm desperately trying to solve a network problem with Vista to a internet
> provider.
> Nearly brand new PC with nVidia Forceware ethernet controller.
> After booting the PC, the network ICON in right bottom bar becomes blue.
> For 1 - 2 seconds the blue bell is visible, then disappears.
> It shows the PC is connected locally, but not to internet.
> According to IPCONFIG/all required IP addr, DNS, Default GW etc is set
> correctly.
>
> I found several ways to get the Internet connection active.
> - disconnect and reconnect the modem, or
> - use the network repair function, or
> - wait for about 15 minutes or
> - change on of the configuration parameters in the network card or
> protocol
> properties.
>
> Another Laptop with WIN-XP connects without problems.
> I could not yet try another Vista PC, but will do to compare.
>
> I have;
> - gone through all network settings - no issues found
> - switched off IPv6
> - reinstalled ethernet card drivers (latest version of nVidia)
> - changed the DHCP Broadcast Flag in the register
> - checked the network connection is for privat LAN
>
> Remarks:
> The PC had earlier two ethernet cards, I removed one,
> now only the motherboard's ethernet controller is active.
> The network provider say's he sees a router at the PC side, but the
> PC is directly connected to the Providers modem, no router installed??
>
> Any suggestion to troubleshoot or even solve the problem is welcome.
>
> Cheers JaapV
>

Hello Bob F,

Sorry I did not reply earlier. For one or another reason my credentials did
not work, although registered, but not activated. I finally found this
problem was in a forum http://forums.techarena.in, with a copy of all
messages here. Whatever I tried in communication to the WEBmaster even new
registration all was ignored. Today I learned I could reply in the
windowshelp.microsoft.com forum.

Again:
When booting the PC, IP address, DNS, Def GW are obtained as you can see in
the IPconfig information. It look like a short moment internet is accessed
(blue bell on the Icon, but then terminated. It will be repaired by shortly
disconnecting the UTP cable, or switching off/on the modem, or use the
Windows network repair function.
A Laptop with Win XP has no problems.

The PC is of recent make, Windows Vista Premium, 64 bit.
Asus motherboard with nForce Ethernet controller.
It had no problems when connected to the previous provider, although via an
older Ethernet card. The problem started when connecting to a new provider.
The I removed this old card.

Below you find IPCONFIG, but I agree with you that routing of a bridge
might cause problems, so I added also the ROUTE PRINT info.

I hope you or anyone else has suggestions to further troubleshoot or may
solve this problem, otherwise a fresh new installation of the Windows an
app's is required.

Cheers Jaap Veneman



Microsoft Windows [versie 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. Alle rechten voorbehouden.

C:\Users\Bekkers>ipconfig /all

Windows IP-configuratie

Hostnaam . . . . . . . . . . . . : PC_van_Bekkers
Primair DNS-achtervoegsel . . . . :
Knooppunttype . . . . . . . . . . : hybride
IP-routering ingeschakeld . . . . : nee
WINS-proxy ingeschakeld . . . . . : nee

Ethernet-adapter LAN-verbinding:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : NVIDIA nForce Networking Controller #2
Fysiek adres. . . . . . . . . . . : 00-19-66-0D-72-B8
DHCP ingeschakeld . . . . . . . . : ja
Autom. configuratie ingeschakeld : ja
Link-local IPv6-adres . . . . . . : fe80::6448:54cf:2a89:b034%12(voorkeur)
IPv4-adres. . . . . . . . . . . . : 88.159.193.9(voorkeur)
Subnetmasker. . . . . . . . . . . : 255.255.248.0
Lease verkregen . . . . . . . . . : donderdag 20 maart 2008 12:02:24
Lease verlopen. . . . . . . . . . : donderdag 20 maart 2008 13:02:24
Standaardgateway. . . . . . . . . : 88.159.192.1
DHCP-server . . . . . . . . . . . : 172.16.22.29
DHCPv6 IAID . . . . . . . . . . . : 201333094
DNS-servers . . . . . . . . . . . : 88.159.1.200
88.159.1.201
NetBIOS via TCPIP . . . . . . . . : ingeschakeld

Tunnel-adapter LAN-verbinding*:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . :
isatap.{DC56B541-B414-4899-B385-42C738E05
EC9}
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
Link-local IPv6-adres . . . . . . :
fe80::200:5efe:88.159.193.9%13(voorkeur)

Standaardgateway. . . . . . . . . :
DNS-servers . . . . . . . . . . . : 88.159.1.200
88.159.1.201
NetBIOS via TCPIP . . . . . . . . : uitgeschakeld

Tunnel-adapter LAN-verbinding* 6:

Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Fysiek adres. . . . . . . . . . . : 02-00-54-55-4E-01
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja

Tunnel-adapter LAN-verbinding* 7:

Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : 6TO4 Adapter
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja
Tijdelijk IPv6-adres. . . . . . . : 2002:589f:c109::589f:c109(voorkeur)
Standaardgateway. . . . . . . . . :
DNS-servers . . . . . . . . . . . : 88.159.1.200
88.159.1.201
NetBIOS via TCPIP . . . . . . . . : uitgeschakeld

Tunnel-adapter LAN-verbinding* 9:

Mediumstatus. . . . . . . . . . . : medium ontkoppeld
Verbindingsspec. DNS-achtervoegsel:
Beschrijving. . . . . . . . . . . : 6TO4 Adapter
Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP ingeschakeld . . . . . . . . : nee
Autom. configuratie ingeschakeld : ja

C:\Users\Bekkers>route print
================================================== =========================
Interfacelijst
12 ...00 19 66 0d 72 b8 ...... NVIDIA nForce Networking Controller #2
1 ........................... Software Loopback Interface 1
13 ...00 00 00 00 00 00 00 e0 isatap.{DC56B541-B414-4899-B385-42C738E05EC9}
8 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
14 ...00 00 00 00 00 00 00 e0 6TO4 Adapter
10 ...00 00 00 00 00 00 00 e0 6TO4 Adapter
================================================== =========================

IPv4 routetabel
================================================== =========================
Actieve routes:
Netwerkadres Netmasker Gateway Interface Metric
0.0.0.0 0.0.0.0 88.159.192.1 88.159.193.9 20
88.159.192.0 255.255.248.0 On-link 88.159.193.9 276
88.159.193.9 255.255.255.255 On-link 88.159.193.9 276
88.159.199.255 255.255.255.255 On-link 88.159.193.9 276
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 88.159.193.9 276
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 88.159.193.9 276
================================================== =========================
Permanente routes:
Geen

IPv6 routetabel
================================================== =========================
Actieve routes:
Indien metrische netwerkbestemming Gateway
1 306 ::1/128 On-link
14 1025 2002::/16 On-link
14 281 2002:589f:c109::589f:c109/128
On-link
12 276 fe80::/64 On-link
13 281 fe80::200:5efe:88.159.193.9/128
On-link
12 276 fe80::6448:54cf:2a89:b034/128
On-link
1 306 ff00::/8 On-link
12 276 ff00::/8 On-link
================================================== =========================
Permanente routes:
Geen

C:\Users\Bekkers>



"Bob F." wrote:

> Interesting problem. First, can you do an "ipconfig /all" from the command
> prompt and provide a cut and paste copy to us please.
>
> A clue exists when you said you removed another card. And with your
> provider's observation because there actually is a trivial router in your
> computer. You can see some of the setup parameters by going to command
> prompt and type "route". But this table gets reset/updated at each boot
> time. It then gets built during a session as you use it, and it discovers
> ports. I am thinking that somehow with the other Ethernet card something in
> this routing table got stuck, but I can't tell you where. I am speaking out
> load here, if for no other reason then to prompt others to jump in and help
> from here.
>
> --
> Regards, BobF.
> "veneman" <register@jveneman(nospam).nl> wrote in message
> news:469457A3-0013-4536-BB4B-E1E147F168E8@microsoft.com...

>
>

Hello Jaap,

Please try this. Start > Type regedit then search path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\
Parameters\Interfaces\

Then select one of the next folders if it appears and look on the right for:

DhcpConnForceBroadcastFlag, double click it, Change the Value Data to “0�.
Then hit ok and close out.

Let me know.
--
Regards, BobF.
"veneman" <register@jveneman(nospam).nl> wrote in message
news:29803050-7093-474A-BA88-85D7B7421960@microsoft.com...

> Hello Bob F,
>
> Sorry I did not reply earlier. For one or another reason my credentials
> did
> not work, although registered, but not activated. I finally found this
> problem was in a forum http://forums.techarena.in, with a copy of all
> messages here. Whatever I tried in communication to the WEBmaster even new
> registration all was ignored. Today I learned I could reply in the
> windowshelp.microsoft.com forum.
>
> Again:
> When booting the PC, IP address, DNS, Def GW are obtained as you can see
> in
> the IPconfig information. It look like a short moment internet is accessed
> (blue bell on the Icon, but then terminated. It will be repaired by
> shortly
> disconnecting the UTP cable, or switching off/on the modem, or use the
> Windows network repair function.
> A Laptop with Win XP has no problems.
>
> The PC is of recent make, Windows Vista Premium, 64 bit.
> Asus motherboard with nForce Ethernet controller.
> It had no problems when connected to the previous provider, although via
> an
> older Ethernet card. The problem started when connecting to a new
> provider.
> The I removed this old card.
>
> Below you find IPCONFIG, but I agree with you that routing of a bridge
> might cause problems, so I added also the ROUTE PRINT info.
>
> I hope you or anyone else has suggestions to further troubleshoot or may
> solve this problem, otherwise a fresh new installation of the Windows an
> app's is required.
>
> Cheers Jaap Veneman
>
>
>
> Microsoft Windows [versie 6.0.6000]
> Copyright (c) 2006 Microsoft Corporation. Alle rechten voorbehouden.
>
> C:\Users\Bekkers>ipconfig /all
>
> Windows IP-configuratie
>
> Hostnaam . . . . . . . . . . . . : PC_van_Bekkers
> Primair DNS-achtervoegsel . . . . :
> Knooppunttype . . . . . . . . . . : hybride
> IP-routering ingeschakeld . . . . : nee
> WINS-proxy ingeschakeld . . . . . : nee
>
> Ethernet-adapter LAN-verbinding:
>
> Verbindingsspec. DNS-achtervoegsel:
> Beschrijving. . . . . . . . . . . : NVIDIA nForce Networking Controller
> #2
> Fysiek adres. . . . . . . . . . . : 00-19-66-0D-72-B8
> DHCP ingeschakeld . . . . . . . . : ja
> Autom. configuratie ingeschakeld : ja
> Link-local IPv6-adres . . . . . . :
> fe80::6448:54cf:2a89:b034%12(voorkeur)
> IPv4-adres. . . . . . . . . . . . : 88.159.193.9(voorkeur)
> Subnetmasker. . . . . . . . . . . : 255.255.248.0
> Lease verkregen . . . . . . . . . : donderdag 20 maart 2008 12:02:24
> Lease verlopen. . . . . . . . . . : donderdag 20 maart 2008 13:02:24
> Standaardgateway. . . . . . . . . : 88.159.192.1
> DHCP-server . . . . . . . . . . . : 172.16.22.29
> DHCPv6 IAID . . . . . . . . . . . : 201333094
> DNS-servers . . . . . . . . . . . : 88.159.1.200
> 88.159.1.201
> NetBIOS via TCPIP . . . . . . . . : ingeschakeld
>
> Tunnel-adapter LAN-verbinding*:
>
> Verbindingsspec. DNS-achtervoegsel:
> Beschrijving. . . . . . . . . . . :
> isatap.{DC56B541-B414-4899-B385-42C738E05
> EC9}
> Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP ingeschakeld . . . . . . . . : nee
> Autom. configuratie ingeschakeld : ja
> Link-local IPv6-adres . . . . . . :
> fe80::200:5efe:88.159.193.9%13(voorkeur)
>
> Standaardgateway. . . . . . . . . :
> DNS-servers . . . . . . . . . . . : 88.159.1.200
> 88.159.1.201
> NetBIOS via TCPIP . . . . . . . . : uitgeschakeld
>
> Tunnel-adapter LAN-verbinding* 6:
>
> Mediumstatus. . . . . . . . . . . : medium ontkoppeld
> Verbindingsspec. DNS-achtervoegsel:
> Beschrijving. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
> Fysiek adres. . . . . . . . . . . : 02-00-54-55-4E-01
> DHCP ingeschakeld . . . . . . . . : nee
> Autom. configuratie ingeschakeld : ja
>
> Tunnel-adapter LAN-verbinding* 7:
>
> Verbindingsspec. DNS-achtervoegsel:
> Beschrijving. . . . . . . . . . . : 6TO4 Adapter
> Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP ingeschakeld . . . . . . . . : nee
> Autom. configuratie ingeschakeld : ja
> Tijdelijk IPv6-adres. . . . . . . : 2002:589f:c109::589f:c109(voorkeur)
> Standaardgateway. . . . . . . . . :
> DNS-servers . . . . . . . . . . . : 88.159.1.200
> 88.159.1.201
> NetBIOS via TCPIP . . . . . . . . : uitgeschakeld
>
> Tunnel-adapter LAN-verbinding* 9:
>
> Mediumstatus. . . . . . . . . . . : medium ontkoppeld
> Verbindingsspec. DNS-achtervoegsel:
> Beschrijving. . . . . . . . . . . : 6TO4 Adapter
> Fysiek adres. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
> DHCP ingeschakeld . . . . . . . . : nee
> Autom. configuratie ingeschakeld : ja
>
> C:\Users\Bekkers>route print
> ================================================== =========================
> Interfacelijst
> 12 ...00 19 66 0d 72 b8 ...... NVIDIA nForce Networking Controller #2
> 1 ........................... Software Loopback Interface 1
> 13 ...00 00 00 00 00 00 00 e0
> isatap.{DC56B541-B414-4899-B385-42C738E05EC9}
> 8 ...02 00 54 55 4e 01 ...... Teredo Tunneling Pseudo-Interface
> 14 ...00 00 00 00 00 00 00 e0 6TO4 Adapter
> 10 ...00 00 00 00 00 00 00 e0 6TO4 Adapter
> ================================================== =========================
>
> IPv4 routetabel
> ================================================== =========================
> Actieve routes:
> Netwerkadres Netmasker Gateway Interface
> Metric
> 0.0.0.0 0.0.0.0 88.159.192.1 88.159.193.9 20
> 88.159.192.0 255.255.248.0 On-link 88.159.193.9 276
> 88.159.193.9 255.255.255.255 On-link 88.159.193.9 276
> 88.159.199.255 255.255.255.255 On-link 88.159.193.9 276
> 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
> 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
> 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
> 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
> 224.0.0.0 240.0.0.0 On-link 88.159.193.9 276
> 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
> 255.255.255.255 255.255.255.255 On-link 88.159.193.9 276
> ================================================== =========================
> Permanente routes:
> Geen
>
> IPv6 routetabel
> ================================================== =========================
> Actieve routes:
> Indien metrische netwerkbestemming Gateway
> 1 306 ::1/128 On-link
> 14 1025 2002::/16 On-link
> 14 281 2002:589f:c109::589f:c109/128
> On-link
> 12 276 fe80::/64 On-link
> 13 281 fe80::200:5efe:88.159.193.9/128
> On-link
> 12 276 fe80::6448:54cf:2a89:b034/128
> On-link
> 1 306 ff00::/8 On-link
> 12 276 ff00::/8 On-link
> ================================================== =========================
> Permanente routes:
> Geen
>
> C:\Users\Bekkers>
>
>
>
> "Bob F." wrote:
>

Hello Bob,

Thanks very much for your quick reply.

I have done this earlier this week and quite sure it was on the correct
interface. I found this suggestion in some other threads. Unfortunately it
did not solve the problem.
Anyway I will redoo this modification and surely check I have done it on the
correct interface key.

Did you see anything strange in the IPconfig or Route info?

Cheers Jaap Veneman

"Bob F." wrote:

> Hello Jaap,
>
> Please try this. Start > Type regedit then search path:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\
> Parameters\Interfaces\
>
> Then select one of the next folders if it appears and look on the right for:
>
> DhcpConnForceBroadcastFlag, double click it, Change the Value Data to “0�.
> Then hit ok and close out.
>
> Let me know.
> --
> Regards, BobF.
> "veneman" <register@jveneman(nospam).nl> wrote in message
> news:29803050-7093-474A-BA88-85D7B7421960@microsoft.com...

>

Dear Bob, others.

I tried now all suggestions I got or found in forums.
- DhcpConnForceBroadcastFlag = 0 or 1 (DHCP works fine)
- Reset TCP/IP (netsh int ip reset resetlog.txt)
- Reset Winsock (netsh winsock reset )
- Reset Route table (route -f)
- IPv6 disabled
None of these solves the problem

Tracert 127.0.0.1 (local host) responds correct.
Tracert "Default GW IP address" shows timeouts
(this while the Def. GW address is configured correctly for the interface,
so routing is may be the problem)

I found that the IPCONFIG /Renew command brings back the Internet connection
to live.

I have no single idea where now to look. Probably the only solution is a
fresh install of Windows Vista,
which is may be less time consuming then the trouble shooting.

Cheers Jaap