Wireless Network Issue - SBS2K3 - Configuration and / or Topology

Hello Group,

Please forgive posting a similar question again however I wish to refocus my question before purchasing additional hardware unnecessarily, or worse, still not resolving the issue.

The core problem is unreliable wireless connectivity. The suspected cause is incorrect network configuration and / or hardware topology.

I have a single NIC SBS2K3 Premium server with 5 clients and one combined modem/router (Billion 7404VGP-M) on a test network. The network is completely wireless. The router has DHCP disabled but is the default Gateway. The server is successfully providing dynamic DHCP to all client machines and they all subsequently point to SBS for DHCP, DNS; and the router as the Gateway.

The network performs faultlessly with all clients able to login to SBS, access server shares, browse companyweb and access the Internet. At intervals ranging from 1 to several hours a fault will occur resulting in all clients, and server, being unable to ping each other - this happens simultaneously across the network. They can however ping the router and ISP. This results in clients being unable to log on to SBS, access their network shares, or (except for the server) use the Internet. A router reboot will restore the network until the next fault condition.

Colleagues have suggested that my topology will not work quoting issues with NAT. My suggestion of upgrading to small office hardware, such as a Cisco wireless router, was also met with hesitation.

My network knowledge is not strong and I'm consequently considering their suggestion of moving to a two NIC server, with a second wireless router, and using two subnets - one subnet for the internal LAN and the other for the public WAN.

Can my current topology work, if so what could be configured incorrectly. If this topology cannot work, why not? If I move to the suggested 2 NIC solution, with a second similar wireless router, will that resolve the issue?

The server is currently isolated from the network so client machines can use the Internet reliably. The router is providing dynamic DHCP and the fault does not occur. I conclude that no hardware faults or wireless hardware incompatabilities are contributing to the issue affecting the network when the server is included.

Posting ipconfig will require reintroduction of the server to the network which I can do tomorrow if requested.

.

Relevant Pages

  • Re: Connection from remote computer to network SQL Server
    ... There is no firewall on the W2K machine acting as the SQL server. ... I tried making the SQL machine a "trusted" on the router. ... connection works. ... To find the IP address of your computer inside the network, ...
    (microsoft.public.access.adp.sqlserver)
  • RE: Small network with lots of features, questions
    ... Your network sounds overly complicated to me. ... to get to the internet. ... To do that, without using your server as a router, you need ...
    (microsoft.public.windows.server.networking)
  • Re: Still cant connect to RWW or OWA remotely
    ... laptop plugged into port on DSL router. ... service, e-mail, and RWW is available to all users on the network. ... The server is a SBS2003 SP1 Standard box without ISA, ... of the two NICs by clicking the Advanced tabs, it won't open that box, ...
    (microsoft.public.windows.server.sbs)
  • Re: Firewall and ISA
    ... Linksys uses NAT to protect you, claiming it's a firewall, but NAT is ... Full access to the network for maintenance, remotely, over a VPN, so ... dedicated server (meaning that ISA is not certified on a non-dedicated ... Are you saying that in addition to the ISA i need to get a new router? ...
    (microsoft.public.windows.server.sbs)
  • Re: Problems accessing SBS 2003 Welcome screen from Internet
    ... In the router, I opened the ports that you ... Ethernet adapter Server Local Area Connection: ... Ethernet adapter Network Connection: ...
    (microsoft.public.windows.server.sbs)