| >>The configuration of the server has been checked and a third party NIC
>>was installed as a test, which worked.
We have AppleTalk bound and working on our FDDI adapter here running
Windows NT 3.5 Server so I would definitely look at the configuration.
Check the Bindings to make sure they're lit. Also, post the errors
that you're seeing in the Event Viewer, especially if they are from
"Defpa". Do you have other NICs loaded/bound in the server? If so,
you have to be careful with the bindings.
/l
|
| I am the NPB contact for this, reseller. There is no other cards in the
server , both TCP , NETBUI and IPX have bound ok. The only other
differance that I can see between this and the config mentioned in the
previous reply is that ours is over copper. Does the config of the card
require changing from default or are factory settings ok. As for the
error messages there does not appear to be anything other a message to
say that this has not worked. Basically what I am asking is appletalk
supported over the PCI FDDI UTP card and has anyone had experiance in
making this work?
Cheers Graeme McDonald
Digital
New Zealand.
|
| >> -< feedback on UTP PCI over copper >-
I should have mentioned that we're also using our -UA UTP adapter.
There is no difference between the -AA, -DA, and -UA adapters at the
driver level. The physical layer differences won't make the driver
behave any differently, certainly not when it comes to protocol
bindings.
This is definitely a configuration problem, though what, I'm not quite
sure at the moment. Could you provide a dump of the Registry entries
for the Defpa? First you need to run the Registry Editor by running
REGEDT32.EXE. Next, go under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Defpa1\Parameters
On the right side of the screen you should see a dozen or so keywords
and their current values. The "BusType" and "CardType" keywords
should be equal to 5. The "MediaType" keyword should be equal to 4.
If memory serves, AppleTalk was quite fussy when it came to one of
these keywords where other protocols were not. If these keywords are
somehow missing or incorrect, please add/change them and reboot.
- Larry
|