Wired/Wireless Conflict

#1 (**permalink**) 08-04-2008, 08:06 PM

We use Windows 2003 Server on our wired LAN and we DO NOT use the
Internet for LAN computers or the Server. We do have a wireless DSL
router that we know works when we use a laptop (not on LAN)...

However, we now have the need to use a XP Pro PC on the Internet AND
the LAN. We installed a wireless adapter in the PC and we can connect
to DSL router and browse the Internet, BUT we have to disable the
wired LAN connection to get it to work.

Here is a summary of our setup:

Workstations on WIRED LAN:
IP: Statically assigned 192.168.1.x
GW: empty
DNS: 192.168.1.5 (WINDOWS 2003 Server IP address)

Wireless Router IP: 192.168.1.1
DHCP enabled --for laptops

PC Wireless Connection:

Obtain automatically IP & DNS, gets:

IP 192.168.1.42
DNS 192.168.1.1
DHCP 192.168.1.1

How can we get both the wired & wirelss connections working on this
PC. We want to isolate the Server and other PCs from the Internet as
much as possible.

Seems to be a gateway issue...

Thanks!

#2 (**permalink**) 08-05-2008, 02:53 AM

On Mon, 4 Aug 2008 12:06:41 -0700 (PDT), compsosinc@gmail.com wrote:

>We use Windows 2003 Server on our wired LAN and we DO NOT use the
>Internet for LAN computers or the Server. We do have a wireless DSL
>router that we know works when we use a laptop (not on LAN)...
>
>However, we now have the need to use a XP Pro PC on the Internet AND
>the LAN. We installed a wireless adapter in the PC and we can connect
>to DSL router and browse the Internet, BUT we have to disable the
>wired LAN connection to get it to work.
>
>Here is a summary of our setup:
>
>Workstations on WIRED LAN:
>IP: Statically assigned 192.168.1.x
>GW: empty
>DNS: 192.168.1.5 (WINDOWS 2003 Server IP address)
>
>Wireless Router IP: 192.168.1.1
>DHCP enabled --for laptops
>
>PC Wireless Connection:
>
>Obtain automatically IP & DNS, gets:
>
>IP 192.168.1.42
>DNS 192.168.1.1
>DHCP 192.168.1.1
>
>How can we get both the wired & wirelss connections working on this
>PC. We want to isolate the Server and other PCs from the Internet as
>much as possible.
>
>Seems to be a gateway issue...

Any particular model router?

Nope. It's an IP layout issue. Two possible solutions.

1. Change your subnet for the wireless router to something other than
192.168.1.xxx. You can't have the same subnet on both sides of the
router (LAN and WAN). Leave the WAN IP at 192.168.1.42, but the LAN
side should be something like 192.168.111.1 with the DHCP delivering
IP's in the 192.168.111.xxx range.

2. Dump the un-necessary router and have the DHCP server in the
Windoze 2003 server deliver the IP's. See:
<http://wireless.navas.us/wiki/Wi-Fi_How_To#Use_a_wireless_router_as_a_wireless_acce ss_point>
Be sure to disable the DHCP server in your unspecified model router.

I think you'll find the PC will magically fix itself when both
interfaces (wired and wireless) do not share the same IP subnet. If
not, you'll need a static route for 192.168.1.xxx for the wired
interface, and a default route via wireless to get to the internet.
Details on request, but I think you'll find that things will work
after you cleanup your network per suggestions 1 or 2.

--
# Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
# 831-336-2558 jeffl@comix.santa-cruz.ca.us
# http://802.11junk.com jeffl@cruzio.com
# http://www.LearnByDestroying.com AE6KS

#3 (**permalink**) 08-05-2008, 01:49 PM

On Aug 4, 9:53*pm, Jeff Liebermann <je...@cruzio.com> wrote:
> On Mon, 4 Aug 2008 12:06:41 -0700 (PDT), compsos...@gmail.com wrote:
> >We use Windows 2003 Server on our wired LAN and we DO NOT use the
> >Internet for LAN computers or the Server. We do have a wireless DSL
> >router that we know works when we use a laptop (not on LAN)...
>
> >However, we now have the need to use a XP Pro PC on the Internet AND
> >the LAN. We installed a wireless adapter in the PC and we can connect
> >to DSL router and browse the Internet, BUT we have to disable the
> >wired LAN connection to get it to work.
>
> >Here is a summary of our setup:
>
> >Workstations on WIRED LAN:
> >IP: Statically assigned 192.168.1.x
> >GW: empty
> >DNS: 192.168.1.5 (WINDOWS 2003 Server IP address)
>
> >Wireless Router IP: 192.168.1.1
> >DHCP enabled --for laptops
>
> >PC Wireless Connection:
>
> >Obtain automatically IP & DNS, gets:
>
> >IP 192.168.1.42
> >DNS 192.168.1.1
> >DHCP 192.168.1.1
>
> >How can we get both the wired & wirelss connections working on this
> >PC. We want to isolate the Server and other PCs from the Internet as
> >much as possible.
>
> >Seems to be a gateway issue...
>
> Any particular model router?
>
> Nope. *It's an IP layout issue. *Two possible solutions.
>
> 1. *Change your subnet for the wireless router to something other than
> 192.168.1.xxx. *You can't have the same subnet on both sides of the
> router (LAN and WAN). *Leave the WAN IP at 192.168.1.42, but the LAN
> side should be something like 192.168.111.1 with the DHCP delivering
> IP's in the 192.168.111.xxx range.
>
> 2. *Dump the un-necessary router and have the DHCP server in the
> Windoze 2003 server deliver the IP's. *See:
> <http://wireless.navas.us/wiki/Wi-Fi_How_To#Use_a_wireless_router_as_a...>
> Be sure to disable the DHCP server in your unspecified model router.
>
> I think you'll find the PC will magically fix itself when both
> interfaces (wired and wireless) do not share the same IP subnet. *If
> not, you'll need a static route for 192.168.1.xxx for the wired
> interface, and a default route via wireless to get to the internet.
> Details on request, but I think you'll find that things will work
> after you cleanup your network per suggestions 1 or 2.
>
> --
> # Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
> # 831-336-2558 * * * * * *je...@comix.santa-cruz.ca.us
> #http://802.11junk.com* * * * * * * je...@cruzio.com
> #http://www.LearnByDestroying.com* * * * * * * AE6KS- Hide quoted text -
>
> - Show quoted text -

Thanks for the reply. Looks like we will go with solution #1 and
change the wireless router to 192.168.2.1. Our LAN is setup with
staticIPs -we do not want to run DHCP on the Server-so we do not want
to change the LAN IPs. And the wireless router is running DHCP so it
is convenient for users with laptops to get on the Internet. We do not
have the wireless router plugged into the LAN switch and we do not
want our server or other LAN PCs to have Internet access -just the one
we put the adapter in.