Re: Wireless connects but only partially

Just enable DHCP on the wireless NIC and let it get an IP address, etc. from the SBS.

So the wireless access point is going to use a fixed IP address in the same range as the SBS - 192.168.1.x, and that's going to be an IP that's excluded from your DHCP scope so DHCP doesn't hand it out to a different device. You should be able to ping the WAP from the SBS. Then, the client PC is going to get its IP and related info from the DHCP server on the SBS. When you run ipconfig /all on the client PC, the wireless card's results should exactly match those of the wired card (when it's connected), except for the last octet of the IP. Now, the connection is passing from the client PC through the WAP to the SBS, exactly as the wired connection passes through the Ethernet switch to the SBS. The WAP isn't doing anything except handling the connection between itself and the client PC (including the WPA security and encryption).


"Rick" <Rick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D3B0566B-9A65-4C8B-A5DE-68A939380345@xxxxxxxxxxxxxxxx
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: Networking Question - VLANs on SBS 2003 Premium SP1
    ... DHCP running on the router. ... Set the DHCP on the router, to make a exclusion of IP range. ... you can set the SBS use fix IP by run the CEICW. ... all gust wireless clients will get IP address from DHCP on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Networking Question - VLANs on SBS 2003 Premium SP1
    ... DHCP running on the router. ... Set the DHCP on the router, to make a exclusion of IP range. ... you can set the SBS use fix IP by run the CEICW. ... all gust wireless clients will get IP address from DHCP on the ...
    (microsoft.public.windows.server.sbs)
  • Re: Coffee shop wifi will not give me IP address, but gives everyone else IP address. But static IP
    ... with a Dell Wireless 1490 Dual B and WLAN Mini-Card ... I set up my connection ... But the router NEVER ... they're using the default OS wifi settings, DHCP, etc. ...
    (alt.internet.wireless)
  • 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: Share Connection with Wii
    ... The second Network card that connect the Laptop to the Boxes can not be on the same Network. ... IP Subnet Mask 255.255.255.0(Via DHCP) ... Router: Wireless Port ... Ethernet adapter Wireless Network Connection: ...
    (microsoft.public.windowsxp.network_web)