Very Computer

1. Can't connect Warp 4 to NT 3.51 server

I'm trying to diagnose a Warp 3 system at a customer site that can't see
the customer's NT4 server on the other side of a router. I installed
tcpbeui. I can ping the NT machine but I can't view its shares.

I tried to recreate the situation in my office by setting my Warp 4
system to have only tcpbeui, no netbeui, thereby forcing it to use TCP
to talk to an NT3.51 server on the same segment. I find that I now get
error NET3502 (network busy or out of resources) where I could netview
the server with netbeui installed before. The server has the server
service bound to both the NETBIOS and WINS(TCP) stacks. I can view the
server from my Linux box using smbclient, so it must be accessable by
TCP/IP. I can't understand why my Warp 4 box fails to connect to it.

What can I look at to trace what's going wrong?

--
Ken

http://www.sewingwitch.com/ken/
http://www.StopTheWarNow.com/
http://www.215Now.com/

2. campus connectivity innovations

3. Upgrading NT 3.51 Server to NT 4.0 with SMS

4. Corruption in Active Directory?

5. Primary srv can't copy logon scripts to logon srv

6. *$*$ 20 Weak Signal Challenge (DSP Post) - Now $30 $*$*$

7. Printing NT w/s > NT srv > Unix > Lexmark

8. macro sendkey functionality

9. Win NT Srv with two NIC's and two subnets - Clients don't install

10. Upgrading NT 3.51 to NT 4.0 using SMS

11. Upgrade NT 3.51 to NT 4.0 with SMS

12. NT 4.0 vs. NT 3.51 vs. Win95

13. NT 4.0 WS won't shutdown because of PCM