Gary's suggestion for DUN and Winipcfg were relevant, possibly other issues
may also apply.
You might have residual settings from the old hard wired networking
conflicting with your new attempted wireless. Also, if your running a
firewall and/or some AV progs, it would be prudent to make sure they are not
interfering.
If it is no longer connected through hard wire:
Delete all networking in Control Panel > Network, then reinstall for your
adapter, making sure you have configured TCP/IP, DNS, Gateway, and other,
for the new wireless network. Also make sure you are using the correct
protocol, size and related, and security, compared with the other computers,
and router and/or wireless server.
Also make sure your hosts [or lmhosts] file [if using] has allowed
connection or is otherwise not interferring.
Additionally, ensure your workgroup and server name for the target 98 box
are part of the wireless network.
That referenced News Group by Gary, has 4654 headings, rather duanting, so
rather than looking for already supplied answers, post a new query if
necessary, should you choose to go there for answers. You could attempt a
search for related and relevant articles.
--
MEB
http://peoplescounsel.orgfree.com/
BLOG -
http://peoplescounsel.spaces.live.com/ Public Notice or the "real
world"
"Most people, sometime in their lives, stumble across truth.
Most jump up, brush themselves off, and hurry on about their business as if
nothing had happen." Winston Churchill
Or to put it another way:
Morpheus can offer you the two pills;
but only you can choose whether you take the red pill or the blue one.
_______________
"Jamie Benson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
| Well thanks for the info anyways. I will give it a few more days on
| here and then post in the group you suggested. Thanks again for your
| help! Have a good one.
|
| Jami
|
| On Jan 29, 11:08 am, "Gary S. Terhune" <grystn...@mvps.org> wrote:
| > Not me. I shot my wad with that one. Steve is the most knowledgeable one
| > here, usually. If he doesn't stop in to this thread soon, consider
| > reposting, and also consider posting to the following NG, since it will
have
| > the most number of networking gurus attending (outside of domain admin
types
| > in the server groups, which you might also want to check out.) These
folks
| > didn't start doing this stuff only a couple of years ago with XP/2003
and
| > wireless. They've been doing networking for years and know it inside
out.
| >
| > microsoft.public.windowsxp.network_web
| >
| > My last suggestion is to get a real newsreader like Outlook Express or
Forte
| > Agent, etc., to make finding and reading these NGs a lot easier. If you
| > already have OE installed, click here:
| >
news://msnews.microsoft.com/microsof...xp.network_web
| >
| > --
| > Gary S. Terhune
| > MS MVP --
Shell/Userhttp://grystmill.com/articles/cleanboot.htmhttp://grystmill.com/ar
ticles/security.htm
| >
| > "Jamie Benson" <JamiLuvsNasca...@gmail.com> wrote in
messagenews:(E-Mail Removed) glegroups.com...
| >
| > > Gary,
| > > Thank you very much for your response to my issue. I rebuilt the
| > > TCP/IP stack via the instructions the MS KB article and I am still
| > > unable to connect to the Internet or my network here at work. Are
| > > there any other KB articles you could suggest or any further
| > > suggestions you or anyone else anyone else may have? I really
| > > appreciate your input.
| >
| > > Jami Benson
| >
| > > On Jan 26, 9:01 pm, "Gary S. Terhune" <grystn...@mvps.org> wrote:
| > > > From the previous thread in this group, "Having issues with
WINIPCFG", a
| > > > solution suggested by MS-MVP Steve Winograd to rebuild the TCP/IP
stack:
| >
| > > > "Try this procedure to repair TCP/IP, even if you don't use Dial-Up
| > > > Networking. It's a subset of the full procedure for removing and
| > > > re-installing the TCP/IP stack shown here:
| >
| > > > "Fatal Error" Error Message Occurs When You
RunWINIPCFGhttp://support.microsoft.com/kb/286748/en-us
| >
| > > > I've found the subset to be effective in fixing many TCP/IP
problems.
| >
| > > > 1. Un-install Internet Connection Sharing (if installed).
| > > > 2. Un-install Dial-Up Networking. Don't reboot.
| > > > 3. Delete registry key
HLM\System\CurrentControlSet\Services\Winsock2
| > > > 4. Re-install Dial-Up Networking. Reboot.
| > > > 5. Re-install Internet Connection Sharing (if desired).
| >
| > > > --
| > > > Gary S. Terhune
| > > > MS
MVP --Shell/Userhttp://grystmill.com/articles/cleanboot.htmhttp://grystmill.
com/ar
| > ticles/security.htm
| >
| > > > "Jamie Benson" <JamiLuvsNasca...@gmail.com> wrote
inmessagenews:1169830151.872729.280510@k78g2000cwa .googlegroups.com...
| >
| >
| >
| > > > > I have a PC that is running 98SE and it is giving me issues
connecting
| > > > > to our wireless network here at my place of business. We have
maybe 25
| > > > > other machines that are all running 98SE and our connected to the
| > > > > network fine. The PC I am having issues with can associate to the
AP,
| > > > > but can not authenticate. It has a Cisco Aironet 350 PCI card. I
KNOW
| > > > > that the AP settings are fine since the other PC's are being
| > > > > cooperative. This PC is new to the wireless network, but has been
| > > > > working fine with it wired into the network. The settings are the
same
| > > > > as every other PC that is working and TCP/IP is bound to the
Aironet
| > > > > card. If anyone has seen anything like this before or has any
ideas I
| > > > > would be super appreciative. Thanks!!
| >
| > > > > Jami Benson
|
Similar Threads
Linear Mode
