larksys
asked on
how can I combine to workgroups
I have a network at 192.168.3 and one at 192.168.1 and need to communicate/share. I can ping from the .1 to the .3 but cannot map a drive (invalid path). Both workgroups are named WORKGROUP.
the .3 network is remote and connects to a VPN server. They use .1 resources (AS400 server, ect.) . The .1 network is local via a hub. Specifically, I need to run an Access job on the .1 network that is located on the .3 network.
the .3 network is remote and connects to a VPN server. They use .1 resources (AS400 server, ect.) . The .1 network is local via a hub. Specifically, I need to run an Access job on the .1 network that is located on the .3 network.
ASKER
User Sandy on the .1 network needs to run an Access job on the .3 network on Linda's machine. How does your suggestion solve that problem?
larksys,
The reason why your two networks are not talking to each other is because of the different segments (one is on x.x.1.x and the other is x.x.3.x) By default, IP networks can only talk to each other when they are on the same segment (and have same subnet mask).
You might have to set up a routing table in your router to talk to both networks. If you have ever setup an internet router to use with broadband internet then you should be familiar with the concept of the routing.
Now, since you are connecting to a remote VPN server we would need to know what service is being used to provide the VPN connection (Routing and Remote Access on a Windows Server?) to proceed. It might be possible to setup a route table on the server to allow proper communication between the two networks.
Let us know!
The reason why your two networks are not talking to each other is because of the different segments (one is on x.x.1.x and the other is x.x.3.x) By default, IP networks can only talk to each other when they are on the same segment (and have same subnet mask).
You might have to set up a routing table in your router to talk to both networks. If you have ever setup an internet router to use with broadband internet then you should be familiar with the concept of the routing.
Now, since you are connecting to a remote VPN server we would need to know what service is being used to provide the VPN connection (Routing and Remote Access on a Windows Server?) to proceed. It might be possible to setup a route table on the server to allow proper communication between the two networks.
Let us know!
ASKER
There are 7 PC on the .3 network connected to a hub that connects to a SOHO box that manages a VPN to the Firebox/VPN that's on the .1 network. I have a policy that nats .3 to .1 but I'm not sure what services may be excluded or included for that matter.
ASKER
The Firebox shows 192.168.3.1/24 and 192.168.1.1/24 as secondary networks on the trusted interface.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am assuming that \Share is a reserved XP term. The path could not be found. I also tried \drivers that is a shared folder on the target PC.
ASKER
I can map a drive from the .3 network to the .1 network. The reverse is not true.
ASKER
I guess the honeymoon is over.
Create one user account in both the workgroups and request the users it login using that credentials. If not while mapping use this user id and pwd. Hope this helps
Cheers!