Wireless computers can't ping 100BaseT computers

[Guest]

I have a UNIDEN WNR2004 router that provides four 100BaseT network connections and 802.11b wireless connections. I have three computers connected via the 100BaseT connections and two computers connected via the 802.11b wireless connections. The router assigns network addressed to all of these computers. Each computer can access the internet through the router

The two 802.11b computers can ping each other
The three 100BaseT computer can ping each other

But the 802.11b computers cannot ping the 100BaseT computers
The 100BaseT computers cannot ping the 802.11b wireless computers

What should I do to allow the 802.11b wireless computers to ping the 100BaseT comptuers

Regards

Rand

 

[Robert Moir]

Randy A. Ynchausti wrote:

What should I do to allow the 802.11b wireless computers to ping the
100BaseT comptuers?

Read the manual that came with the router. Ask their support for help. Look
at the configuration options on the router.

This isn't a Windows problem by the sounds of it but a configuration issue
with the router.


--

 

[Guest]

Robert,

Read the manual that came with the router. Ask their support for help. Look
at the configuration options on the router.

This isn't a Windows problem by the sounds of it but a configuration issue
with the router.

Thanks for the reponse. I have contacted UNIDEN support twice. They keep insisting that the problem is a "Windows file sharing" configuration problem. They are either right, or they can't handle the question. I don't know which.

I do agree with you. Ping should hit the address no matter what type of connection the computer uses.

I hope there is someone out there that can provide some Windows XP Professional configuration information to allow my 802.11b wireless computers to ping my 100BaseT computers.

Regards,

Randy

 

[Robert Moir]

Robert,

ping the >> 100BaseT comptuers?

for help. Look > at the configuration options on the router.

configuration issue > with the router.

Thanks for the reponse. I have contacted UNIDEN support twice. They
keep insisting that the problem is a "Windows file sharing"
configuration problem. They are either right, or they can't handle
the question. I don't know which.

They can't handle the question. Easy to prove that too:
If you can't *ping* something, that has nothing what so ever to do with
Windows File Sharing, because you haven't even tried to share a file yet, so
how can file sharing be broken?

If you have 2 computers side by side on the wire that can ping each other,
and 3 side by side on wireless that can ping each other, but none of the
wireless machines can ping any of the wired ones or vice-versa, then clearly
the problem is on the bridge between the wireless and wired bits of your
setup, not on any individual machine's configuration.

The wired vs. wireless issue should not affect pinging or file sharing at
all because that is the "physical network" that your network traffic is
moving across (or not in this case!)... and file sharing does not know or
care what the physical network is doing... it can either see its target or
it cannot.

I do agree with you. Ping should hit the address no matter what type
of connection the computer uses.

Exactly. Or it could be blocked by the local firewall (in which case no
machine would work, including the ones on the same type of network, which
you say *does* work).

I hope there is someone out there that can provide some Windows XP
Professional configuration information to allow my 802.11b wireless
computers to ping my 100BaseT computers.

I'm afraid not. There is nothing to configure on Windows XP to allow or
block the exact scenario you describe.

On my home network, i have one desktop machine (wired), a Apple iBook
running OSX 10.3, and a laptop that dual boots Win XP Pro and Win 2003 (both
wireless).

My network switch/router thing is a Linksys WRT54G. These 3 computers can
talk to each other and all talk to the internet quite happily without any
extra configuration or fiddling needed just because 1 of them is wired and
the rest wireless. Now if I can get an Apple computer talking to two windows
computers on this system, pinging, sharing files, whatever... and I didn't
have to do anything "special" to do it.... then its clear to me that your
router is either faulty or not configured correctly.


--

 

[Roger Abell]

If you are getting a live network connection with your XP
wireless device, but cannot ping some machines, then the
issue is not XP. As Robert indicates it is an issue with the
network design/topology. A segment is not reachable.
The support people that say it is an MS filesharing issue
either did not listen when you said "ping" or they are
simply incompetent.

--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA

Robert,




Thanks for the reponse. I have contacted UNIDEN support twice. They keep

insisting that the problem is a "Windows file sharing" configuration
problem. They are either right, or they can't handle the question. I don't
know which.

I do agree with you. Ping should hit the address no matter what type of connection the computer uses.

I hope there is someone out there that can provide some Windows XP

Professional configuration information to allow my 802.11b wireless
computers to ping my 100BaseT computers.

 

[Guest]

Not so sure I agree w/ the MS response its not MS. This sounds like the problem I have been having for the last 2 days. My system is netgear. I have a desktop w/ WXP pro connected to broadband w/ wireless 802.11b router between. Then I got a wireless USB adapter (also netgear for xmas.) I can get to the internet perfectly fine using the adapter on my laptop (also WXP pro). But could not get network running. I could ping 1 way (from desktop to laptop), but not in reverse. What we discovered (me and the netgear help person) was that under properties of my network connections lan was that in the box "this connection uses the following items", there were at least 2 items checked in the list that the netgear guy suggested were a problem: Deterministic network enhancer, and another one that had the word advertising in it (sorry cannot remember it, I could not uncheck so I had to delete it). Now I only have 3 things checked : client for ms networks, file and print sharing and internet protocal tcp/ip. After I did this I was able to ping the desktop from the laptop.

Unfortunately, I am still having problems. Personally I believe it is in the MS XP system based on what I saw. I am pretty frustrated by the whole thing. But I will say the netgear guy has given me the most help so far.

If I ever get to the bottom I will try to drop a line in this news group. I am currently trying to fight through sharing folder issues and forcedguest (whatever that means, still struggling for laymans description)

Bob

 

[Roger Abell]

Interesting info Bob.
Note that if you are only referring to this thread, then there
is no MS response here. MVPs are private individuals,
and in no way represent MS.
I use Intel, 3Com, Linksys, and for wireless also MS hardware,
so I have not experienced Uniden or Netgear.
Yes, if the hardware cannot handle having some networking
features loaded into its network stack, and this makes that
hardware confused/unresposive or just wierd, then all bets
are off until the hardware is only loaded with drivers it can
handle.
Many of the network issues people bring here have especially
when it is a partial reachability issue has to do with network
design, gateway, net mask, etc. mistakes.

If you have not yet, then maybe you should start a thread with
subject indicating your filesharing issue, and try to lay out what
you are trying to do that is not working. Also, especially for
file sharing over the network it is very different whether one
has XP Home or Pro so indicating which versions are involved
is a big help.

--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA

Not so sure I agree w/ the MS response its not MS. This sounds like the

problem I have been having for the last 2 days. My system is netgear. I
have a desktop w/ WXP pro connected to broadband w/ wireless 802.11b router
between. Then I got a wireless USB adapter (also netgear for xmas.) I can
get to the internet perfectly fine using the adapter on my laptop (also WXP
pro). But could not get network running. I could ping 1 way (from desktop
to laptop), but not in reverse. What we discovered (me and the netgear help
person) was that under properties of my network connections lan was that in
the box "this connection uses the following items", there were at least 2
items checked in the list that the netgear guy suggested were a problem:
Deterministic network enhancer, and another one that had the word
advertising in it (sorry cannot remember it, I could not uncheck so I had to
delete it). Now I only have 3 things checked : client for ms networks, file
and print sharing and internet protocal tcp/ip. After I did this I was able
to ping the desktop from the laptop.

Unfortunately, I am still having problems. Personally I believe it is in

the MS XP system based on what I saw. I am pretty frustrated by the whole
thing. But I will say the netgear guy has given me the most help so far.

If I ever get to the bottom I will try to drop a line in this news group.

I am currently trying to fight through sharing folder issues and forcedguest
(whatever that means, still struggling for laymans description)

 

[Robert Moir]

Not so sure I agree w/ the MS response its not MS. This sounds like
the problem I have been having for the last 2 days. My system is
netgear. I have a desktop w/ WXP pro connected to broadband w/
wireless 802.11b router between. Then I got a wireless USB adapter
(also netgear for xmas.) I can get to the internet perfectly fine
using the adapter on my laptop (also WXP pro). But could not get
network running. I could ping 1 way (from desktop to laptop), but
not in reverse. What we discovered (me and the netgear help person)
was that under properties of my network connections lan was that in
the box "this connection uses the following items", there were at
least 2 items checked in the list that the netgear guy suggested were
a problem: Deterministic network enhancer, and another one that had
the word advertising in it (sorry cannot remember it, I could not
uncheck so I had to delete it). Now I only have 3 things checked :
client for ms networks, file and print sharing and internet protocal
tcp/ip. After I did this I was able to ping the desktop from the
laptop.

Unfortunately, I am still having problems. Personally I believe it
is in the MS XP system based on what I saw. I am pretty frustrated
by the whole thing. But I will say the netgear guy has given me the
most help so far.

If I ever get to the bottom I will try to drop a line in this news
group. I am currently trying to fight through sharing folder issues
and forcedguest (whatever that means, still struggling for laymans
description)

Hi Bob,
Sorry to hear you are having problems too, but I'm not sure your problems
and Randy's problems are connected. You were having trouble pinging at all,
it seems like, whereas Randy can ping to all computers on the same type of
network as I understand it (e.g. wireless machines can all ping each other,
wired machines can all ping each other) and the trouble for him only appears
when traffic has to "cross the bridge" between his wireless and his wired
network.

Your problem does sound like its at least partially down to machine setup
however, and slightly different.

I've not heard of the "Deterministic network enhancer" and I don't believe
its a standard part of any windows setup, which makes me wonder if you were
connected directly to the internet before via ADSL and your ADSL provider
has a custom setup they apply to your machine... or maybe you connect to a
Virtual Private Network at work and you were given a setup program for this
by your IT dept at work? If either of these is the case then its certainly
possible that whatever got changed by whatever installed this "Deterministic
network enhancer" is a large part of your problem.


--

 

[Guest]

Well, I did install software to access my work pc via virtual private network. And that s/w was on my desktop but not my laptop and the desktop is what I use to access my work pc. So maybe that is where the deterministic network enhancer and other stuff came from.

I will check my work connection to see if I hosed it trying to make a local LAN work.

Bob