I've got 2 D-Link 804v configured and tunneled to one another just fine. The problem is browsing or connecting through "new use" over the tunnel from Office A to Office B.
Office A has 10- workstations, all Windows 2000 Professional.
Office B has the Windows 2000 Server, as a PDC with AD, that all workstations from Office A needs to connect to for file storage and etc.,
I cannot use any UNC names for workstations at Office B or for the server.
I can connect using \\LAN.IP.Addy.Of.Workstation.
I cannot connect to the Win2k Server with the LAN I.P., only the WAN.
That is also the only way I can connect to the routers web configuration page for both routers. (using the WAN IP)
What can I do to be able to use the UNC naming?
Can I import the LMHosts file?
Would configuring the Win2k Server as a WINS also work over the IPSec tunnel.
Is it normal after linking the two routers together, to not be able to use the LAN IP for the router?
If not, what is up with that?
Any ideas on what to check?
TIA
Walk softly and carry a big stick; you'll go far. - Theodore Roosevelt
Office A has 10- workstations, all Windows 2000 Professional.
Office B has the Windows 2000 Server, as a PDC with AD, that all workstations from Office A needs to connect to for file storage and etc.,
I cannot use any UNC names for workstations at Office B or for the server.
I can connect using \\LAN.IP.Addy.Of.Workstation.
I cannot connect to the Win2k Server with the LAN I.P., only the WAN.
That is also the only way I can connect to the routers web configuration page for both routers. (using the WAN IP)
What can I do to be able to use the UNC naming?
Can I import the LMHosts file?
Would configuring the Win2k Server as a WINS also work over the IPSec tunnel.
Is it normal after linking the two routers together, to not be able to use the LAN IP for the router?
If not, what is up with that?
Any ideas on what to check?
TIA
Walk softly and carry a big stick; you'll go far. - Theodore Roosevelt
