Topic: Connecting from subnet to SME Server

[Ron]

Hello everyone.

I am in the process of connecting branches via VPN through the third party for a client.  All is working quite well. The configuration for my setup is as follows:

Main office: 192.168.1.xxx
Remote office: 192.168.2.xxx

The SME server and other servers are in the main office and the VPN is setup through the router so SME doesn't have anything to do with it. My problem is that from the remote office, I can click on all the servers with the shares and I can see them, but when I click on SME server from network neighbourhood, it tells me that the connection is missing.  How come?

I have even added the following segment in the LOCAL NETWORK as:

Network address: 192.168.2.0
Subnet: 255.255.255.0
Router: 192.168.1.4  (i-e sdsl router addy. Ofcourse, it doesn't recognize the router on remote office i-e 192.168.2.4)

I am going crazy and almost at the point of giving up and going back to NT and use it as a file server. I have to get this working for a client and as deadline is approaching, I am almost giving up.  Hope you can rescue me before I jump from the tallest building in my town.

[Michael Smith]

Sounds frustrating... can you connect via UNC or IP, i.e. \smebox\files or \192.168.1.1\files?  What OS are the client machines running?  

IMHO being able to browse via Network Neighborhood is a bonus, or "lagniappe" as we'd call it here in southern Louisiana ... not truly necessary.  If you can connect directly you can always map drives per machine or with a login script.

[Ron]

I am using Windows 98 on the client side and I have two other NT and Windows 2000 servers running in the main branch.  I can see all the shares etc. of NT and Windows 2000, but it's only SME server that doesn't like to share from the branch. Ironically, it is fine when I connect or see the shares from the same local network i-e 192.168.0.xxx network.

I have tried to see the shares that I can see from the main network. All branches are connecting through the router via VPN connection which is done through the router and not SME server.   If I could see the shares from network neighbourhood, then it is easy to do the UNC/drive mapping via script or the individual computer etc. I can just see the SME server name, but nothing inside.

Is there any physical setting need to be changed on the SME server that would allow the shares to open up?  I suspect that there is perhaps a bug or an issue to be resolved on SME server.