Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 439
  • Last Modified:

cisco 4.7 at&t can not connect mtu set to 1400 bites in 0.

I am trying to connect from home to work using vpn 4.7 cisco. however when i connect the bytes in say 0. and when i try to connect to my server through remote desktop it just disconnects me. I ahve set the mtu at 1400 like some forums stated and nothing. I have worked with my IT team they do not know what the problem is. I have called at&T they say is a vpn issue and they do not know about vpns so i am at a loss. Please help i have gone evry route i can think off.
  • 7
  • 5
  • 2
1 Solution
Kamran ArshadIT AssociateCommented:

Have you checked the available bandwidth to you? You can do so using IPerf.

Iperf                 Open-Source
Kamran ArshadIT AssociateCommented:
Also any specific entries in the VPN client log?
alx02Author Commented:
Here is what the log says;
Cisco Systems VPN Client Version
Copyright (C) 1998-2005 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Windows, WinNT
Running on: 5.1.2600 Service Pack 2
Config file directory: C:\Program Files\Cisco Systems\VPN Client\

1      10:14:30.665  05/21/09  Sev=Warning/2      IKE/0xA3000067
Received an IPC message during invalid state (IKE_MAIN:507)

i can not get iperf to run it runs and i see the windown come up real quick but can not access it.
Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

alx02Author Commented:
Here is another thing we just tested. We took my laptop to someone elses house that does not have att and we were still unable to get any bytes in/ connect to servers.
If you have the same problem through another ISP then it has nothing to do with AT&T.

Based on the error message, you are not even successfully connecting to the VPN server.  Your IT department should see messages of some sort on the VPN server.

The message "Received an IPC message during invalid state (IKE_MAIN:507)" indicates the the VPN client received a message from the VPN server, but the client was not "ready" to get that message.

I would go back to your IT department and have them look at their logs some more.
alx02Author Commented:
thank you for your response i am having them take a look at their logs on their ide this week and will post what they say.
alx02Author Commented:
Sat down with IT and connected while they had their logs up here is what they are seeing;
User xxxxxx was granted access.
 Fully-Qualified-User-Name = xxxxxxxxxxxxxx/Users/xxxxxx
 NAS-IP-Address =
 NAS-Identifier = <not present>
 Client-Friendly-Name = Cisco 2811 Router VPN
 Client-IP-Address =
 Calling-Station-Identifier =
 NAS-Port-Type = Virtual
 NAS-Port = 2
 Proxy-Policy-Name = Use Windows authentication for all users
 Authentication-Provider = Windows
 Authentication-Server = <undetermined>
 Policy-Name = VPN Login
 Authentication-Type = PAP
 EAP-Type = <undetermined>

But i still get no bytes in.
Until you get connected to the VPN succesfully you will get no bytes in.

Are you still getting the RPC error?

After you "think" you are connected, issue the commands:

     ipconfig /all
     netstat -rn

and confirm with your IT department that they are correct for your setup.
alx02Author Commented:
We sat down and looked at the logs from the ipconfig and netstat -rn with IT. All looks fine from their side they say. they are questioning as to why one of my gateways are showing as but other than that they have no further information.
If the routing table looks good to them, what happens if you issue the command:

tracert -d x.x.x.x

where x.x.x.x is one of the IP addresses for a host that you should be using the VPN for.

Can you post your routing tables?  Under Windows there should normally be at least two route entries that use as the gateway address.  The first is for the whole loopback address space and that should look like:       1

The other entry should be for your specific IP addresss something like:

        y.y.y.y       1

Where y.y.y.y is your computer's IP address.  Once connected to the VPN you should end up with two entries as your computer should have two IP addresses; one for the NIC and one the virtual NIC representing the VPN connection.
alx02Author Commented:
here is the table;
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
       1       20       20       1       1       20       20       20       20       1       1       20       20       1               3       1       1
Default Gateway:
when i do the tracert command i get host unreachable
What was the IP address you were attempting to do a tracert to?
Also can you post the output from ipconfig command?

It appears that part of the problem may be your home IP subnet is part of both your works IP subnets (the VPN tunnel and the internal network).

Right now I would say that your home computers IP address is with a subnet mask of

It appears your works VPN subnet is, but I'm not sure of the subnet, as there is no route to that network.  I do see:
       20       1

Which is really confusing because this says to get to any host in the subnet you must go through, which I think is your IP address on the VPN.

How much trouble would it be to change your home's IP subnet to something like

alx02Author Commented:
i changed the subnet to a 172 and same results. The It department has looked in further and they are convinced it has something to do with the vpn as i have gone to other people's home and can not log in on different service providers and setups.
I would agree, however I would also say that you may have had another issue from your home due to your IP subnet appearing to be within your works IP subnets.

Does anybody you know work?

If so, you may want to get a copy of the output from their ipconfig /all and netstat -rn to compare to what you have.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

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