Can't connect from notebook to router

  • Thread starter Thread starter il barbi
  • Start date Start date
I

il barbi

My notebook runs Windows Vista Home Premium and has a wireless Broadcom
802.11g adapter, I'm just testing near my router D-Link DI-524 and obviously
I get 100% signal power but I can't ping the router (192.168.0.1) - I get
error 1231. Now I hope the router address is the same for the wireless
devices too...
From ipconfig /all I get:
- Windows IP Configuration: node type=hybrid, routing IP enabled=no,
proxy wins enabled = no
- then it lists 3 "tunnel boards for connection to LAN" (perhaps this
displays not so because I'm translating from italian) with: device state
disconnected and DHCP enabled=no
Moreover I found just for one time a mask saying "Connection status" -
"Connection details" giving: Ipv4 config. address 169.254.235.2; IPv4 subnet
mask 255.255.0.0; Netbios on TCP/IP enabled
In the Network adapter Properties - advanced I see some 20 parameters that I
can't just understand except a communication channel being set to 6 as for
the router side.
Now I'm tired to try the configuration menus, I'd like some step-by-step
procedure and possibly some diagnostic tool before I go to my repair store
il barbi
 
My notebook runs Windows Vista Home Premium and has a wireless
Broadcom 802.11g adapter, I'm just testing near my router D-Link
DI-524 and obviously I get 100% signal power but I can't ping the
router (192.168.0.1) - I get error 1231. Now I hope the router
address is the same for the wireless devices too...
From ipconfig /all I get:
- Windows IP Configuration: node type=hybrid, routing IP
enabled=no, proxy wins enabled = no
- then it lists 3 "tunnel boards for connection to LAN" (perhaps
this displays not so because I'm translating from italian) with:
device state disconnected and DHCP enabled=no
Moreover I found just for one time a mask saying "Connection
status" - "Connection details" giving: Ipv4 config. address
169.254.235.2; IPv4 subnet mask 255.255.0.0; Netbios on TCP/IP
enabled In the Network adapter Properties - advanced I see some 20
parameters that I can't just understand except a communication
channel being set to 6 as for the router side.
Now I'm tired to try the configuration menus, I'd like some
step-by-step procedure and possibly some diagnostic tool before I
go to my repair store il barbi
Click to expand...

169.254.xxx.xxx addresses occur when the computer can't get an IP
address. In your case, "DHCP enabled = No" is the most likely
reason. DHCP is needed to obtain IP address, DNS servers, and other
network configuration. Make sure that your DHCP is enabled and try
again.

Network Connections Control panel -> right-click your Connection ->
Properties -> Internet Protocol -> Properties -> "Obtain an IP
Address automatically"

Also make sure that your DHCP Client Service is running:
Right-click "My Computer" -> Manage -> Services and Applications ->
Services -> Make Sure DHCP Client is "Started".

HTH,
John


HTH,
John
 
John Wunderlich said:
169.254.xxx.xxx addresses occur when the computer can't get an IP
address. In your case, "DHCP enabled = No" is the most likely
reason. DHCP is needed to obtain IP address, DNS servers, and other
network configuration. Make sure that your DHCP is enabled and try
again.
DHCP IS enabled...

Also make sure that your DHCP Client Service is running:
Right-click "My Computer" -> Manage -> Services and Applications ->
Services -> Make Sure DHCP Client is "Started".
Click to expand...
....and DHCP client IS started...:-(
....sigh
il barbi
 
Robert L. (MS-MVP) said:
169.254.235.2 is auto Ip if you don't have one. You should enable DHCP.
Click to expand...
I assure you I have enabled DHCP in protocol TCP/IPv4... Now I read that
there is a compatibility problem between PCs running Vista and PCs running
WinXP that seems to fit with my problem, i.e. in Windows Registry the
Broadcast flag is enabled while in the contrary in WinXP it is disabled and
this prevents Vista from obtaining an IP address - I made the related patch
to Windows Registry but nothing changed...
Another hint was the possible conflict in network configuration from Vista
utility versus the board manufacturer's utility, involving the need for
disabling Windows Zero Configuration when using the last solution - now in
Vista WZC is enabled and no board manufacturer's configuration utility is
started, so there must not be such conflict
(By the way, these two items were not listed in the majority of the many
network tutorials I've read till now...)
il barbi
 
Back
Top