Access Point IP Address

I've currently got a small wired network (3 computers) and intend to
very soon purchase a wireless Access Point.

At the moment I am using fixed IP addresses within the 192.160.0.xxx
range rather than the DHCP method, this is more for learning reasons
than anything else.

When I get the access point I assume it plugs in to my existing hub
and gets allocated an IP address.

If one of my wireless devices need to connect to a wired device (I use
VNC quite a bit) do I give it the actual address or do I have to route
it through the Access Point?

Geoff Lane

In article <(E-Mail Removed)>, Geoff Lane
<(E-Mail Removed)> wrote:
>I've currently got a small wired network (3 computers) and intend to
>very soon purchase a wireless Access Point.
>
>At the moment I am using fixed IP addresses within the 192.160.0.xxx
>range rather than the DHCP method, this is more for learning reasons
>than anything else.
>
>When I get the access point I assume it plugs in to my existing hub
>and gets allocated an IP address.
>
>If one of my wireless devices need to connect to a wired device (I use
>VNC quite a bit) do I give it the actual address or do I have to route
>it through the Access Point?
>
>Geoff Lane

Hi, Geoff. I assume that you're really asking about a wireless access
point, not a wireless router. An access point is like a wireless hub,
and it doesn't do routing, NAT, etc.

An access point might or might not get its own IP address -- I have
access points that work both ways. If it does get an IP address, the
reason is probably to let you connect to the access point's built-in
web server to configure it. For example, I use http://192.168.123.250
to configure one of mine.

However, that's not relevant to computer-to-computer access. To
connect to another computer, use that computer's IP address. As long
as the access point's IP address is in the same subnet as the
computers, no additional configuration is necessary.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

In article <(E-Mail Removed)>, Geoff Lane
<(E-Mail Removed)> wrote:
>I've currently got a small wired network (3 computers) and intend to
>very soon purchase a wireless Access Point.
>
>At the moment I am using fixed IP addresses within the 192.160.0.xxx
>range rather than the DHCP method, this is more for learning reasons
>than anything else.
>
>When I get the access point I assume it plugs in to my existing hub
>and gets allocated an IP address.
>
>If one of my wireless devices need to connect to a wired device (I use
>VNC quite a bit) do I give it the actual address or do I have to route
>it through the Access Point?
>
>Geoff Lane

Here's something that I forgot to mention in my first reply: if your
access point does have an IP address, I strongly recommend assigning
it a static IP address. That way, you'll always know what its IP
address is. With DHCP, its IP address can change at any time, making
it hard to find the access point on the network.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com

Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm

On Mon, 21 Jul 2003 01:51:47 -0600, "Steve Winograd [MVP]"
<(E-Mail Removed)> wrote:

>>I've currently got a small wired network (3 computers) and intend to
>>very soon purchase a wireless Access Point.
>>
>>At the moment I am using fixed IP addresses within the 192.160.0.xxx
>>range rather than the DHCP method, this is more for learning reasons
>>than anything else.
>>
>>When I get the access point I assume it plugs in to my existing hub
>>and gets allocated an IP address.
>>
>>If one of my wireless devices need to connect to a wired device (I use
>>VNC quite a bit) do I give it the actual address or do I have to route
>>it through the Access Point?

>Hi, Geoff. I assume that you're really asking about a wireless access
>point, not a wireless router. An access point is like a wireless hub,
>and it doesn't do routing, NAT, etc.

At the moment I have a machine that dual boots (Win98/Linux) that I
use as the server, when it connects to the internet it performs NAT
for the others within the network.

I assume that when I get my wireless system going any wireless device
goes via the access point into the wired system then NAT is performed
if it subsequently goes out onto the internet.

Geoff Lane

On Mon, 21 Jul 2003 02:10:45 -0600, "Steve Winograd [MVP]"
<(E-Mail Removed)> wrote:


>>I've currently got a small wired network (3 computers) and intend to
>>very soon purchase a wireless Access Point.
>>
>>At the moment I am using fixed IP addresses within the 192.160.0.xxx
>>range rather than the DHCP method, this is more for learning reasons
>>than anything else.

>Here's something that I forgot to mention in my first reply: if your
>access point does have an IP address, I strongly recommend assigning
>it a static IP address. That way, you'll always know what its IP
>address is. With DHCP, its IP address can change at any time, making
>it hard to find the access point on the network.

That's what I thought, I know many like the apparent ease of DHCP but
I must admit to liking a bit of control so I can then understand if
things go wrong.

Geoff Lane