Note: If your DNS Servers listed the same IP address as your Default Gateway, read the following!

The DNS server (Domain Name System) server can get a bit complicated. Some router's act as an intermediary between for the actual DNS servers and your computer. If this is the case your Default Gateway will list the same IP address as the DNS Servers entry. We need to have the correct DNS Server IP addresses not the Default Gateway. You will not be able to use the Internet if we don't find out what your actual DNS servers are. There are a couple different ways to find these. The first way is to log into your router's web interface and look at your router's status page. On that page you should see an entry for DNS Servers, or Name Servers. Write down the IP addresses of these DNS Servers. Another way to find out what the correct DNS Servers to use, is to call your local Internet Service Provider or ISP. They should know the IP addresses of your DNS Servers right away. If they ask you why you need them, simply tell them you are trying to setup a static IP address on your computer. If they try to sell you a static external IP address, don't buy it. That's an entirely different thing than what you are trying to setup here.

Start, run, cmd and type “tracert google.com”

The first address you see after 192.168.x.x should be the DNS server your router routes through.

The default gateway and the DNS server both have the same address listed here which I think the quote above was saying isn’t right?

Paste the output here. I want to see the IP address for the first hop outside of your home network, basically.

C:\Users\jenni>tracert google.com

Tracing route to google.com [2a00:1450:4009:81c::200e]
over a maximum of 30 hops:

1 8 ms 2 ms 2 ms broadband.bt.com [2a00:23c7:6e09:8401:ced4:2eff:fe87:2bc9]
2 5 ms 4 ms 4 ms 2a00:2302::1103:203:4cf
3 * * * Request timed out.
4 * * * Request timed out.
5 * * 17 ms 2a00:2380:3013:8000::10
6 16 ms 16 ms 16 ms 2a00:2380:13::95
7 19 ms 16 ms 16 ms 2a00:2380:2001:7000::19
8 * * * Request timed out.
9 * 19 ms * 2001:4860:0:1101::1
10 16 ms 15 ms 15 ms 2001:4860:0:1101::10
11 20 ms 17 ms 17 ms 2607:f8b0:e000:8000::6
12 17 ms 16 ms 16 ms 2001:4860::9:4001:2716
13 24 ms 18 ms * 2001:4860:0:135e::1
14 20 ms 18 ms 20 ms 2001:4860:0:1::316d
15 19 ms 17 ms 16 ms lhr48s13-in-x0e.1e100.net [2a00:1450:4009:81c::200e]

Trace complete.

Start, run, cmd and type “tracert google.com”

The first address you see after 192.168.x.x should be the DNS server your router routes through.

That's unlikely to be the case. DNS lookups are out of band, the DNS server doesn't forward traffic.

Gilly - I looked at the link you provided and couldn't see the section you highlighted, was it on that link?

You shouldn't need to do anything with DNS here, you just need to port forward. What's your router make and model? Normally port forwarding is either a one or two step process. If it's one step, you just create a firewall rule (usually under the security section) to forward incoming TCP traffic on port 30000 to your PC IP address. If it's two step, you have to create a service for TCP traffic on port 30000 and give it a name, then enable a firewall to forward that service to your PC IP address

That's unlikely to be the case. DNS lookups are out of band, the DNS server doesn't forward traffic.

Gilly - I looked at the link you provided and couldn't see the section you highlighted, was it on that link?

You shouldn't need to do anything with DNS here, you just need to port forward. What's your router make and model? Normally port forwarding is either a one or two step process. If it's one step, you just create a firewall rule (usually under the security section) to forward incoming TCP traffic on port 30000 to your PC IP address. If it's two step, you have to create a service for TCP traffic on port 30000 and give it a name, then enable a firewall to forward that service to your PC IP address

Here you go:

https://www.bt.com/help/broadband/learn ... my-bt-hub-

You want port 30000 (for both internal and external, start and end) and protocol TCP, and the 'device' should be the IP address or name of whichever machine you're running FoundryVTT on.


Once you've done all that, you can give someone the external IP of your network (using something like https://whatismyip.com) and they'll be able to put that IP address and port 30000 into the Foundry client.

Lol what? There are… quite a lot better places to look for this information!

Lol what? There are… quite a lot better places to look for this information!

According to the email I just got from Google, this is the thread the most non-Beex people are searching for.

Hello, new viewers!