Server not able to see wireless clients. Wireless able to see server?

[chipowaz]

I'm running Windows Server 2003 SBS.

I just installed a Linksys Wireless G Access Point that is attached to my switch.

Here is the current setup:

(DSL) -> (Linksys Router) -> [Windows Server 2003] -> (10/100/1000 Switch) -> (Linksys WAP54G Access Point) ->(Workstation Clients)

1. Wireless clients are able to see the server, login, and perform all of their tasks normally (able to ping the server).

2. However, the SERVER is not able to see the wireless clients (not able to ping wireless workstations).

I'm trying to connect to the wireless workstations from the server via Remote Desktop Connection.

Can anyone think of why this is happening and how to resolve it? Any thoughts or comments are greatly appreciated.

 

[markdmac]

First thing that comes to mind is make sure you have DHCP turned off on your WAP. SBS will shut down its own DHCP if it detects another DHCP server.

You should take a look at the prescriptive guidance for Small IT. If goes into detail about setting up wireless securely with SBS.

http://www.microsoft.com/technet/itsolutions/smbiz/sitsol/LPDesigning.mspx

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark

 

[chipowaz]

Mark,

DHCP is turned off on the WAP. SBS is running on static IP, DHCP is turned off.

The server is still unable to see my wireless clients and connect remotely to them . Wireless clients can see the server just fine.

Any thoughts?

WAP has teh following configuration:

IP Address: 10.0.0.61
Subnet Mask: 255.255.255.0
Default Gateway: 10.0.0.2

Wireless Clients have IP addresses:
10.0.0.63
10.0.0.64

I'm thinking that the WAP is not acting as transparently as it is suppose to and it is not passing on the request to the wireless clients.

Any thoughts? Thanks so much.

 

[hunterdw]

Before you think too hard... check for Win XP Service Pack 2 on the workstations.

If they SP2, then the firewall by default turns off access to ICMP - you can't ping it.

It can ping you, but you can't ping it.

Give that a go first.