Archived from groups: alt.internet.wireless (More info?)
THE COMPUTER THAT IS CONNECTED TO MY WIRELESS ROUTER IS NOT ACCESSIBLE TO
ANY OF THE WIRELESS CONNECTIONS ON MY NETWORK. DOES ANYONE HAVE A CHECKLIST
OF STEPS I COULD USE TO TROUBLESHHOT THIS? THE COMPUTR NAME IS OK ON THE
NETWORK. I CAN ACCESS ALL OF THE WIRELESS CONNECTIONS FROM THIS COMPUTER.
ALL OF THE WIRELESS CONNECTIONS CAN ACCESS EACH OTHER.
Archived from groups: alt.internet.wireless (More info?)
Richard Winsten wrote:
> THE COMPUTER THAT IS CONNECTED TO MY WIRELESS ROUTER IS NOT ACCESSIBLE
> TO ANY OF THE WIRELESS CONNECTIONS ON MY NETWORK. DOES ANYONE HAVE A
> CHECKLIST OF STEPS I COULD USE TO TROUBLESHHOT THIS? THE COMPUTR NAME
> IS OK ON THE NETWORK. I CAN ACCESS ALL OF THE WIRELESS CONNECTIONS
> FROM THIS COMPUTER. ALL OF THE WIRELESS CONNECTIONS CAN ACCESS EACH
> OTHER.
Archived from groups: alt.internet.wireless (More info?)
In article <iIouc.4782$Yd3.565@newsread3.news.atl.earthlink.net>,
Richard Winsten <Rwinsten@pipeline.com> wrote:
:THE COMPUTER THAT IS CONNECTED TO MY WIRELESS ROUTER IS NOT ACCESSIBLE TO
:ANY OF THE WIRELESS CONNECTIONS ON MY NETWORK. DOES ANYONE HAVE A CHECKLIST
F STEPS I COULD USE TO TROUBLESHHOT THIS? THE COMPUTR NAME IS OK ON THE
:NETWORK. I CAN ACCESS ALL OF THE WIRELESS CONNECTIONS FROM THIS COMPUTER.
:ALL OF THE WIRELESS CONNECTIONS CAN ACCESS EACH OTHER.
Is your typing in all upper-case intended to indicate an extrodinary
priority for this matter that could not have been better conveyed by
a mixed-case statement of urgency?
Anyhow. Are the wired and wireless sides in the same IP address range?
If not, then do you have a WINS server configured? You are probably
relying on NETBIOS to have the resources see each others, but NETBIOS
works largely by subnet broadcasts, so if you have multiple subnets
you need WINS servers set up so that the subnets can see each other's
resources.
--
Rump-Titty-Titty-Tum-TAH-Tee -- Fritz Lieber
Archived from groups: alt.internet.wireless (More info?)
"Richard Winsten" <rwinsten@pipeline.com> wrote in
news:iIouc.4782$Yd3.565@newsread3.news.atl.earthlink.net:
> THE COMPUTER THAT IS CONNECTED TO MY WIRELESS ROUTER IS NOT ACCESSIBLE
> TO ANY OF THE WIRELESS CONNECTIONS ON MY NETWORK. DOES ANYONE HAVE A
> CHECKLIST OF STEPS I COULD USE TO TROUBLESHHOT THIS? THE COMPUTR NAME
> IS OK ON THE NETWORK. I CAN ACCESS ALL OF THE WIRELESS CONNECTIONS
> FROM THIS COMPUTER. ALL OF THE WIRELESS CONNECTIONS CAN ACCESS EACH
> OTHER.
>
>
>
Why are you shouting? All capitals mean you're shouting.
If you have WEP or possibly WAP enabled on the wireless, then it can
present an issue with wired and wireless machines trying to see each
other. Did you disable encryption on the wireless to verify that is not
the issue? If the WEP or WAP is the issue, then you may have to change
network protocol from NetBEUI to NWlink IPX SPX NetBIOS compatible on all
machines so that the wired and wireless machine can talk to each other
with WEP or WAP enabled. That was my solution when I faced the issue.
You should protect the NetBIOS ports with a software firewall solution on
all machines, if you use the NetBIOS protocol.
Archived from groups: alt.internet.wireless (More info?)
If you have are running XP make sure that the computers don't have the XP
firewall enabled. Disable the firewall on all local PCs and enable it on
the wireless router.
Tony
"Richard Winsten" <rwinsten@pipeline.com> wrote in message
news:iIouc.4782$Yd3.565@newsread3.news.atl.earthlink.net...
> THE COMPUTER THAT IS CONNECTED TO MY WIRELESS ROUTER IS NOT ACCESSIBLE TO
> ANY OF THE WIRELESS CONNECTIONS ON MY NETWORK. DOES ANYONE HAVE A
CHECKLIST
> OF STEPS I COULD USE TO TROUBLESHHOT THIS? THE COMPUTR NAME IS OK ON THE
> NETWORK. I CAN ACCESS ALL OF THE WIRELESS CONNECTIONS FROM THIS COMPUTER.
> ALL OF THE WIRELESS CONNECTIONS CAN ACCESS EACH OTHER.
>
>
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.