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

Hi,

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

Iperf                dast.nlanr.net/Projects/Iperf           Open-Source

Also any specific entries in the VPN client log?

Here is what the log says;
Cisco Systems VPN Client Version 4.7.00.0533
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.

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.

giltjr,
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.

All,
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 = 38.101.72.145
 NAS-Identifier = <not present>
 Client-Friendly-Name = Cisco 2811 Router VPN
 Client-IP-Address = 38.101.72.145
 Calling-Station-Identifier = 208.102.1.138
 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.

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 127.0.0.1. 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 127.0.0.1 as the gateway address.  The first is for the whole loopback address space and that should look like:

        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1

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

        y.y.y.y         255.255.255.255 127.0.0.1       127.0.0.1       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.

here is the table;
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0         10.0.1.1        10.0.1.3       20
          0.0.0.0          0.0.0.0        10.0.10.4       10.0.10.4       1
         10.0.0.0        255.0.0.0        10.0.10.4       10.0.10.4       20
         10.0.1.0    255.255.255.0         10.0.1.3        10.0.1.3       20
         10.0.1.0    255.255.255.0        10.0.10.4       10.0.10.4       1
         10.0.1.1  255.255.255.255         10.0.1.3        10.0.1.3       1
         10.0.1.3  255.255.255.255        127.0.0.1       127.0.0.1       20
        10.0.10.4  255.255.255.255        127.0.0.1       127.0.0.1       20
   10.255.255.255  255.255.255.255         10.0.1.3        10.0.1.3       20
   10.255.255.255  255.255.255.255        10.0.10.4       10.0.10.4       20
     38.104.22.10  255.255.255.255         10.0.1.1        10.0.1.3       1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
        224.0.0.0        240.0.0.0         10.0.1.3        10.0.1.3       20
        224.0.0.0        240.0.0.0        10.0.10.4       10.0.10.4       20
  255.255.255.255  255.255.255.255         10.0.1.3        10.0.1.3       1
  255.255.255.255  255.255.255.255        10.0.10.4               3       1
  255.255.255.255  255.255.255.255        10.0.10.4       10.0.10.4       1
Default Gateway:         10.0.10.4
===========================================================================
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 10.0.1.3 with a subnet mask of 255.255.255.0.

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

         10.0.1.0    255.255.255.0         10.0.1.3        10.0.1.3       20
         10.0.1.0    255.255.255.0        10.0.10.4       10.0.10.4       1

Which is really confusing because this says to get to any host in the 10.0.1.0/24 subnet you must go through 10.0.10.4, 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 192.168.10.0/24?

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.