LAN routing / file sharing issue

W

Wowbagger

The office LAN is configured as

192.168.1.0 255.255.255.0

Within the LAN there is a wireless router with an IP of 192.168.1.64

Machines connecting to the wireless router are configured as

192.168.42.0 255.255.255.0

There is a particular machine on the wireless segment:

192.168.42.101 with a shared directory.

I created a route using the command

route add 192.168.42.0 mask 255.255.255.0 192.168.1.64

and even a direct route

route add 192.168.42.101 mask 255.255.255.0 192.168.1.64

but I just cannot hit that box from my side of the wireless router.

Is there something wrong with my route configuration? What do I need to do
to tell my computer how to reach that machine?
 
D

Donald

Sorry the previous post was wrong. Are you connecting all your computers
directly to the wireless router without ICS and simple file sharing? Did you
check the SSID of the wireless router are all the same on all the computers?
Did you enable NetBIOS or NetBIOS over TCPIP on your network connection
properties? Is there any IP address confliction? Did you try to use DHCP on
the router? Can you ping that destination computer with or without the
route?
 
J

John Wunderlich

The office LAN is configured as

192.168.1.0 255.255.255.0

Within the LAN there is a wireless router with an IP of
192.168.1.64

Machines connecting to the wireless router are configured as

192.168.42.0 255.255.255.0

There is a particular machine on the wireless segment:

192.168.42.101 with a shared directory.

I created a route using the command

route add 192.168.42.0 mask 255.255.255.0 192.168.1.64

and even a direct route

route add 192.168.42.101 mask 255.255.255.0 192.168.1.64

but I just cannot hit that box from my side of the wireless
router.

Is there something wrong with my route configuration? What do I
need to do to tell my computer how to reach that machine?


If your "Wireless Router" is a NAT router (ie a standard home
router), this won't work. Yeah you're shoving the packets at the
router, but the router's Network Address Translation tables won't
know what to do with it. Even if it does make it through, you
haven't set up any routing tables on the wireless router to get the
reply packet back to where you want it.

What you really want here is a wireless "Access Point" instead of a
router so that all machines, wired or not, are on the same subnet
and can freely communicate. You can reconfigure a NAT router to act
as an Access Point. It involves not connecting the WAN port and
connecting to the LAN port instead. You also have to change the IP
address of the Wireless Router to be on the same subnet as the other
router but not conflicting with the other router's IP address on
the subnet, and you have to disable DHCP on the wireless router.

Some articles to help you:
"Using a Wireless Router as an Access Point"
<http://www.dslreports.com/faq/11233>

"Quick Guide to Configure Wireless Router as Access Point"
<http://www.home-network-help.com/wireless-router-as-access-point.html"

"Wireless Router as an Access Point"
http://www.webpronews.com/expertarticles/2006/08/29/wireless-router-as-an-access-point

HTH,
John
 
W

Wowbagger

I cannot ping the destination computer through the router but if I can ping
it without difficulty from a machine on the same segment.

NetBIOS over TCPIP is enabled, and DHCP serves up the back segment.
 
W

Wowbagger

John Wunderlich said:
If your "Wireless Router" is a NAT router (ie a standard home
router), this won't work.

No way to use the server functions somehow?
What you really want here is a wireless "Access Point" instead of a
router so that all machines, wired or not, are on the same subnet
and can freely communicate.

I only need to get to the machine long enough to copy a user profile from
the old machine to the new one - the wireless router functions need to stay
to serve up IPs for the laptops (the office scope is just about full so I
need the extra range of addresses).
 
B

Brian A.

John Wunderlich said:
No way to use the server functions somehow?


I only need to get to the machine long enough to copy a user profile from
the old machine to the new one - the wireless router functions need to
stay to serve up IPs for the laptops (the office scope is just about full
so I need the extra range of addresses).

I have two routers in my LAN network with the first one connected to the
WAN port on the second one. I can access both router configurations and
have full router/server functions of both. Below is how I have both routers
configured with the only difference being I used your supplied LAN
information. Of course there may/most likely will be a difference in the
configuration pages of yor routers compared to mine.

If the office LAN router is connected to the WAN port of the Wireless
router:
On the office LAN router configure a Static Route to the LAN side of the
Wireless router.
Destination: 192.168.42.100
Subnet mask: 255.255.255.0
Gateway: WAN IP of Wireless router. (I presume 192.168.1.64)
Hop count: 2
Interface: LAN

On the Wireless router configure:
WAN IP: Fixed
IP address: 192.168.1.64
Subnet mask: 255.255.255.0
Gateway: 192.168.1.0

LAN setup:
DHCP: Enabled
Pool starting address: 192.168.42.101
Count: Whatever you want
Primary DNS Server: DNS addresse used by office LAN router supplied by ISP.
Secondary DNS Server: DNS addresse used by office LAN router supplied by
ISP.

LAN TCP/IP:
LAN IP address: 192.168.42.100
IP subnet nask: 255.25.255.0

Port Forward:
Start: 80
End: 80
Server IP: 192.168.42.100

Static Route:
Destination: 0.0.0.0
Subnet mask: 0.0.0.0
Gateway: 192.168.1.0
Hop count: 2


--
Brian A. Sesko
Conflicts start where information lacks.
http://basconotw.mvps.org/

Suggested posting do's/don'ts: http://www.dts-l.org/goodpost.htm
How to ask a question: http://support.microsoft.com/kb/555375
 
D

Donald

Why do you have to go through that wireless router if you can ping the
destination computer through your office LAN? If you need to copy something
over, can you go through the subnet 192.168.42.0? How is your office LAN
connected?
 
D

Donald

Otherwise you will have to change the LAN IP address of the wireless router
to be within 192.168.42.0. Otherwise it doesn't talk with the computers.
 
W

Wowbagger

This is how the LAN is configured:

Target machine (192.168.42.101)

|
|
\./

(192.168.42.1)
Wireless router
(192.168.1.64)

|
|
\./

My machine (192.168.1.71)
Machine to be migrated (192.168.1.90)
server (192.168.1.238)
printer (192.168.1.231)
etc, etc, etc

|
|
\./

{{{ gateway out to the internet }}}


I can ping everything on both segments from the target machine, can connect
to the server, to the printers, the internet - everything works well. What
I can't do is connect to a shared folder on the target machine so I can use
the USMT to copy a profile over to the new machine.
 
W

Wowbagger

I've found a workaround - I've configured a virtual server to forward port
21 to the target, then used the free utility FTPdrive to map a drive letter
on the source computer that points to the filezilla ftp server I just
installed. Problem solved, no muss, no fuss.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top