Re: Wireless connects but only partially

Hello Richard,

Thank you for your update. Also thanks Dave for the good input.

I agree with Dave, we need to set the client get IP address from SBS, but
not set fix IP for the wireless NIC.

Additional, I want to say that:

1. Please let us know your network topology: 1 NIC or 2 on SBS? Your
wireless access point is your broadband router or not?

2. Please post the whole outcome of command "ipconfig /all" from SBS and
the wireless client. We do not know which NIC IP configuration you refer to
in your description.

I appreciate your time and look forward to hearing from you.

Thanks and have a nice day!

Best regards,

Terence Liu (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
Thread-Topic: Wireless connects but only partially
thread-index: AcjXwVl1k1TbOXxiSS6jqY+308ppwA==
X-WBNR-Posting-Host: 207.46.192.207
From: =?Utf-8?B?Umljaw==?= <Rick@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <08C5DD59-4138-4480-894A-5C045FBB52F1@xxxxxxxxxxxxx>
<3D7A8C28-127D-42B6-B3DA-1F6514E50838@xxxxxxxxxxxxx>
<D6C81113-448F-4CFC-97A9-90943A6EEBFD@xxxxxxxxxxxxx>
<F8A12F3E-3ECE-48E6-913A-DFCD96F18022@xxxxxxxxxxxxx>
<DDF050A2-FDFA-4595-BE2B-7B1EE342606E@xxxxxxxxxxxxx>
<AC85F73D-EB3C-4399-949C-B3FB3F86C492@xxxxxxxxxxxxx>
Subject: Re: Wireless connects but only partially
Date: Thu, 26 Jun 2008 12:18:01 -0700
Lines: 235
Message-ID: <D3B0566B-9A65-4C8B-A5DE-68A939380345@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
Newsgroups: microsoft.public.windows.server.sbs
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:113165
NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
X-Tomcat-NG: microsoft.public.windows.server.sbs

Greetings Terence and Dave,

I am very grateful for your time. In answer to your questions; when the
client is connected thru Ethernet the system works perfect, I can see all
of
the other clients on the network and the internet works fine. The
SBS-Server
DHCP is enabled, and disabled on the router. However, and this may be my
problem that Terence has inquired, I have set the same static address on
the
client IPv4 as the server. I will change it to automatic and see if this
helps. I am almost certain my problems are with my IP assignments,
particularly my Default Gateways. What would be your suggestions?

IPv4 Settings wireless:
IP â?? 192.168.16.5
Subnet â?? 255.255.255.0
Default Gateway - ? (I have used 192.168.16.2 and the router 192.168.1.1)
Preferred DNS â?? 192.168.16.2
Alternate DNS â?? 198.66.164.74 (provided by ISP)
WAP Settings:
IP â?? 192.168.16.5
Sub â?? 255.255.255.0
Default Gateway - ? (I have used 192.168.16.2 and the router 192.168.1.1)
DNS1 â?? 192.168.16.DNS2 â?? 198.66.164.74

--
Thank you,

Richard


"Dave Nickason [SBS MVP]" wrote:

You don't need to run any wizards - this should function the same as
wired.

When you get the successful login, are you sure you're authenticating to
the
SBS rather than with cached credentials? If you enter your password
incorrectly, does that show in the security log on the SBS?

You probably said this earlier, but does that PC function correctly when
connected to the wired LAN? It's domain-joined with /connectcomputer,
has
the correct settings for Internet connection in IE, etc?

DHCP should be enabled on your wireless NIC. The entries look OK, but
it
should be getting its IP info from the DHCP server on the SBS.

"Rick" <Rick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DDF050A2-FDFA-4595-BE2B-7B1EE342606E@xxxxxxxxxxxxxxxx
Hello Dave,
Thank you for your patience but I hate to report in spite of following
all
suggestions still no connections.

Specifics: Linksys Wireless Broadband WRT54G3G-ST â?? Set as Gateway,
Firewall
disabled, DHCP disabled with identical settings to WAP. Again, wireless
connection allows me to logon with user password but cannot identify
the
domain or access internet. Also, just a reminder I have not run Remote
Access Wizard; currently I do not need to set up true VPN and when I
try
all
users on the network lose internet. The firewall on my SOPHOS
antivirus
is
disabled. I still appreciate any thoughts you or others may have.

WAP: Linksys USBN300

Windows IP Configuration wireless

Host Name . . . . . . . . . . . . : Felicia-PC
Primary Dns Suffix . . . . . . . : adxxxxxing.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : adxxxxxing.local

Wireless LAN adapter Wireless Network Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Linksys Wireless-N USB Network
Adapter WUSB300N
Physical Address. . . . . . . . . : 00-1E-E5-2C-60-45
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.16.5(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.2
DNS Servers . . . . . . . . . . . : 192.168.16.2
NetBIOS over Tcpip. . . . . . . . : Enabled
NetBIOS over Tcpip. . . . . . . . : Disabled

--
Thank you,

Richard


"Dave Nickason [SBS MVP]" wrote:

Your IPv4 address should be in the same subnet as the wired
connection,
though, right? For example both might be 192.168.1.x. The first
three
octets should match in both addresses.

Can you browse the server? For example, if you go to Start -> Run
and
type
in \\<servername> does it bring up an Explorer window showing the
shares
on
the server, as it does with a wired PC? I wouldn't worry about ping
too
much - it's possible your WAP is blocking ping.

This is what I would do. First, go into the router configuration and
set
it
as an access point rather than a router. This is probably documented
in
the
instructions for the device. Make sure DHCP is turned off on the
router,
and that the wired router connection is using a fixed IP address from
the
exclusion range on the SBS (or a DHCP reservation). The access point
shouldn't be getting an IP from DHCP. Make sure that MAC address
filtering
is either disabled, or correctly configured to the exact MAC address
of
the
wireless card on the client PC.

Now make sure that the router, and the wireless card on the PC, are
configured exactly the same. Choose WPA personal or WPA2 personal,
but
make
sure it's the same on both. Then, if WPA, choose TKIP encryption on
both.
If WPA2, choose AES encryption on both. Very carefully make sure
that
the
same key is used on both the router and in the configuration on the
client
PC.

At this point, hopefully everything will be working as expected. If
not,
please post back.


"Rick" <Rick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D6C81113-448F-4CFC-97A9-90943A6EEBFD@xxxxxxxxxxxxxxxx
Greetings again Dave,

I followed Mr. Owen Williams configuration details and am still not
connecting. During the initial installation I followed the
instructions
and
setup outlined in Microsoft TechNet document, â??Configure Wireless
Networking
on Windows Small Business Server 2003â?? explicitly.

Here are some unusual items:
When I connect thru the wireless, I can log on under the user name,
however,
I cannot ping the router or the server. Also, I cannot connect to
the
internet, yet my ipconfig is the same as when using Ethernet
(except
for
IPv4
address).

Could this be the problem, when setting up my Linksys WAP and
router I
set
them to WPA Personal. If it is absolutely necessary to run under
Radius
which
of my personal certificates under my console root (SBS-Server,
Wireless
Access, etc) would I use and exactly when I expand them what
specific
information would I copy to my WAP setup?

--
Thank you,

Richard


"Dave Nickason [SBS MVP]" wrote:

Are you connecting to an access point that was in use on your
network
before? Do you have other wireless client PCs that are getting the
expected
experience?

The first thing that comes to mind is, do you have the access point
configured as a router instead of just an AP, and if so, is your
Vista
PC
getting its IP info from the DHCP server running on the router?
Your
client
PC needs to use the DHCP server on the SBS - you can compare an
ipconfig
/all from the new PC to a PC on the wired LAN to see if it's
getting
and
IP
in the same subnet, and pointing to the SBS for DNS and DHCP.

Here's a document by SBS MVP Owen Williams that tells the best way
to
configure the wireless (I guess I should say in my opinion the
best
way).
If you just have the single wireless client and this is more work
than
it's
worth, I recommend manually configuring WPA or WPA2
authentication. I
go
to
www.grc.com and use the random password generator to get a
63-character
key,
but in any case I recommend using a key of 30 characters or more.

Configuring Secure Wireless Network Access with Microsoft®
Windows®
Small
Business Server 2003
http://home.comcast.net/~clearviewtc/


"Rick" <Rick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:08C5DD59-4138-4480-894A-5C045FBB52F1@xxxxxxxxxxxxxxxx

-- I have just installed a wireless network adapter on a new
Vista
PC
setting up the user with the WirelessUser Template.

My Vista network sharing center indicates I have access to local
and
internet, however, I cannot see any of the other users I usually
see
when
I
was hard wired except for myself and I have no access to the
internet.

Iâ??m not certain configuring Remote Access is a prerequisite
since Iâ??m
not
really using a VPN; I have stayed away from configuring this
feature
because
the hard wired users on the network lose the internet when I run
the
wizard.
Any thoughts? I appreciate your time.

Thank you,

Richard





.

Relevant Pages

  • Re: SBS 2003 Client Application Launcher Error
    ... Executing MAPI Profile configuration... ... would you please help me confirm if the problematic client ... This newsgroup only focuses on SBS technical issues. ... | The client does logon with a domain account and that account is ...
    (microsoft.public.windows.server.sbs)
  • Re: Wireless connects but only partially
    ... client IPv4 as the server. ... the correct settings for Internet connection in IE, ... DHCP should be enabled on your wireless NIC. ... go into the router configuration and set ...
    (microsoft.public.windows.server.sbs)
  • Re: Wireless connects but only partially
    ... On the client PC, any auto-enrollment, group policy, or userenv errors in your application log? ... Do you have IAS logging turned on, and if so, what is it logging in the system log on the SBS? ... SBS standard 2003, four hardwired Vista workstations, one wireless. ... Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: RADIUS server setup
    ... I'm still playing around with the wireless configuration, ... > computers using wireless to connect to an SBS server. ... > using the device's version of Internet Explorer and browsing to http:// ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 running but not very well I need REAL help
    ... the SBS server's internal NIC, and that both NICs on the SBS list only the ... you want to make sure that your DNS Server ... Once you have the DNS configuration set, and that means that none of the ... > with one client and two users. ...
    (microsoft.public.windows.server.sbs)
Loading