|
| I am having a problem accessing some servers on my office network after
connecting through a VPN.
I am using the Secure VPN Client - Mobile User VPN from WatchGuard
Technologies. I don't know what VPN hardware is on my office side.
Connecting to the VPN works fine. After connecting I can ping server1, but
not server2. Both are defined in my hosts table. Ping works the same way
with the server name or IP address.
I do the following commands before accessing the servers. They both complete
successfully.
net use * \\server1\dir1 /user:domain1\user1
net use * \\server2\dir2 /user:domain1\user1
I am logged in as user1 on the domain domain1.
After these commands I can access server1, but not server2, meaning that if
look bring up an explorer window pointing to \\server2\dir1, I see the files
stored as "offline". Server1 files are actually showing the files on the
server.
I don't know if makes a difference, but I have Offline Files enabled and
files in dir1 and dir2 marked for being "available offline". I don't see how
I ping one server, but not another. Server2 is a new machine on the network.
I am running Win XP on the client. I think that we have Win Server 2003 on
the domain controller.
Here is some more information that may be helpful. My support folks aren't
able to fingure out what is going wrong. Thanks for any help.
host file entries are:
172.16.16.24 server2
172.16.16.22 server1
A ipconfig shows:
Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . : Belkin
IP Address. . . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
A route print shows:
========================================
===================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 0f 1f 13 b1 53 ...... Broadcom 440x 10/100 Integrated Controller -
Pac
ket Scheduler Miniport
0x10004 ...00 0e 35 11 82 ed ...... Intel(R) PRO/Wireless 2200BG Network
Connect
ion - Packet Scheduler Miniport
========================================
===================================
========================================
===================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.3 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.2.0 255.255.255.0 192.168.2.3 192.168.2.3 25
192.168.2.3 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.2.255 255.255.255.255 192.168.2.3 192.168.2.3 25
224.0.0.0 240.0.0.0 192.168.2.3 192.168.2.3 25
255.255.255.255 255.255.255.255 192.168.2.3 2 1
255.255.255.255 255.255.255.255 192.168.2.3 192.168.2.3 1
Default Gateway: 192.168.2.1
========================================
===================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.50.0 255.255.255.0 172.16.15.15 1
An arp -a shows:
Interface: 192.168.2.3 --- 0x10004
Internet Address Physical Address Type
192.168.2.1 00-11-50-33-32-fa dynamic
192.168.2.4 00-0f-3d-f7-66-29 dynamic
|
|