Re: Wireless Network Issue - SBS2K3 - Configuration and / or Topol
- From: Roman <Roman@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 11 Dec 2007 14:47:00 -0800
Hi Les,
Thank you for your reply. I am quietly confident that moving the SBS to
wired ethernet will assist. I am also entertaining the thought of upgrading
the home modem/router to a Cisco 877W however I'd be unimpressed if the
problem persisted after doing that.
I must say though that my confidence is increasing that it may resolve the
issue. As mentioned previously I'll be posting my server and a client
ipconfig /all tonight. I'd be grateful if you visit this thread again with
your thoughts.
Thanks again.
"Les Connor [SBS MVP]" wrote:
The router/access point is likely half of the problem, the wireless NIC in.
the SBS is the other half. You shouldn't need to go to a dual NIC SBS to
resolve this.
As Lanwench suggests, and what I use at home, is a Sonicwall TZ 150-W
wireless router. The SBS is hard-wired to the sonicwall, and with a static
IP, and the SBS is the DHCP/DNS server - but everything else in my house is
wireless and it works fine.
Many of the inexpensive SOHO router/access points are trouble. They just
seem to jam up, overheat, or something - and are especially troublesome
where any level of wireless security (encryption) is in use.
--
Les Connor [SBS MVP]
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:eIlv2v$OIHA.4480@xxxxxxxxxxxxxxxxxxxxxxx
Roman <roman@xxxxxxxxxxxxxxx> wrote:
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.
Note that if you're not using ISA, you really want something better
between your network & your modem....I'd look into a decent Sonicwall (or
Watchguard, perhaps).
The
network is completely wireless.
Ouch. Even your server? I *really* discourage this config. I had it
running for a while on my home network and was never happy with it.
Even for workstations, using really reliable wireless kit, it's not the
best idea. What's the reason you aren't using wired Ethernet? It's still
the best solution.
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.
That's fine.
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.
When this happens, can they ping the server by IP address? Name resolution
is a secondary issue. The ipconfig you mention below will help sort this
out, note.
What do you see in the event logs?
Have you tried another router?
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.
I don't see what NAT has to do with this. NAT is provided by your
router....it has nothing to do with your LAN-connected devices.
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.
Why? That sounds like a case of adding *more* complexity to something that
is already having problems, which strikes me as a bad idea.
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?
Highly doubtful.
The server is currently isolated from the network so client machines
can use the Internet reliably.
What does that mean? I thought this was a lab!
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.
Yes, do...from a workstation & the server.
If you're going to use wireless, get a better wireless access point
(again, I'm a fan of Sonicwall) and I still suggest you *not* use it for
all your workstations, and definitely not your server. Save it for the
occasional laptop. It's just so much more reliable to use wired ethernet.
- References:
- Wireless Network Issue - SBS2K3 - Configuration and / or Topology
- From: Roman
- Re: Wireless Network Issue - SBS2K3 - Configuration and / or Topology
- From: Lanwench [MVP - Exchange]
- Re: Wireless Network Issue - SBS2K3 - Configuration and / or Topology
- From: Les Connor [SBS MVP]
- Wireless Network Issue - SBS2K3 - Configuration and / or Topology
- Prev by Date: Re: Please help with my lack of understanding
- Next by Date: Re: SBS 2003 2NIC's
- Previous by thread: Re: Wireless Network Issue - SBS2K3 - Configuration and / or Topology
- Next by thread: Re: Wireless Network Issue - SBS2K3 - Configuration and / or Topology
- Index(es):
Relevant Pages
|
