Hello,

Its been a good linux day today I have achieved many things. Firstly I installed slackware10.2, which went without a problem, and acidrip and mplayer (slight nightmare with libdvdcss but there was bound to be some problems).

I also setup a ftp server with vsftpd and apache with my website on it, and connected the whole thing up with dnydns to my ip address.

This is where I have a slightly odd problem. When I connect to either server with the domain names blah.blah.net etc from outside of my network they work fine. But if I connect with those names from inside my network I get the login for the configuration of the router. The servers work as expected if I use the ip of the computer with them on from inside the router. I found an earlier post that said to change the hosts file, I did this as per the post but it has made no difference. The router is setup with port forwarding rather than DMZ. Anyone know why this might be happening. Its not really a problem, but I would be interested to the whys and wherefores.

I like getting all these little computer jobs done, espically on rainy sundays like today.

Cheers,
Phil

Hi

You mention you have a network right?
It's NAT issue we're looking at here. What router are you using?

You can do simple traceroute to the domain name blah.blah.net from a local pc and see where it goes.

There's one alternative here. if you have control over your BIND server, quick setup a A host over the names of the domain/computer then you can instantly access the files.

hi,

tracert goes to the router in 1step bouncing of one of the btcentralplus servers

There is a NAT on the router, its a 'zoom' one, can't remember the exact model.
Access to the files is not a problem as the directory that I'm serving is shared with nfs to the LAN, the ftp server so I can upload stuff from uni and other things, er.... and its fun.

cheers
Phil

You will find that when using dynamic dns addressing for a website hosted on your network being access internally *will* simply show you your router login page. There's tons of posts explaining why, but short anwser, just access it via it's internal name or ip address whilst on your network.

I have the same setup as yourself. I don't use Slack but I don't think that is your problem.

It sounds like it may be an issue with Router security or authentication. What kind of router are you using?