I have a linux server that hosts a website (widgets) for our organization (It was setup by some vendor that is long gone)

The server has two interfaces:
ETH0: 192.1.1.25 /24
ETH1: 10.1.1.25 /24

From the network if I ping the website widgets it translates to 10.1.1.25.

When I go home and launch the VPN I cannot access the site by its name. I can ping it by the name though. However if I type in 192.1.1.25 into the browser I can access the site.

The VPN assigns IPs in the 192.1.200.0/24 subnet.

The routing table looks like:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
192.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
192.1.0.0 192.1.1.1 255.255.0.0 UG 0 0 0 eth0
0.0.0.0 10.1.1.85 0.0.0.0 UG 0 0 0 eth1




Thanks for any assistance.

Welcome to LQ.


10.x.x.x and 192.x.x.x are reserved addresses for private networks, I think the other one is 172.16.x.x. All internal networks belong here, and they share their address with countless other internal networks.

I know nothing about your vpn, but I gather you have access to your internal 192.1.x.x from an address on 192.1.x.x. You don't tell us anything's wrong, it's just mystifying. The internet uses ports to identify services. Port 80 is http (browsing). VPNs use many ports depending on type.

You really don't understand much of this, do you? If it's a business, hire/contract someone to maintain the site. Get him/her in and let him explain it to you. If the club is penniless, there's a hard road ahead for somebody.

The reason you cannot access the server over VPN using the name is because your internal DNS resolves to the 10.x.x.x address. There are several ways to address this so that it will work.

1. Setup DNS to give out addresses depending on the IP Address that requests them
2. Allow access to the 10.x.x.x network from the 192.x.x.x network
3. Add a host file entry for this server into your host file.

Almost,

10.x.x.x/8
172.16.x.x/12
192.168.x.x/24

Are the reserved IP Address ranges

I knew it was Class A, B, & C networking officially but I've had a stroke since I grokked this stuff and a little of this is hazy. 10.x.x.x and only /8?

RFC1918 Page 3.

/Groan
I never realised how much I had grown to hate fixing electronic hardware until I stopped in 2006, and people came after me to do one last job. . .

I never realised how much I hated engineering blurb until I had to read some after I graduated in 2014. Your network standard brought it all flooding back. I had a Math section in my own final paper, analyzing my design and I can't follow it now :-(. I should have googled instead of asking.

Thanks for the reply, nevertheless

You are welcome. I'm just here to help those who ask for it and I can.

lazydog, we've kinda hijacked Abernut's thread with our(my) waffling.

lazydog has highlighted the Private Address range. Unless you're employed in BBN Communications in Cambridge, England, you shouldn't be using that (192.1.1.25) IP in case it gets to the outside world, where it is registered and will get redirected to BBN Communications. That could certainly affect your routing issues! BBN may even view it as spam, or an attack. Use 192.168.1.25 instead - that's private.

Make that change if you're not the registered owner of 192.1.1.25, and see what effect that has on your routing issues.

From where will I get a new packet tracer for this ???

Welcome to LQ, mattypul

Post a new thread for a new question pls. That offers you the choice to "Check for similar threads." You should do that, in case your query is already answered. This_Tutorial offers a good idea of what to include. Do not use words like 'this' 'that' 'it' but be explicit in naming things and don't presume we can guess. Don't tell us it fails without giving the error, even if it means nothing to you.