Workstation sees wireless router but can not connect

  • Thread starter Thread starter Guest
  • Start date Start date
Toggle sidebar Toggle sidebar
G

Guest

Guest
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

I have a Windows'98SE computer with Linksys WMP11 wireless card and
Linksys BEFW11S4 router.

I can see the SSID of the router (with 50%-70% signal) but can not
connect.

Any suggestions on troubleshooting this situation?
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Using the proper type of encryption and password/passphrase to connect?

--
Richard G. Harper [MVP Shell/User] rgharper@gmail.com
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Eugene F." <pm771.am@gmail.com> wrote in message
news:1117135815.295529.131770@g14g2000cwa.googlegroups.com...
>I have a Windows'98SE computer with Linksys WMP11 wireless card and
> Linksys BEFW11S4 router.
>
> I can see the SSID of the router (with 50%-70% signal) but can not
> connect.
>
> Any suggestions on troubleshooting this situation?
>
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Richard,

Thank you very much for the response.

> Using the proper type of encryption and password/passphrase to connect?

Both Router and workstation have WEP disabled. No MAC filtering on the
router either.

Eugene
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Eugene F. wrote:
> Richard,
>
> Thank you very much for the response.
>
>> Using the proper type of encryption and password/passphrase to
>> connect?
>
> Both Router and workstation have WEP disabled. No MAC filtering on the
> router either.
>
> Eugene

Disable the ethernet NIC and modem, if any, reboot. What does the DHCP
client table in the router show about the new wireless? Do you see the
wireless NIC in the active wireless MAC table? Enable Netbios over
TCP/IP on the workstation. Run command, winipcfg /all and post the
results.

Q
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Q,

Thank you very much for the reply.

I do not have other NIC cards (nor on-board chips). I just have
LinkSys Wireless PCI card ver. 2.7.

IP Config shows three Ethernet adaptors: two of them - "PPP" and my
wireless card.

<<< What does the DHCP client table in the router show about the new
wireless? >>>

Wireless is listed there with proper IP Address (192.168.1.102) and
correct MAC.

<<< Do you see the wireless NIC in the active wireless MAC table? >>>

Yes, it is listed as #1.

<<< Enable Netbios over TCP/IP on the workstation. >>>

Not sure how to do it.

<<< Run command, winipcfg /all and post the results. >>>

Here it goes:

IP Address: 192.168.1.102
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DHCP Server: 192.168.1.1
Primary WINS server: <blank>
Secondary WINS server: <blank>

I reinstalled the card driver (as advised by Linksys Tech Support) to
no avail.

Right now I have intermittent and mostly negative results:
1. Occasionally I can establish connection with the router
2. When connection established - PING returns either only timouts (most
of the time)or timeouts and normal tramsmissions. No pattern can be
observed.

I have NIS (Norton Internet Security) 2003. Disabling does not solve
the problem.

I noticed Microsoft security patch KB891711 in both StartUp (via
MSConfig) and Add/Delete Software (Control Panel). Uninstalling it did
not help either.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Eugene F. wrote:
> Q,
>
> Thank you very much for the reply.
>
> I do not have other NIC cards (nor on-board chips). I just have
> LinkSys Wireless PCI card ver. 2.7.
>
> IP Config shows three Ethernet adaptors: two of them - "PPP" and my
> wireless card.
>
> <<< What does the DHCP client table in the router show about the new
> wireless? >>>
>
> Wireless is listed there with proper IP Address (192.168.1.102) and
> correct MAC.
>
> <<< Do you see the wireless NIC in the active wireless MAC table? >>>
>
> Yes, it is listed as #1.
>
> <<< Enable Netbios over TCP/IP on the workstation. >>>
>
> Not sure how to do it.
>
> <<< Run command, winipcfg /all and post the results. >>>
>
> Here it goes:
>
> IP Address: 192.168.1.102
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.1.1
> DHCP Server: 192.168.1.1
> Primary WINS server: <blank>
> Secondary WINS server: <blank>
>
> I reinstalled the card driver (as advised by Linksys Tech Support) to
> no avail.
>
> Right now I have intermittent and mostly negative results:
> 1. Occasionally I can establish connection with the router
> 2. When connection established - PING returns either only timouts
> (most of the time)or timeouts and normal tramsmissions. No pattern
> can be observed.
>
> I have NIS (Norton Internet Security) 2003. Disabling does not solve
> the problem.
>
> I noticed Microsoft security patch KB891711 in both StartUp (via
> MSConfig) and Add/Delete Software (Control Panel). Uninstalling it
> did not help either.

Find the application winsockxpfix.exe via Google. This will fix the
underlying programming for TCP/IP.

Q
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Eugene F. wrote:
> I have a Windows'98SE computer with Linksys WMP11 wireless card and
> Linksys BEFW11S4 router.
>
> I can see the SSID of the router (with 50%-70% signal) but can not
> connect.
>
> Any suggestions on troubleshooting this situation?
>

You've been given some good suggestions.
I've had problems that were fixed by flashing the access point.
I also have a bunch of usb wireless interfaces that work well on some
computers and not at all on others. That's why we have junk piles ;-)
mike

--
Return address is VALID but some sites block emails
with links. Delete this sig when replying.
..
Wanted, PCMCIA SCSI Card for HP m820 CDRW.
FS 500MHz Tek DSOscilloscope TDS540 Make Offer
Wanted 12" LCD for Compaq Armada 7770MT.
Bunch of stuff For Sale and Wanted at the link below.
MAKE THE OBVIOUS CHANGES TO THE LINK
ht<removethis>tp://www.geocities.com/SiliconValley/Monitor/4710/
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Mike,

<<< I also have a bunch of usb wireless interfaces that work well on
some
computers and not at all on others >>>

I had this very configuration working just fine (the same wireless
card, the same desktop, the same physical location). Probably should
look deeper into Win'98SE networking settings.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Q,

<<< Find the application winsockxpfix.exe via Google. This will fix
the
underlying programming for TCP/IP. >>>

Thanks for the tip. Will give it a try and report back.

Eugene
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

"Eugene F." <pm771.am@gmail.com> wrote in message
news:1118104443.795422.260520@g14g2000cwa.googlegroups.com...
> Q,
>
> Thank you very much for the reply.
>
> I do not have other NIC cards (nor on-board chips). I just have
> LinkSys Wireless PCI card ver. 2.7.
>
> IP Config shows three Ethernet adaptors: two of them - "PPP" and my
> wireless card.
>
> <<< What does the DHCP client table in the router show about the new
> wireless? >>>
>
> Wireless is listed there with proper IP Address (192.168.1.102) and
> correct MAC.
>
> <<< Do you see the wireless NIC in the active wireless MAC table? >>>
>
> Yes, it is listed as #1.
>
> <<< Enable Netbios over TCP/IP on the workstation. >>>
>
> Not sure how to do it.
>
> <<< Run command, winipcfg /all and post the results. >>>
>
> Here it goes:
>
> IP Address: 192.168.1.102
> Subnet Mask: 255.255.255.0
> Default Gateway: 192.168.1.1
> DHCP Server: 192.168.1.1
> Primary WINS server: <blank>
> Secondary WINS server: <blank>
>
> I reinstalled the card driver (as advised by Linksys Tech Support) to
> no avail.
>
> Right now I have intermittent and mostly negative results:
> 1. Occasionally I can establish connection with the router
> 2. When connection established - PING returns either only timouts (most
> of the time)or timeouts and normal tramsmissions. No pattern can be
> observed.
>
> I have NIS (Norton Internet Security) 2003. Disabling does not solve
> the problem.
>
> I noticed Microsoft security patch KB891711 in both StartUp (via
> MSConfig) and Add/Delete Software (Control Panel). Uninstalling it did
> not help either.
>

Have you tried running the Home Networking wizard that comes with NIS? Been
awhile since I've run Win98, but I seem to remember a similiar problem I had
with an older Linksys BEFW11S4 router and Win98 and doing that cleared up
the problem for me. For some reason disabling NIS didn't help but running
that wizard did.

Good luck.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Riffrafter wrote:
> "Eugene F." <pm771.am@gmail.com> wrote in message
> news:1118104443.795422.260520@g14g2000cwa.googlegroups.com...
>
>>Q,
>>
>>Thank you very much for the reply.
>>
>>I do not have other NIC cards (nor on-board chips). I just have
>>LinkSys Wireless PCI card ver. 2.7.
>>
>>IP Config shows three Ethernet adaptors: two of them - "PPP" and my
>>wireless card.
>>
>><<< What does the DHCP client table in the router show about the new
>>wireless? >>>
>>
>>Wireless is listed there with proper IP Address (192.168.1.102) and
>>correct MAC.
>>
>><<< Do you see the wireless NIC in the active wireless MAC table? >>>
>>
>>Yes, it is listed as #1.
>>
>><<< Enable Netbios over TCP/IP on the workstation. >>>
>>
>>Not sure how to do it.
>>
>><<< Run command, winipcfg /all and post the results. >>>
>>
>>Here it goes:
>>
>>IP Address: 192.168.1.102
>>Subnet Mask: 255.255.255.0
>>Default Gateway: 192.168.1.1
>>DHCP Server: 192.168.1.1
>>Primary WINS server: <blank>
>>Secondary WINS server: <blank>
>>
>>I reinstalled the card driver (as advised by Linksys Tech Support) to
>>no avail.
>>
>>Right now I have intermittent and mostly negative results:
>>1. Occasionally I can establish connection with the router
>>2. When connection established - PING returns either only timouts (most
>>of the time)or timeouts and normal tramsmissions. No pattern can be
>>observed.
>>
>>I have NIS (Norton Internet Security) 2003. Disabling does not solve
>>the problem.
>>
>>I noticed Microsoft security patch KB891711 in both StartUp (via
>>MSConfig) and Add/Delete Software (Control Panel). Uninstalling it did
>>not help either.
>>
>
>
> Have you tried running the Home Networking wizard that comes with NIS? Been
> awhile since I've run Win98, but I seem to remember a similiar problem I had
> with an older Linksys BEFW11S4 router and Win98 and doing that cleared up
> the problem for me. For some reason disabling NIS didn't help but running
> that wizard did.
>
> Good luck.
>
>
>
WinXP also has a network setup wizard that will prepare a script for
Win98 machines.. That might be worth a try if a WinXP machine is available.


--
Ron Hunter rphunter@charter.net
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Yes. I ran through the entire uninstall/reinstall process:

1. Unistalled the software
2. Removed the wireless card
3. Reinstalled the software
4. Reinstalled the card
5. Re-run the wizard
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

>From my older posting:

<<< 2. When connection established - PING returns either only timouts
(most of the time)or timeouts and normal tramsmissions. No pattern can
be observed. >>>

Here is an example:


-----------------------------------------
Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=2ms TTL=150
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=9ms TTL=150
Reply from 192.168.1.1: bytes=32 time=11ms TTL=150
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=13ms TTL=150
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
Reply from 192.168.1.1: bytes=32 time=4ms TTL=150
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2ms TTL=150


Ping statistics for 192.168.1.1:

Packets: Sent = 31, Received = 7, Lost = 24 (77% loss),

Approximate round trip times in milli-seconds:

Minimum = 2ms, Maximum = 13ms, Average = 1ms

Control-C
-----------------------------------------
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Q,

<<< Find the application winsockxpfix.exe via Google. This will fix
the underlying programming for TCP/IP. >>>

I used LSPFix utility that seems to fix the same type of problem as
WinsockXPFix but is suitable for Win '98SE. It did not find any
problems. Should I try WinsockXPFix nevertheless?

TIA, Eugene
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

if you r using a firewall...then there is a possibility that it mite b
causing a problem.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

<<< if you r using a firewall...then there is a possibility that it
mite b causing a problem. >>>

I use Norton Internet Security (NIS) 2003 that has a firewall
component. The erratic behavior I experience happens both with NIS
enabled and disabled.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

This looks like a bad signal!

We had a similar problem with a LAN at a multi-OS company network. When
a faulty cable was replaced it worked perfect.

So you should just move your computer closer to the router and remove
obstructions. In case it is obvious the signal should be just fine, it
could also be possible that the wireless antenna is damaged.

I _DOUBT_ this has anything to do with software.

Eugene F. wrote:
> Here is an example:
>
>
> -----------------------------------------
> Pinging 192.168.1.1 with 32 bytes of data:
>
> Reply from 192.168.1.1: bytes=32 time=2ms TTL=150
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.1: bytes=32 time=9ms TTL=150
> Reply from 192.168.1.1: bytes=32 time=11ms TTL=150
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.1: bytes=32 time=13ms TTL=150
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.1: bytes=32 time=3ms TTL=150
> Reply from 192.168.1.1: bytes=32 time=4ms TTL=150
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.1.1: bytes=32 time=2ms TTL=150
>
>
> Ping statistics for 192.168.1.1:
>
> Packets: Sent = 31, Received = 7, Lost = 24 (77% loss),
>
> Approximate round trip times in milli-seconds:
>
> Minimum = 2ms, Maximum = 13ms, Average = 1ms
>
> Control-C
> -----------------------------------------
>


--
Model: INFJ
Primary function: Coprocessor
Secondary function: Cluster commander

Yes I'm a therian:
http://www.wikitherian.org

Powered by Deamons(TM).

....to live your life fast
and powerfull; and then
live your life just to keep
the Deamons at bay.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

<<< This looks like a bad signal! >>>

Another networked computer in the same room still works fine and this
computer used to work at this very location.

<<< ... it could also be possible that the wireless antenna is damaged.
>>>

I get a signal just no the reliable connection. It takes multiple
attempts to establish the connection and then it either extremely
sluggish from the beginning or works for a very short period of time
and then deteriorates.

Could a bad antenna produce such bizarre effect?
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Thank you very much for your input.

<<< A broken antenna would cause the computer to get a much weaker
signal. >>>

NIC software shows the strength of a signal. While it's not great it
used to be good enough for a stable connection.

<<< Too much computer cables around the antenna, improper grounding, a
metal cage of any form around the antenna, audio speakers nearby or
anything else that causes radio interference may also be to blame,
check that first. >>>

While almost everything on your list applies to my case (antenna is at
the back of the desktop with all the other cables around), the same
setup (no matter how bad it is) used to work fine.

Eugene
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

<<< My bet is on the wireless card. Try replacing it with the one of
the other computer and try if it has the same effect. >>>

Thank you for the suggestion. Unfortunately this is the only _wireless
desktop_ I have.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

"Eugene F." <pm771.am@gmail.com> wrote in message
news:1119646541.877216.218280@g44g2000cwa.googlegroups.com...
> <<< My bet is on the wireless card. Try replacing it with the one of
> the other computer and try if it has the same effect. >>>
>
> Thank you for the suggestion. Unfortunately this is the only _wireless
> desktop_ I have.
>

Have you tried changing WIFI channels? You may be getting interference from
cell phones or other WIFI signals.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Eugene F. wrote:
> <<< This looks like a bad signal! >>>
>
> Another networked computer in the same room still works fine and this
> computer used to work at this very location.
>
> <<< ... it could also be possible that the wireless antenna is damaged.
>
>
> I get a signal just no the reliable connection. It takes multiple
> attempts to establish the connection and then it either extremely
> sluggish from the beginning or works for a very short period of time
> and then deteriorates.
>
> Could a bad antenna produce such bizarre effect?

The way your pinging goes it makes it obvious that something is wrong
with getting the packets accross. All the connection attempting and
sluggish behaviour is just a side-effect of that (Ethernet works in a
way that it resends requests that fail to get across, so if the computer
is retrying several hundred times every packet it sends, then the result
is that it is either slow or just times out).

In the case of netwok cables, a wrong wiring, cable warped around a
metal object, an overpowered network (as in... 30 volts instead of 20...
this is more common in old telephone networks) or a screwed up cable
will cause exactly the effect you describe. In the case of wireless
interenet there are no cables thus it is only possible that this is
radio interference or poor signal reception.

And if another computer gets signal okay, and the other acts like it
doesn't I think a broken antena is to blame. A broken antena would cause
the computer to get a much weaker signal.

Too much computer cables around the antena, inproper grounding, a metal
cage of any form around the antena, audio speakers nearby or anything
else that causes radio interference may also be to blame, check that first.

--
Model: INFJ
Primary function: Coprocessor
Secondary function: Cluster commander

Yes I'm a therian:
http://www.wikitherian.org

Powered by Deamons(TM).

....to live your life fast
and powerfull; and then
live your life just to keep
the Deamons at bay.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

<<< Have you tried changing WIFI channels? >>>

Yes. I changed it from 6 (Linksys default) to 1.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Mike Rush wrote:

> Have you tried changing WIFI channels? You may be getting interference
> from cell phones or other WIFI signals.

It wouldn't be cell phones, though cordless phones are a possibility.
 
Archived from groups: comp.dcom.modems.cable,microsoft.public.win98.gen_discussion (More info?)

Eugene F. wrote:
> Thank you very much for your input.
>
> <<< A broken antenna would cause the computer to get a much weaker
> signal. >>>
>
> NIC software shows the strength of a signal. While it's not great it
> used to be good enough for a stable connection.
>
> <<< Too much computer cables around the antenna, improper grounding, a
> metal cage of any form around the antenna, audio speakers nearby or
> anything else that causes radio interference may also be to blame,
> check that first. >>>
>
> While almost everything on your list applies to my case (antenna is at
> the back of the desktop with all the other cables around), the same
> setup (no matter how bad it is) used to work fine.

My bet is on the wireless card. Try replacing it with the one of the
other computer and try if it has the same effect.

There is nothing in software that could cause that effect and the
problem is characteristic of poor network wiring.

--
Model: INFJ
Primary function: Coprocessor
Secondary function: Cluster commander

Yes I'm a therian:
http://www.wikitherian.org

Powered by Deamons(TM).

....to live your life fast
and powerfull; and then
live your life just to keep
the Deamons at bay.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom