ADTPro and Uthernet II [message #368964] |
Tue, 12 June 2018 23:47 |
|
Originally posted by: Robert Allred
I need some help troubleshooting.
I am running ADTPro server 2.0.2 on my MacBook Pro macOS 10.13.4. Client is an Apple II+ running ADTPro 2.0.0 with Uthernet card in slot 3. Self-test of the ethernet card come back as expected. When I try to connect from the client to the server, I get a host timeout after about 10 seconds.
I have turned off firewall on the MacBook. I have tried DHCP and manually configuring on the client side.
Any ideas?
Pics:
https://photos.app.goo.gl/6aYUsJtrgFyJfHSn6
|
|
|
|
Re: ADTPro and Uthernet II [message #368974 is a reply to message #368967] |
Wed, 13 June 2018 10:59 |
|
Originally posted by: Robert Allred
That's what I'm trying to do...
I'll dig out my audio cables and update that way and then try again.
On Tuesday, June 12, 2018 at 10:37:04 PM UTC-7, Jeff Ramsey wrote:
> This worked for me but I was using the 2.0.2 client as well as the 2.0.2 server. Can you try updating your client disk?
|
|
|
Re: ADTPro and Uthernet II [message #368977 is a reply to message #368967] |
Wed, 13 June 2018 14:02 |
|
Originally posted by: Mark D. Overholser
On 12-Jun-18 22:37, Jeff Ramsey wrote:
> This worked for me but I was using the 2.0.2 client as well as the
> 2.0.2 server. Can you try updating your client disk?
>
Only the v2.0.1b and v2.0.2 Clients support the Uthernet II..
Upgrade your Client to v2.0.2 and you should have a Uthernet II option...
MarkO
|
|
|
Re: ADTPro and Uthernet II [message #368978 is a reply to message #368977] |
Wed, 13 June 2018 14:32 |
|
Originally posted by: Brian J. Bernstein
On Wednesday, June 13, 2018 at 2:02:18 PM UTC-4, Mark D. Overholser wrote:
> On 12-Jun-18 22:37, Jeff Ramsey wrote:
>> This worked for me but I was using the 2.0.2 client as well as the
>> 2.0.2 server. Can you try updating your client disk?
>>
>
>
>
> Only the v2.0.1b and v2.0.2 Clients support the Uthernet II..
>
>
> Upgrade your Client to v2.0.2 and you should have a Uthernet II option...
>
>
> MarkO
I've observed the same problem over and over with the latest client/server on a Mac. I'm not quite sure why, but I think I've observed better results when running the ADT server on a Windows VM. Kind of solving the problem by dropping an anvil on a nail, but haven't been able to find diagnostic output despite enabling debug messages. Then again, I haven't looked TOO hard :-)
|
|
|
|