Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBS 2003 with remote office. Remote office cant see server!!

Status
Not open for further replies.

aron2k

IS-IT--Management
Dec 20, 2005
10
US
Hey you all...

New to here. Will try to explain.

I have 2 Office's VPN together with Syberguard Hardware VPN's Running a SBS2003 and also a Win2000 Server.

Everything has been great for about a year or about. I have just been moving things around so we can use the Web Outlook and Remote web service too. and in doing so the SBS server is blind or something.

The remote office can see all PC's and the Win2000 server but can't see the SBS? In the main office with the server we can see it just fine and everything works great.

Also main office can see all PC's in remote office too.

Any help would be great.

info:
SBS2003 server.
Domian controller
Exchange
DNS
Remote Web Workplace
OWA
and file server

It has 2 nic cards.
1 for its own IP and router/firewall
1 for local to a switch and the VPN router to the other office.

If you need more info let me know.

Thanks Aaron
 
Can you ping this machine from the remote office?
What about the 2 nic configuration? is this new or has it been configured with 2 nics before as well?

It could be a routing problem, where the sbs server are sending packets to the remote office in the wrong direction (if that is the case, it would be to the
I would do the following:
1) Try to ping the SBS server from the remote service
2) If unsuccessfull try to ping the remote office from the SBS server
3) If that is unsuccessfull as well, look at the machines local routing table. It could be that you need to add an entry for the remote subnet, with the proper gateway, so the sbs server know which gateway to use when communicating with that subnet.

Let me know if this approach helps
 
Do you have Remote Desktop enabled on the SBS server?
 
If you can't ping it from a remote machine, see if you can ping it from the remote firewall/vpn box (most have a built in ping tool). Ping

the IP address
the netbios name ("server")
the FQDN name ("server.mydomain.local")
the domain name ("mydomain.local", etc)

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)
Want to know how email works? Read for yourself -
 
Not useing the SBS server for remote desktop. Useing the Win2000 for the termanel server.

Using the SBS for share point and Exchange and File server.

When I ping the SBS from the remote office it does not come up. But if I ping any other computer comes up.

Will try from the server. I think I can do that but will double check. Been off site today so will check on things this weekend.

Aaron
 
Ok I'm back!

The the 2 NIC's in this machine is new.
I can Ping the remote office from any PC in the local office BUT if I try to ping the remote office from the SBS than the server does not see them. But it does see the local PCs.

Can not ping the server from the remote office.
Can ping it from the local PCs.

"3) If that is unsuccessfull as well, look at the machines local routing table. It could be that you need to add an entry for the remote subnet, with the proper gateway, so the sbs server know which gateway to use when communicating with that subnet."

Will look at the local routing table. Dont know if I know where to find that, But will look. :)


Aaron
 
I will briefly explain what my theory is:

Your server has two NIC´s. I suppose the SBS server is confused about where to put the packets to the remote subnet, and probably it sends them out on the wrong NIC.

Your facts:
- The remote pc´s can not ping the SBS server.
- The SBS server can not ping the remote pc´s.
- SBS server can ping local PC´s
- Local PC´s can ping the SBS server

Have you tried to perform a tracert from the SBS server against one of the remote PC´s? That would give you an indication of which interface it is sending the ICMP packets through.

I am making a couple of assumptions here:
Lets call the internet nic, NIC1
Lets call the local nic, NIC 2
Lets give the local subnet the network id of 192.168.20.0 /24
Lets give the remote subnet the network id of 192.168.30.0 /24

If my assumption is right, and the tracert tells you that the ICMP packets is sent through NIC1, then do the following:

1) Start -> Run -> CMD
2) Type route print, to print out the SBS server routing table
3) Next, add a routing entry to the servers routing table, with the following command:

route -p add 192.168.30.0 mask 255.255.255.0 192.168.20.10 metric 1 if 0x10005

Short explanation:
-p (makes the route persistent. In other words it will still be there after the next reboot)
192.168.30.0 (the remote network id. Change with the proper one)
mask (the remote subnet mask. change with the proper one)
192.168.20.10 (this is the adress of the gateway on the local subnet. Change it with the proper gateway that leads to the remote subnet)
metric 1 (the metric priority value. Use it as it is)
if 0x10005 (This is the id of the network interface you are binding the route entry to. Change it to the proper value. If you type route print, you will get the id of all the nics installed in the SBS Server).
4) Check that the route is added, by typing route print once more (it should be listed under the persistent section)
5) Try to ping the remote machines from the SBS server once more.

Now it should work. Let me know the results of this please :)




 
No disrespect meant but "termanel" is spelled "terminal".
 
HEY HEY PEEPS!!

Well its like you do this for a living! Works like a champ!

Thanks Peeps for all the help here.

You all ROCK!

A-RON
 
Hey got an issue...

When the server reboots the interface changes to the wrong NIC card??

any ideals?

I have been having to go back in and redo the route add?

A-RON
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top