your default gateway generally has to be on the same subnet as the one
you're on. can you ping the default gateway? tracert?
I bet what you need you need a static route defined in the client
machines so they can find their way to anything else other than their
default gateway
I am not familiar with a LANmodem, but if it has an ip address, it
would need to be defined as an ethernet interface in NT or I don't see
how NT could route traffic to it, especially as a 'backup gateway'.
On Fri, 15 Feb 2002 11:50:30 -0500, "Brent Atkerson"
>I am able to ping from the wireless client to the wired card in the NT box.
>WinNT can ping the 3Com LANmodem fine, however, I am not able to ping the
>modem from the wireless client. From within WinNT (Start>Find>Computer) I
>can instantly find anything on the wired side and NOTHING on the wired side.
the browsing does not work because you need a lmhosts entry, or a
master browser in each subnet. (or have your NT server be a member of
a workgroup on both subnets( by default you cannot browse across
subnets in microsoft networking using ip
>NT Box:
> wired NIC address is 192.168.1.xx
> default gateway 192.168.2.xx (wireless card in NT box)
> backup gateway 192.168.1.xx (LANmodem)
> subnet mask of 255.255.255.0
>wireless card address is 192.168.2.xx
> default gateway 192.168.1.xx (wired card in NT box)
> backup gateway 192.168.1.xx (LANmodem)
> subnet mask of 255.255.255.0
>wireless client is 192.168.2.xx
> default gateway 192.168.2.xx (wireless card in NT box)
> backup gateway 192.168.1.xx (LANmodem)
> subnet mask of 255.255.255.0
>Any suggestions?
>Many thanks in advance,
>Brent
>> Well (egg on my face and the fact I am not an NT Super Guru), it was an
>> issue of default gateways not being in the correct order and not
>re-applying
>> the latest service pack.
>> Thanks for your help,
>> Brent
>> > Hi,
>> > Can you ping the wireless adapter IP (in the server) from any client on
>> the
>> > wired side? If not then its a basic routing problem - i.e. NT isn't
>> > forwarding to that card. Given that NT isn't corrupt (and you have
>ticked
>> > the routing box) then it may be the driver causing issues.
>> > al.
>> > > Hello all,
>> > > I recently installed an ISA adapter and an Orinoco Gold PC_CARD in an
>NT
>> > 4.0
>> > > SP6a server box and the same type of hardware in a Win98 machine and
>> > enabled
>> > > IP forwarding in the NT box. I have the cards talking to each other.
>> The
>> > > wired side of the NT box communicates normally with the wired clients
>> and
>> > > the wireless side communicates with the wireless clients, however the
>> > wired
>> > > clients can not talk to the wireless client and vice-versa. Does
>anyone
>> > > have a clue what could be wrong? I have already been on the phone
>(for
>> > > about 1.5 hours) with CDW (the company we bought the wireless hardware
>> > from)
>> > > and they are continuing to work on it. I can ping the wireless client
>> by
>> > > name or address with no errors and I can ping the wired clients by
>name
>> or
>> > > address with no errors from the NT box. If I try
>Start>Find>Computers,
>> on
>> > > the NT box, I can find anything on the wired network but can *not find
>> > > anything* on the wireless side.
>> > > Hardware is;
>> > > HP Netserver E60 with integrated 10/100 network card PII/400, 640 MB
>> > RAM...
by