Re: Wired/Wireless Conflict
- From: "Spaceman" <spaceman@xxxxxxxxxxxxxxxx>
- Date: Mon, 4 Aug 2008 15:25:17 -0400
I may be wrong but I think the easiest thing you could do is
to change the Wireless router IP to 192.168.2.1
and leave everything else the same.
This will allow the wireless to give out a different set of
IP addresses that will not conflict with the wired networks
addresses.
If I am wrong.
Here is my sig anyway to prove even certified people
can be wrong
:)
--
James M Driscoll Jr
MCTS (Vista)
Spaceman
<compsosinc@xxxxxxxxx> wrote in message news:0c84059a-e6c2-4d71-9208-d6d3cb170851@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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!
.
- Follow-Ups:
- Re: Wired/Wireless Conflict
- From: Phillip Windell
- Re: Wired/Wireless Conflict
- From: Phillip Windell
- Re: Wired/Wireless Conflict
- References:
- Wired/Wireless Conflict
- From: compsosinc
- Wired/Wireless Conflict
- Prev by Date: Re: Wireless EAP Problem
- Next by Date: Re: Wireless EAP Problem
- Previous by thread: Wired/Wireless Conflict
- Next by thread: Re: Wired/Wireless Conflict
- Index(es):
Relevant Pages
|