Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 945
  • Last Modified:

Outlook 2003 will not connect over VPN

I have a user who cannot get Outlook to connect to the exchange server.  He is on a hotel internet connection, and connected through Cisco VPN Client.  

All his ip configuration is below.  He can ping our mail server (inxs00090) and our proxy servers.  

I think it is  DNS problem, but when he is connected to VPN, he tried changing his DNS to our internal DNS server but no change.  

He can access Outlook Web Acccess so the exchange and his mailbox is fine.  My exchange guy has checked the logs on the server and there is nothing wrong.  his client has always worked fine on VPN and in the office and there have been no changes to his PC.  

He is high profile so I urgently need to help him get this working.  He is overseas so i cannot access the PC but can get him to do some troubleshooting.  

The below was from a batch file I sent him and got him to run:

Windows IP Configuration
 
        Host Name . . . . . . . . . . . . : pctl020818
        Primary Dns Suffix  . . . . . . . : eams.icompany.com
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : icompany.com
                                            eams.icompany.com
 
Ethernet adapter Wireless Network Connection:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
        Physical Address. . . . . . . . . : 00-1F-3B-19-5A-D9
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.11.114
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        IP Address. . . . . . . . . . . . : fe80::21f:3bff:fe19:5ad9%4
        Default Gateway . . . . . . . . . :
        DHCP Server . . . . . . . . . . . : 192.168.11.254
        DNS Servers . . . . . . . . . . . : 212.30.96.123
                                            fec0:0:0:ffff::1%1
                                            fec0:0:0:ffff::2%1
                                            fec0:0:0:ffff::3%1
        Lease Obtained. . . . . . . . . . : 18 February 2009 17:40:28
        Lease Expires . . . . . . . . . . : 19 February 2009 05:40:28
 
Ethernet adapter Local Area Connection:
 
        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Marvell Yukon 88E8055 PCI-E Gigabit Ethernet Controller
        Physical Address. . . . . . . . . : 00-1A-80-D2-C6-17
 
Ethernet adapter Bluetooth Network:
 
        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Bluetooth LAN Access Server Driver
        Physical Address. . . . . . . . . : 00-1E-3D-8B-6D-93
 
Ethernet adapter Local Area Connection 3:
 
        Connection-specific DNS Suffix  . : icompany.com
        Description . . . . . . . . . . . : Cisco Systems VPN Adapter
        Physical Address. . . . . . . . . : 00-05-9A-3C-78-00
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 10.220.16.11
        Subnet Mask . . . . . . . . . . . : 255.0.0.0
        IP Address. . . . . . . . . . . . : fe80::205:9aff:fe3c:7800%8
        Default Gateway . . . . . . . . . : 10.220.16.11
        DNS Servers . . . . . . . . . . . : 147.1.64.59
                                            147.1.179.215
                                            fec0:0:0:ffff::1%1
                                            fec0:0:0:ffff::2%1
                                            fec0:0:0:ffff::3%1
        Primary WINS Server . . . . . . . : 147.1.64.59
        Secondary WINS Server . . . . . . : 147.1.179.215
 
Tunnel adapter Teredo Tunneling Pseudo-Interface:
 
        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
        Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%6
        Default Gateway . . . . . . . . . :
        NetBIOS over Tcpip. . . . . . . . : Disabled
 
Pinging inxs00090.eams.icompany.com [10.220.149.101] with 32 bytes of data:
 
Reply from 10.220.149.101: bytes=32 time=49ms TTL=126
Reply from 10.220.149.101: bytes=32 time=146ms TTL=126
 
Ping statistics for 10.220.149.101:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 49ms, Maximum = 146ms, Average = 97ms
 
Pinging inxs-proxy.eams.icompany.com [10.220.80.12] with 32 bytes of data:
 
Reply from 10.220.80.12: bytes=32 time=56ms TTL=126
Reply from 10.220.80.12: bytes=32 time=57ms TTL=126
 
Ping statistics for 10.220.80.12:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 56ms, Maximum = 57ms, Average = 56ms
 
Pinging lonsproxy.eams.icompany.com [147.1.64.169] with 32 bytes of data:
 
Reply from 147.1.64.169: bytes=32 time=53ms TTL=122
Reply from 147.1.64.169: bytes=32 time=81ms TTL=122
 
Ping statistics for 147.1.64.169:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),




0
itinfserv
Asked:
itinfserv
  • 4
  • 2
1 Solution
 
Hypercat (Deb)Commented:
If NetBIOS over TCP/IP is disabled on the VPN connection, this is most likely the problem.  I'm not familiar with Cisco VPN setup, but it looks to me like it is.  Try enabling NetBIOS over TCP/IP over the VPN connection and see if that resolves your issue.
0
 
itinfservAuthor Commented:
Do you mean client-side or on the concentrator?  Where is the setting on the client?  He connected fine from the last hotel he stayed in and other users are connected to the same concentrator.  
0
 
Hypercat (Deb)Commented:
I would have thought it would be disabled at your end, not on the client side.  He's using a Cisco VPN client, so as I said I'm not familiar with the settings for that on the client side. But I assumed that the "Teredo Tunneling Pseudo Interface" was an element of the Cisco VPN client, but I checked it and it is related to IPv6.  Assuming you're not using IPv6, then it's not relevant.
One thing I don't see is whether NetBIOS over TCP/IP is enabled for the wireless NIC and/or the Cisco VPN client.  I would have him check the properties of both of these connections to see if NetBIOS over TCP/IP is enabled.  This setting should be in the properties of the network connection itself, where it normally is on the WINS tab of the Advanced properties of the IP properties.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
kavlinsCommented:
I would RDP to that PC either with logmein or teamviewer after installing it on my and his machine. Let him install this small free version utility on his PC.Once done create a session no. and connect to it. This utility has the File Transfer feature too. So if you do need see anything unusual in the settings, try a reinstall of VPN Client and see what happens.
0
 
itinfservAuthor Commented:
Thanks.  I think you are on the right track with NetBIOS over TCP/IP.  It seems to come up a lot when searching the topic.  Nothing shows it's relation to Cisco Client though.  I will have to test it tomorrow in the office with windows network connections.  Will update.

Thanks for the help.  
0
 
itinfservAuthor Commented:
Unfortunately we never resolved this.  The user has returned and now it works whereever he is.  We see this with certain service providers (esp Tiscali).  

I will close the question.  Thanks all for your help and comments.  
0
 
itinfservAuthor Commented:
Unfortunately we never resolved this.  The user has returned and now it works whereever he is.  We see this with certain service providers (esp Tiscali).  

I will close the question.  Thanks all for your help and comments.  
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now