sabnzbd & windows server 2003

[Mr5o1]

Hi All..

Been using sabnzbd for a while now. I love it, thanks for the hard work.

Until recently I've been using amahi as a home server, which has a sabnzbd package. For different reasons I eventually got a bit over amahi, and decided to go with Windows Server 2003 instead.

That said, amahi did have cool local addresses for things.. so sabnzbd would be at sabnzbd.home.com or something instead of 192.168.1.123:8080/sabnzbd

There must be a way to configure that sort of redirect in server 2003.. but I dont seem to be able to find anything. One of those "I'd be able to work it out if I knew what to search for" sort of things.

Any thoughts?

[shypike]

You's have to configure the DNS server of Server2003
and then tell your client PC's to use that.
The simple way is to add some entries to the local HOSTS file of your clients.
Probably here: c:\Windows\System32\drivers\etc\hosts

[sander]

@Mr5o1

Do you mean access to SABnzbd from a computer on your local LAN, or from a computer on Internet?

[john3voltas]

You's have to configure the DNS server of Server2003
and then tell your client PC's to use that.
The simple way is to add some entries to the local HOSTS file of your clients.
Probably here: c:\Windows\System32\drivers\etc\hosts

I'm not so sure this would work.
The OP wants to have FQDN's out off host:port.
Hosts file only specifies hostnames not ports...

[Mr5o1]

Thanks for your replies..

@shypike: already configured it to be a domain controller and DNS
@sander: local LAN
@john3voltas: thanks.. maybe 'fqdn' is the term I'm looking for.. I'll look into it.

[sander]

Thanks for your replies..

@shypike: already configured it to be a domain controller and DNS
@sander: local LAN
@john3voltas: thanks.. maybe 'fqdn' is the term I'm looking for.. I'll look into it.

I'm not a Windows user, but this is worth a try: find out the Full Computer Name (in control panel -> system or something like that), and "PING" that Full Computer Name.
If that works from different Windows computers, I guess it should also work for HTTP://:8080/

[john3voltas]

Sander, from where I stand it looks way more difficult than just that.
Let's say he has SAB on port 8080, Transmission on port 8090, etc.
Instead of http://localhost:8080/ to get to SAB he wants to http://sab.his_pc.com/
Instead of http://localhost:8090/ to get to Transmission he wants to http://torrent.his_pc.com/
See how the port numbers are gone and see how the hostname:port was replaced by FQDN.
Cheers

[sander]

Sander, from where I stand it looks way more difficult than just that.
Let's say he has SAB on port 8080, Transmission on port 8090, etc.
Instead of http://localhost:8080/ to get to SAB he wants to http://sab.his_pc.com/
Instead of http://localhost:8090/ to get to Transmission he wants to http://torrent.his_pc.com/
See how the port numbers are gone and see how the hostname:port was replaced by FQDN.
Cheers

Thanks for clarifying.