VDI is purposely blocking traffic from Dialtone Internet again.

It caused me some trouble yesterday when I was trying to e-mail someone I'm working with. The e-mail account I was using was hosted on an Interserver.net server, and his e-mail account was hosted on a Dialtone Internet server.

They were doing this a couple weeks back too. They eventually lifted the block... but now it's back again.

Can anyon else confirm this? And if they have done that does anyone know why?

vdi is not blocking anyones traffic. If email not working check the dns setting and reverse/forward on the server name.

that will cause the email to reject.

I don't think VDI would do such a thing.. Maybe your ISP doesn't allow relying since you are using the server to email someone from DI..

Not only e-mail is down; telnet, FTP and traceroute don't work either.

I have a server on Dialtone Internet (66.33.60.115), and a server on InterServer/VDI (216.74.79.145).

Tracing from DI to VDI:

traceroute to 216.74.79.145 (216.74.79.145), 30 hops max, 38 byte packets
1 66.33.60.1 (66.33.60.1) 16.618 ms 3.636 ms 0.741 ms
2 12.119.94.5 (12.119.94.5) 1.747 ms 5.086 ms 12.310 ms
3 gbr4-p100.ormfl.ip.att.net (12.123.218.66) 16.161 ms 10.162 ms 104.933 ms
4 gbr3-p10.attga.ip.att.net (12.122.2.129) 14.968 ms 13.504 ms 13.310 ms
5 gbr4-p60.attga.ip.att.net (12.122.1.142) 13.383 ms 13.924 ms 14.184 ms
6 gbr4-p30.wswdc.ip.att.net (12.122.2.226) 25.580 ms 26.352 ms 25.571 ms
7 ggr1-p370.wswdc.ip.att.net (12.123.9.53) 25.488 ms 25.588 ms 25.816 ms
8 pos6-3.core1.Washington1.Level3.net (209.244.219.157) 27.226 ms 26.904 ms 26.878 ms
9 so-4-0-0.mp1.Washington1.Level3.net (209.247.10.65) 27.203 ms 27.199 ms 27.232 ms
10 so-0-0-0.mp1.Weehawken1.Level3.net (209.247.8.46) 32.770 ms 32.555 ms 32.629 ms
11 loopback0.hsipaccess1.Weehawken1.Level3.net (209.247.2.3) 33.414 ms 33.417 ms 33.100 ms
12 p4-0.core1.cftnnj.inet.vdi.net (63.211.89.150) 34.790 ms 34.239 ms 83.788 ms
13 * * *
14 * * *

Tracing from VDI to DI:

traceroute to 66.33.60.115 (66.33.60.115), 30 hops max, 38 byte packets
1 trapezoid (66.78.36.71) 1391.633 ms !H 2995.415 ms !H 2999.937 ms !H

Note that I'm logged into both servers at this moment! I can connect to both, but they can't connect to each other. The traceroute from DI to VDI fails after entering VDI's network, and the traceroute from VDI to DI can't even get out of VDI's network. This suggests that VDI is doing something underhanded.

I've complained to Interserver about this the last time they happened, and they said that VDI was blocking traffic from DI for legal reasons.

If I do a trace route to vdi.net from my DI server, it goes through fine. If I do a trace route to the IP number you listed in your trace route, I get the same results as you do.

I can also reach www.vdi.net from my DI server.

Looks like VDI only block traffic to certain IP. I would call them and find out.

Teach me how to read this,


traceroute to 216.74.79.145 (216.74.79.145), 30 hops max, 38 byte packets
1 66.33.60.1 (66.33.60.1) 16.618 ms 3.636 ms 0.741 ms
2 12.119.94.5 (12.119.94.5) 1.747 ms 5.086 ms 12.310 ms
3 gbr4-p100.ormfl.ip.att.net (12.123.218.66) 16.161 ms 10.162 ms 104.933 ms
4 gbr3-p10.attga.ip.att.net (12.122.2.129) 14.968 ms 13.504 ms 13.310 ms
5 gbr4-p60.attga.ip.att.net (12.122.1.142) 13.383 ms 13.924 ms 14.184 ms
6 gbr4-p30.wswdc.ip.att.net (12.122.2.226) 25.580 ms 26.352 ms 25.571 ms
7 ggr1-p370.wswdc.ip.att.net (12.123.9.53) 25.488 ms 25.588 ms 25.816 ms
8 pos6-3.core1.Washington1.Level3.net (209.244.219.157) 27.226 ms 26.904 ms 26.878 ms
9 so-4-0-0.mp1.Washington1.Level3.net (209.247.10.65) 27.203 ms 27.199 ms 27.232 ms
10 so-0-0-0.mp1.Weehawken1.Level3.net (209.247.8.46) 32.770 ms 32.555 ms 32.629 ms
11 loopback0.hsipaccess1.Weehawken1.Level3.net (209.247.2.3) 33.414 ms 33.417 ms 33.100 ms
12 p4-0.core1.cftnnj.inet.vdi.net (63.211.89.150) 34.790 ms 34.239 ms 83.788 ms
13 * * *
14 * * *

Dollac: It means that traffic from my DI server to my VDI server at 216.74.79.145 only reaches as far as p4-0.core1.cftnnj.inet.vdi.net before it gets blocked.

Someone on a "local" forum I subscribe to has stated they cannot reach some VDI servers from their ISP. I have posted a request for their ISPs name.

This could be interesting...

The user I was referring to stated they use BellSouth ADSL with Dynamic IP. They also said that some other ADSL users could access the site fine.

Not sure what's happening here as I can reach the site fine, and have no other method to test...

Originally posted by pmak0
Dollac: It means that traffic from my DI server to my VDI server at 216.74.79.145 only reaches as far as p4-0.core1.cftnnj.inet.vdi.net before it gets blocked.

I would cal the owner of the server and see if portsentry put you on the SH*tlist.. that could do it.

Originally posted by William


I would cal the owner of the server and see if portsentry put you on the SH*tlist.. that could do it.



Quite right Bill, it seems that some of the most unlikely IP's turn up on that s***tlist, which stops email and all... good advice.

Worth a regular check ;)

Originally posted by William


I would cal the owner of the server and see if portsentry put you on the SH*tlist.. that could do it.

Nope, we have 4 people right now that can't access our sites on VDI

One in Florida, one in New Jersey, one in Austria and one in Ohio

none of them is in the S***List

see if the ip are close , 66.74. what ever.

then make sure the mask for the ip on the server for that ip is... 255.255.255.255 aliases IPs should be 255.255.255.255 not 255.255.255.0

Originally posted by CRego3D


Nope, we have 4 people right now that can't access our sites on VDI

One in Florida, one in New Jersey, one in Austria and one in Ohio

none of them is in the S***List

blah, still can't reach your site Carlos...
been about 5 days or so...

VDI is not blocking traffic to DI's network. The problem you are experiencing is actually a server problem that administrator has to fix, it's not an issue with VDI. If you look at the post where someone attempted to traceroute and it died at the first hop, if you look at the hop closely, you will see that is the local machine, it doesn't even touch the VDI network.

It is a local problem with the network mask, some administrators do not specify the network mask letting the machine default to a network mask of 255.0.0.0, the problem with this is if you attempt to access any machine with any IP address that starts with 66 (66.x.x.x), it will attempt to contact the host on the local network instead of forwarding the packet to the default gateway, when it doesn't receive a response, it displays '!H'. Simply ask the server administrator to correct the network mask and this problem will go away.

If VDI was blocking the hosts, *.core1.cftnnj.inet.vdi.net or *.edge1.cftnnj.inet.vdi.net would respond with '!X' which is short for 'Administratively Prohibited', not just ignoring the packet (which would display as '*').

Omachonu Ogali (via John Sorrentino's workstation)
missnglnk@vdi.net

So what's the command for setting the netmask? Does anyone know?

Hello,

You should contact your upstream provider (interserver) they were given all the information on this already and they will be able to help you.

John