| T O P I C R E V I E W |
| dvsmith |
Posted - Jun 16 2010 : 3:55:05 PM
Hi,
I can't seem to connect to Fatt when I'm on the new DUHS VPN. I connect to it just fine using the old VPN, so I'm not sure what's going on. The output of nslookup appears to be the same under both circumstances (see below). I am using a MacBook Pro, and I'm trying connect via an smb mount.
new VPN
David-V-Smiths-MacBook-Pro:~ dvsmith$ nslookup fatt.dhe.duke.edu
Server: 152.16.177.101
Address: 152.16.177.101#53
Name: fatt.dhe.duke.edu
Address: 152.16.111.80
old VPN
David-V-Smiths-MacBook-Pro:~ dvsmith$ nslookup fatt.dhe.duke.edu
Server: 152.16.177.101
Address: 152.16.177.101#53
Name: fatt.dhe.duke.edu
Address: 152.16.111.80
It claims it can't see or connect to Fatt when I'm on the new VPN. Let me know what else I can send to help debug this issue...
Thanks,
David
|
| 13 L A T E S T R E P L I E S (Newest First) |
| francis.favorini |
Posted - Jun 27 2010 : 9:34:51 PM
Glad it's working now.
The 10.*.*.* addresses are private, non-routable addresses that will only be meaningful inside the DUMC network. When you connect to a computer outside of DUMC (such as the web site you mention), it will see a public IP address (152.16.*.*) via a process called Network Address Translation (NAT). |
| dvsmith |
Posted - Jun 25 2010 : 7:25:24 PM
Thanks... I figured it was some firewall issue. I can access Fatt on the new VPN now.
I was/am only using the new VPN.I was checking my IP with http://www.whatsmyip.org/ -- which apparently isn't 100% correct for some reason. If I use ifconfig instead, it looks like a 10.14.x.x address, and that's what I get when I log on to cluster. |
| francis.favorini |
Posted - Jun 24 2010 : 3:50:40 PM
I am told if you are on the new VPN, you should be getting a 10.14.x.x address. I have now added 10.14.x.x subnet to the firewalls on our servers.
You may want to check that you are using the new VPN only and not both at the same time or something? How are you determining your IP address? |
| francis.favorini |
Posted - Jun 24 2010 : 3:01:48 PM
This is starting to seem like a DHTS firewall issue. I'll have them check it. |
| dvsmith |
Posted - Jun 23 2010 : 9:59:56 PM
Nope... I can't connect to those either (can't see it; error message below). I'm still getting the same IP when I log onto the new VPN.
The server “fatt.dhe.duke.edu” may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again. |
| francis.favorini |
Posted - Jun 23 2010 : 6:35:38 PM
Try connecting to Hill or Goldman. It doesn't matter if you don't have any experiments there, you should still be able to see the top-level directories. |
| dvsmith |
Posted - Jun 23 2010 : 4:30:15 PM
OK, Fatt seems to be working on the old VPN again... Not sure why it was down for about an hour. Thanks. |
| dvsmith |
Posted - Jun 23 2010 : 3:14:44 PM
OK, now I can't connect to Fatt at all... Did it just crash or something?
|
| dvsmith |
Posted - Jun 23 2010 : 10:52:21 AM
I still can't connect to Fatt using the new VPN client. Is anyone else having this problem? I'm just hoping to get this resolved before they eliminate the old VPN client. |
| dvsmith |
Posted - Jun 18 2010 : 10:38:31 PM
I can connect to Munin and Hugin, but not Fatt. I don't have anything on any other server. Maybe this is normal, but I appear to have the same IP as the last time I logged on (152.16.51.172); I didn't think the old VPN worked that way. |
| francis.favorini |
Posted - Jun 18 2010 : 2:20:42 PM
Is it only Fatt you can't connect to? |
| dvsmith |
Posted - Jun 17 2010 : 12:01:50 PM
When I'm on the new VPN, my IP address is 152.16.51.172.
When I'm on the old VPN, my IP address is 152.16.179.130.
If I remember correctly, the old VPN always gave us a 152.16.179.xxx or 152.16.180.xxx address (or something like that).
Thanks,
David
|
| francis.favorini |
Posted - Jun 17 2010 : 10:56:01 AM
What IP address are you getting on the new VPN? |
