ATCS not working for me

[4mula1]

When NS had their first pileup this year I was unable to get ATCS Monitor working with the Fort Wayne Metro layout. It had worked before. Since then I've tried periodically and it still doesn't work.

On a whim I tried connecting to fwaudio.dyndns.org:4800 with my browser and all it returns is a number. If I hit refresh the number increases.

Other layouts work (NS Chicago Line has a lot of errors) but there is no packet activity in the window. Anybody experiencing this?

[Rob]

Seems ok here. Only trouble point i know of is the CSX Kingsbury server is having issues, so when i get reception i add my own to it and get partial coverage from milford to bremen or so usually, ft wayne and deshler servers cover east of cromwell very good then.

[Greg46m]

Hmm, that's very strange, I do see somewhat of a problem.

Try doing this for me, use this address to try to connect, 65.25.154.112, port 4800. What happens?

What IP address are you trying to connect from? I looked up the address from your last post and it doesn't show up in my ATCS server log. There are a few logs from clients that didn't fully connect and therefore I cannot see their IP's.

Additionally, open up the command prompt program (Select Run under the Start button and type "cmd" and enter) Type in (without quotes) "ping fwaudio.dyndns.org". If you don't get a reply, try this "ping 65.25.154.112". If still no reply, let me know. I tried this from my server site and I didn't get a response. It kinda looks like there might be an issue with my ISP perhaps.

[wayne b]

Just wondering, are the boxes checked in the configure>source>fwaudio port 4800

[4mula1]

Hmm, that's very strange, I do see somewhat of a problem.

Try doing this for me, use this address to try to connect, 65.25.154.112, port 4800. What happens?

What IP address are you trying to connect from? I looked up the address from your last post and it doesn't show up in my ATCS server log. There are a few logs from clients that didn't fully connect and therefore I cannot see their IP's.

Additionally, open up the command prompt program (Select Run under the Start button and type "cmd" and enter) Type in (without quotes) "ping fwaudio.dyndns.org". If you don't get a reply, try this "ping 65.25.154.112". If still no reply, let me know. I tried this from my server site and I didn't get a response. It kinda looks like there might be an issue with my ISP perhaps.

I'm at work now so I can't use ATCS Monitor, but doing an nslookup on fwaudio.dyndns.org gives me the IP address of (you guessed it) 65.25.154.112. I remotely logged into my Solaris box at home and I don't receive a response when pinging the host. FWIW, my home IP address is static so the IP address logged from my original post is my home IP address (xxx.xxx.132.99).