Re: wireless: pings ok, but can't connect to net
- From: "MilesG" <mjgolding@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 1 Apr 2006 09:55:49 +0100
"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:Ow1vUoTVGHA.1728@xxxxxxxxxxxxxxxxxxxxxxx
"MilesG" <mjgolding@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:xqWdnVXFtdQ7WbDZRVny2A@xxxxxxxxx
router
"Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
news:uxkFZ1QVGHA.196@xxxxxxxxxxxxxxxxxxxxxxx
"MilesG" <mjgolding@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Z4adnYf-CPIMx7DZRVny2w@xxxxxxxxx
Pegasus (MVP) wrote:192.168.1.6,
See below.
snip
Do I have to add DNS setting in the TCP/IP dialog box? It seems
that
manually selecting an IP address demands an entry here, but I don't
know what. Also, exploring further in Advanced... I get told there
is no WINS server entry. Plus I don't know which to check out of
enable/disable NetBios, or use netbios setting form DHCP server.
You must set your DNS and your Default Gateway addresses
manually to the internal address used by your router, which is
probably 192.168.1.1.
Thanks for the help Pegasus, but I am not flying yet. Yes the router's
address is that, and I entered it so that now I have IP address
subnet mask 255.255.255.0, default gateway 192.168.1.1, Prefered DNSserver
192.168.1.1, and under Advanced/WINS, Enable LMHosts is checked and so
too
is Use Netbios settings from DHCP server. There is nothing in the WINS
window.
Miles
While "not flying yet" sounds nicely descriptive, it tells me nothing.
A more informative statement would be if you can ping the router,
other PCs, an Internet site by its IP address, an Internet site by
its name.
Thanks for your reply Pegasus. The Win2000 system can still ping the
and the other two PCs OK and they can ping back. Pinging an Internet siteby
its domain name elicited "unknown host"; using the same site's IP address
was successful.
Miles
This means that name resolution does not work. If other PCs on the
same network can ping Internet names successfully then the DNS
entry on your problem PC is incorrect. Compare it with the DNS
entry on successful PCs. If other PCs on the same network cannot
ping Internet names either then the DNS configuration of your
router is incorrect. Ask your ISP for the address of his DNS servers.
The Router Manager on the Main system (which pings internet names OK) shows
the Lan IP to be 192.168.1.1, default gateway 217.47.74.143, primary DNS
server 194.72.9.38, secondary server 62.6.40.162. So should I eneter the
default gateway IP on the W2000 system? (I don't understand why
automatically assigning an IP address didn't work in the first place).
Miles
.
- Follow-Ups:
- Re: wireless: pings ok, but can't connect to net
- From: Pegasus \(MVP\)
- Re: wireless: pings ok, but can't connect to net
- References:
- Re: wireless: pings ok, but can't connect to net
- From: Pegasus \(MVP\)
- Re: wireless: pings ok, but can't connect to net
- From: MilesG
- Re: wireless: pings ok, but can't connect to net
- From: Pegasus \(MVP\)
- Re: wireless: pings ok, but can't connect to net
- Prev by Date: Re: Delaying Network Interface Startup
- Next by Date: Re: wireless: pings ok, but can't connect to net
- Previous by thread: Re: wireless: pings ok, but can't connect to net
- Next by thread: Re: wireless: pings ok, but can't connect to net
- Index(es):
Relevant Pages
|
|