Workgroup/domain file sharing

[bakershack]

I have an W2K SP4 machine (2NET) connected to two networks - one on a domain (HOWARD) and the other just a workgroup with some industrial controls and a PC (WGPC). I want the workgroup network totally isolated, so I do not have 2NET bridging them. I want to share a folder on WGPC (XP Pro SP2 - firewall disabled) so that I can see it from 2NET. I can browse the domain just fine, and I can ping the IP of WGPC from 2NET, but I cannot browse to the shared folder (permissions Everyone-Full Control), map a drive, or connect in any other way. The IP range for the domain network are 10.x.x.x, and the IP range for the workgroup network is 192.168.x.x. Has anyone done something like this before, and could you help me figure out why I cannot access this shared folder?

Thanks,
Kelly

 

[bcastner]

If you Start, Run, \\192.168.x.x what happens?
(replace x.x with the valid values)

 

[bakershack]

Cannot find the PC. I have some other things to try and will update this afternoon. The PCs are at a different location, and though I can access the 2NET PC through VNC, I cannot access the WGPC. Any other suggestions welcome, especially before I go to the other location.

Kelly

 

[bakershack]

Problem solved. I set the gateway of WGPC to the IP of 2NET, and everything works fine now.

Kelly

 

[bcastner]

I suspect what you really want to do with WGPC is a ROUTE ADD /P
You need a route for both the Workgroup, and the remote LAN.

It is not right to set Gateway IPs outside your local subnet, nor does it do much for the speed of the Workgroup. It would be better to ADD a persistent (/P) ROUTE to the remote site.

See the end of this article:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q128647

 

[LloydSev]

route -p add <network> MASK <netmask> <gateway>

Computer/Network Technician
CCNA

 

[bcastner]

Thank you LloySev,

The persistent route add parameter is -p and not /p as I described above.

My bad.

Best to all,
Bill Castner