wireless: pings ok, but can't connect to net

[MilesG]

I have a similar problem to austinpctech a few threads down. 2 x XP systems,
1 Win 2000Pro, BTVoyager2091 router, BT Voyager1040 adapter on the 2000
system.

1. Is your wireless adapter enabled or disabled? Yes
2. Does it see your wireless network? Yes
3. Does it authenticate with your access point? I assume it does because the
connection icons show "connected"
4. Does it get an address from your DHCP server, or if the
address is assigned manually, is this address within the
correct subnet? It did get an address automatically(169,254.175.163) but
I could not ping anything using this, even setting it up in ZoneAlarmPro in
TrustedZone. I then manually setup 192.168.1.6 which means....
5. Can you ping your server? .....I can now ping the router (192.168.1.1)
and the other 2 computers (...1.2 and ....1.3) and they can ping the W2000
system
6. Can you make a connection to a server share, using this
command: net use q: \\YourServer\SomeShare

I don't understand this command. I don't know what to insert in
"YourServer\SomeShare". I tried in the Command prompt <net use q:
\\Home\Main> in vain. (My Computer now can navigate to shared files through
Microsoft Windows Networks\Home\Main and ....\Music, the names of the two XP
systems, and the XP systems can see files on the 2000 system likewise)

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.

Thanks for the help so far! Any further help would be appreciated. If there
is a good site that explains all this, I'd be glad to know.

Miles

 

[Pegasus \(MVP\)]

See below.

I have a similar problem to austinpctech a few threads down. 2 x XP systems,
1 Win 2000Pro, BTVoyager2091 router, BT Voyager1040 adapter on the 2000
system.

1. Is your wireless adapter enabled or disabled? Yes
2. Does it see your wireless network? Yes
3. Does it authenticate with your access point? I assume it does because the
connection icons show "connected"
4. Does it get an address from your DHCP server, or if the
address is assigned manually, is this address within the
correct subnet? It did get an address automatically(169,254.175.163)

but

No, you did not get an address. The address you quote is
assigned when a machine fails to get an address from the
DHCP server.

I could not ping anything using this, even setting it up in ZoneAlarmPro in
TrustedZone. I then manually setup 192.168.1.6 which means....
5. Can you ping your server? .....I can now ping the router (192.168.1.1)
and the other 2 computers (...1.2 and ....1.3) and they can ping the W2000
system

That's OK.

6. Can you make a connection to a server share, using this
command: net use q: \\YourServer\SomeShare
I don't understand this command. I don't know what to insert in
"YourServer\SomeShare". I tried in the Command prompt <net use q:
\\Home\Main> in vain. (My Computer now can navigate to shared files through
Microsoft Windows Networks\Home\Main and ....\Music, the names of the two XP
systems, and the XP systems can see files on the 2000 system likewise)

The command is irrelevant when connecting to the net.

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.

 

[MilesG]

See below.
snip


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 192.168.1.6,
subnet mask 255.255.255.0, default gateway 192.168.1.1, Prefered DNS server
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

 

[Pegasus \(MVP\)]

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 192.168.1.6,
subnet mask 255.255.255.0, default gateway 192.168.1.1, Prefered DNS server
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.

 

[MilesG]

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 router
and the other two PCs OK and they can ping back. Pinging an Internet site by
its domain name elicited "unknown host"; using the same site's IP address
was successful.
Miles

 

[Pegasus \(MVP\)]

Thanks for your reply Pegasus. The Win2000 system can still ping the router
and the other two PCs OK and they can ping back. Pinging an Internet site by
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.

 

[MilesG]

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

 

[Pegasus \(MVP\)]

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

There is nothing wrong with your default gateway. If there was
then you would not be able to ping any external IP address.

 

[MilesG]

snip

There is nothing wrong with your default gateway. If there was
then you would not be able to ping any external IP address.

Thanks for your continued help Pegasus. Now I've entered IP 192.168.1.6,
subnet Mask 255.255.255.0, default gateway 192.168.1.1, Preferred DNS server
194.72.9.38, alternative DNS server 62.6.40.162, which are the settings
given by the router manager on the system that is ethernet-connected to the
router (although the terminology there is "Primary DNS../Secondary DNS..").
No change: the systems ping each other, and the Win2000 system still pings a
numeric IP address OK, but not its alphabetical equivalent.
I'm puzzled that ipconfig on the Main computer says the DNS server is
192.168.1.1, which is not what the router manager tells me, and that the
Default Gateway is shown as 217.47.74.143 by the router manager, and
192.168.1.1 by ipconfig.
Miles

 

[Pegasus \(MVP\)]

snip


Thanks for your continued help Pegasus. Now I've entered IP 192.168.1.6,
subnet Mask 255.255.255.0, default gateway 192.168.1.1, Preferred DNS server
194.72.9.38, alternative DNS server 62.6.40.162, which are the settings
given by the router manager on the system that is ethernet-connected to the
router (although the terminology there is "Primary DNS../Secondary DNS..").
No change: the systems ping each other, and the Win2000 system still pings a
numeric IP address OK, but not its alphabetical equivalent.
I'm puzzled that ipconfig on the Main computer says the DNS server is
192.168.1.1, which is not what the router manager tells me, and that the
Default Gateway is shown as 217.47.74.143 by the router manager, and
192.168.1.1 by ipconfig.
Miles

In most cases the preferred Default Gateway settings on workstations
point at the router.

The router itself uses the Default Gateway settings assigned by your
ISP.

I draw your attention to my previous reply where I suggested that
you should make your problem machine the same as one of your
working machines.

 

[MilesG]

In most cases the preferred Default Gateway settings on workstations
point at the router.

The router itself uses the Default Gateway settings assigned by your
ISP.

I draw your attention to my previous reply where I suggested that
you should make your problem machine the same as one of your
working machines.

Pegasus, the previous reply to which you refer advised me to look at the DNS
entry on successful PCs. The difficulty there is that the settings in LAN
Properties on the XP working machine are set to do everything automatically,
a technique that didn't work on the 2000 system, which is why I started a
manual approach, and looked elsewhere on the machine for data to enter.
Moreover the XP dialog boxes don't always match those of W2000: the DNS box
is blank and DHCP shows up in Advanced IP settings, which is not an option
in my W2000 setup. I thought I was matching the machines when I applied
those Router Manager DNS settings. I guess it's the ipconfig display on the
working machine that should guide me.
Miles

 

[Pegasus \(MVP\)]

Pegasus, the previous reply to which you refer advised me to look at the DNS
entry on successful PCs. The difficulty there is that the settings in LAN
Properties on the XP working machine are set to do everything automatically,
a technique that didn't work on the 2000 system, which is why I started a
manual approach, and looked elsewhere on the machine for data to enter.
Moreover the XP dialog boxes don't always match those of W2000: the DNS box
is blank and DHCP shows up in Advanced IP settings, which is not an option
in my W2000 setup. I thought I was matching the machines when I applied
those Router Manager DNS settings. I guess it's the ipconfig display on the
working machine that should guide me.
Miles

Indeed: ipconfig /all will tell you everything.

 

[MilesG]

Indeed: ipconfig /all will tell you everything.

Thanks for all your help Pegasus. I'll report back here when I get a result.
Miles

 

[MilesG]

Thanks for all your help Pegasus. I'll report back here when I get a
result.
Miles

Well, I got a result. The system was given to me by a friend who had
complained that it was no good, required a new hard drive, was full of
viruses and wouldn't even boot properly. So, after trying a few different
valid DNS addresses, and soon realising that the problem must be elsewhere,
I considered malware. Before the earlier postings here I had removed a fair
bit of crud with Adaware and Norton (both very out of date because it
couldn't LiveUpdate of course). However, looking through the file system in
some depth, I could see several suspicious files, some of which seemed to be
trojan diallers. Knowing that ewido was good, I installed that earlier this
evening from a download on one of the other systems, and ran it. It found 49
malicious objects, many of them diallers. I reinstalled the Wireless PCI
card (having switched it to the W98SE system to check that was operating OK)
and very soon saw a system tray popup saying AVG had updated, so I knew I
was connected. The settings were still manually configured, so I changed to
auto IP and auto DNS and all was still fine.
Thanks again Pegasus for persevering. If you are interested in the files
that ewido removed that were plainly causing the problem I'll gladly, albeit
a bit embarrassedly, post or email them, but they are not pretty reading.
Miles

 

[Pegasus \(MVP\)]

Well, I got a result. The system was given to me by a friend who had
complained that it was no good, required a new hard drive, was full of
viruses and wouldn't even boot properly. So, after trying a few different
valid DNS addresses, and soon realising that the problem must be elsewhere,
I considered malware. Before the earlier postings here I had removed a fair
bit of crud with Adaware and Norton (both very out of date because it
couldn't LiveUpdate of course). However, looking through the file system in
some depth, I could see several suspicious files, some of which seemed to be
trojan diallers. Knowing that ewido was good, I installed that earlier this
evening from a download on one of the other systems, and ran it. It found 49
malicious objects, many of them diallers. I reinstalled the Wireless PCI
card (having switched it to the W98SE system to check that was operating OK)
and very soon saw a system tray popup saying AVG had updated, so I knew I
was connected. The settings were still manually configured, so I changed to
auto IP and auto DNS and all was still fine.
Thanks again Pegasus for persevering. If you are interested in the files
that ewido removed that were plainly causing the problem I'll gladly, albeit
a bit embarrassedly, post or email them, but they are not pretty reading.
Miles

Thanks for the update. No need to send me a list of files.
I deeply distrust machines that have been upgraded from
Win98 or infected with viruses - too much trouble. I usually
reload the OS in such cases.