Cannot connect to VPS

November 26, 2009 at 05:46:33
Specs: Windows Vista
My VPS has just been migrated to a new IP address (109.104.65.105) and now I am unable to connect to it. My internet connection itself is fine, but I am unable to get anything from this new IP address, whether mail, http, ftp or remote desktop connections, and pings and tracerts fail. However, everyone else can see the sites on this server fine (e.g. www.doraexplorer.com), and I can see it myself via sites like megaproxy.com - this only seems to be affecting my connection!

I've tried on both a Vista 64 and an XP 32 box, so it's not a PC issue. I've also tried disabling both Windows Firewall and the firewall on my router (a Linksys WAG354G V.2) but no joy there either.

Can anyone suggest where I should be looking next?

Thanks in advance


See More: Cannot connect to VPS

Report •


#1
November 26, 2009 at 06:33:10
I can ping it & FTP to it. So, it's something on your machine blocking it. Is Norton running?

How do you know when a politician is lying? His mouth is moving.


Report •

#2
November 26, 2009 at 06:59:58
Yeah, like I said this seems to be restricted to my connection, but I can't see why! No Norton here either, just AVG Free on the Vista box. The XP box has had it's firewall disabled and AV turned off, but that doesn't nake any difference, I still cannot connect from that box either.

Report •

#3
November 26, 2009 at 07:15:04
Tell me more about your LAN. For example:
modem > router > switch > all PCs. List the PCs if there are more than the 2 you mentioned. Do you have DSL or cable?

Where are the other people who don't have a problem located? Are they in another building with another service?

How do you know when a politician is lying? His mouth is moving.


Report •

Related Solutions

#4
November 26, 2009 at 07:32:02
The router is a Linksys WAG354G V.2, both PC's are physically connected and both are the only computers connected. The connection itself is ADSL2+. Those who can see the server are on a different connection.

As I said, my connection is fine for *everything* else, it's just this one IP address that won't connect - which is of course the one I really need!

Thanks


Report •

#5
November 26, 2009 at 08:19:14
What are some of the exact error messages you get?

Disconnect 1 of the PCs from the router & try the other. Then switch it.

Run ipconfig /all from both boxes & post the outputs here.

How do you know when a politician is lying? His mouth is moving.


Report •

#6
November 26, 2009 at 09:07:30
Unplugging everything else from the router except one connection makes no difference.

As for error messages, Firefox gives:

The connection has timed out. The server at www.doraexplorer.com is taking too long to respond.
etc.

IE:

Internet Explorer cannot display the webpage
etc.

FTP:

Status: Connecting to 109.104.65.105:21...
Error: Connection timed out
Error: Could not connect to server

ipconfig /all for the vista box gives:

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Vista64-PC
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : domain_not_set.invalid

Wireless LAN adapter Wireless Network Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Realtek RTL8187 Wireless 802.11b/g 54Mbps
 USB 2.0 Network Adapter
   Physical Address. . . . . . . . . : 00-15-AF-64-DB-84
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . : domain_not_set.invalid
   Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether
net Controller
   Physical Address. . . . . . . . . : 00-1E-8C-C8-A2-25
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4c17:6016:b227:c835%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 26 November 2009 11:12:39
   Lease Expires . . . . . . . . . . : 27 November 2009 11:12:38
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 251666060
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-10-23-BA-12-00-1E-8C-C8-A2-25

   DNS Servers . . . . . . . . . . . : 83.146.21.6
                                       212.158.249.5
                                       192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : isatap.{A69AD7A6-D7E0-48A8-A8CC-3AA94B130
A53}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:0:d5c7:a2d6:282b:28a9:a8b5:b1a5(Pref
erred)
   Link-local IPv6 Address . . . . . : fe80::282b:28a9:a8b5:b1a5%11(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Local Area Connection* 11:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : domain_not_set.invalid
   Description . . . . . . . . . . . : isatap.domain_not_set.invalid
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

The tracert error is:

C:\Users\Tony>tracert www.doraexplorer.com

Tracing route to www.doraexplorer.com [109.104.65.105]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    21 ms    27 ms    21 ms  host-83-146-18-123.dslgb.com [83.146.18.123]
  3  ge-0-0-0.30.cht-cor-001.bddsl.net [83.146.22.30]  reports: Destination net unreachable.

Trace complete.

ping test gives:

C:\Users\Tony>ping 109.104.65.105

Pinging 109.104.65.105 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 109.104.65.105:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging from within the router interface gives

 Ping Result:  Pkt Send:4 Pkt Recv:0 Avg Rtt:1.0 

Cheers


Report •

#7
November 26, 2009 at 09:13:01
And the XP box's ipconfig /all is:

Windows IP Configuration

        Host Name . . . . . . . . . . . . : behemoth
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : domain_not_set.invalid

Ethernet adapter Hamachi:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Hamachi Network Interface
        Physical Address. . . . . . . . . : 7A-79-05-96-EA-65
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : No
        IP Address. . . . . . . . . . . . : 5.150.234.101
        Subnet Mask . . . . . . . . . . . : 255.0.0.0
        Default Gateway . . . . . . . . . :
        DHCP Server . . . . . . . . . . . : 5.0.0.1
        Lease Obtained. . . . . . . . . . : 26 November 2009 17:13:57
        Lease Expires . . . . . . . . . . : 26 November 2009 17:18:12

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : domain_not_set.invalid
        Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Control
ler
        Physical Address. . . . . . . . . : 00-11-D8-0E-BF-DF
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.1.65
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 83.146.21.6
                                            212.158.249.5
                                            192.168.1.1
        Lease Obtained. . . . . . . . . . : 26 November 2009 17:13:06
        Lease Expires . . . . . . . . . . : 27 November 2009 17:13:06


Report •

#8
November 26, 2009 at 12:07:40
Disable Hamachi & see what happens.

How do you know when a politician is lying? His mouth is moving.


Report •

#9
November 26, 2009 at 12:42:15
OK, tried that - uninstalled Hamachi from the XP box - but again no difference. I don't think it's relevant anyway - the XP box is rarely used, and I don't have Hamachi on the Vista box. I only really mentioned the XP box to show that it wasn't a computer-specific issue.

I was thinking the tracert might shed some light on this. This isn't exactly my field (obviously), but it looks like the problem is happening after the request leaves my router, or am I reading it wrong?

Tracing route to www.doraexplorer.com [109.104.65.105]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    21 ms    27 ms    21 ms  host-83-146-18-123.dslgb.com [83.146.18.123]
  3  ge-0-0-0.30.cht-cor-001.bddsl.net [83.146.22.30]  
reports: Destination net unreachable.

Once again, thanks


Report •

#10
November 26, 2009 at 15:44:11
I running out of ideas but it's starting to look like a DNS problem. One thing that's strange is the 3rd entry. You have the 2 DNS entries of your ISP & under that you have the IP of the router. How did that happen? I've never seen more than 2 entries.

How do you know when a politician is lying? His mouth is moving.


Report •

#11
December 1, 2009 at 13:23:48
In case anyone runs into similar problems...

The issue was that the 109 range was only introduced recently (August '09) and they hadn't updated their filter list, hence the tracert failures.

Thanks to guapo for taking the time to suggest possible issues.

Cheers


Report •

#12
December 1, 2009 at 13:32:46
That wasn't too smart on their part.

How do you know when a politician is lying? His mouth is moving.


Report •


Ask Question