I'm writing a client program and a corresponding server program that
runs strictly on Microsoft Networks. I need the programs to communicate
using TCP/IP and IPX/SPX. Its not important that they communication
between the two computers be very fast. Currently I'm using the
Microsoft Winsock control for TCP/IP communication and I don't know what
I'm going to use for IPX/SPX. I would like the person using the client
to interface with the server program in the same way that a person
interfacing with a typical Microsoft Network would. For example, using
NetBios names instead of IP addresses and using controls like the ones
in Network Neighborhood. Is there a way for two programs to communicate
on a Microsoft Network where you don't have to worry about TCP/IP  and
IPX/SPX and just let windows figure out which protocol to use. I read
that there is a NetBios layer on top of Microsoft TCP/IP. Is there a way
to use this layer to do other things besides file transferes like
sending strings of data from one computer to another. I would also like
to get all the information that Network Neighborhood displays into my
program. The DirListBox can't accessing anything but drives and mapped
drives.
Thanks in advanced

    I'm writing a client program and a corresponding server program that
runs strictly on Microsoft Networks. I need the programs to communicate
using TCP/IP and IPX/SPX. Its not important that they communication
between the two computers be very fast. Currently I'm using the
Microsoft Winsock control for TCP/IP communication and I don't know what
I'm going to use for IPX/SPX. I would like the person using the client
to interface with the server program in the same way that a person
interfacing with a typical Microsoft Network would. For example, using
NetBios names instead of IP addresses and using controls like the ones
in Network Neighborhood. Is there a way for two programs to communicate
on a Microsoft Network where you don't have to worry about TCP/IP  and
IPX/SPX and just let windows figure out which protocol to use. I read
that there is a NetBios layer on top of Microsoft TCP/IP. Is there a way
to use this layer to do other things besides file transferes like
sending strings of data from one computer to another. I would also like
to get all the information that Network Neighborhood displays into my
program. The DirListBox can't accessing anything but drives and mapped
drives.
Thanks in advanced

    I'm writing a client program and a corresponding server program that
runs strictly on Microsoft Networks. I need the programs to communicate
using TCP/IP and IPX/SPX. Its not important that they communication
between the two computers be very fast. Currently I'm using the
Microsoft Winsock control for TCP/IP communication and I don't know what
I'm going to use for IPX/SPX. I would like the person using the client
to interface with the server program in the same way that a person
interfacing with a typical Microsoft Network would. For example, using
NetBios names instead of IP addresses and using controls like the ones
in Network Neighborhood. Is there a way for two programs to communicate
on a Microsoft Network where you don't have to worry about TCP/IP  and
IPX/SPX and just let windows figure out which protocol to use. I read
that there is a NetBios layer on top of Microsoft TCP/IP. Is there a way
to use this layer to do other things besides file transferes like
sending strings of data from one computer to another. I would also like
to get all the information that Network Neighborhood displays into my
program. The DirListBox can't accessing anything but drives and mapped
drives.
Thanks in advanced

    I'm writing a client program and a corresponding server program that
runs strictly on Microsoft Networks. I need the programs to communicate
using TCP/IP and IPX/SPX. Its not important that they communication
between the two computers be very fast. Currently I'm using the
Microsoft Winsock control for TCP/IP communication and I don't know what
I'm going to use for IPX/SPX. I would like the person using the client
to interface with the server program in the same way that a person
interfacing with a typical Microsoft Network would. For example, using
NetBios names instead of IP addresses and using controls like the ones
in Network Neighborhood. Is there a way for two programs to communicate
on a Microsoft Network where you don't have to worry about TCP/IP  and
IPX/SPX and just let windows figure out which protocol to use. I read
that there is a NetBios layer on top of Microsoft TCP/IP. Is there a way
to use this layer to do other things besides file transferes like
sending strings of data from one computer to another. I would also like
to get all the information that Network Neighborhood displays into my
program. The DirListBox can't accessing anything but drives and mapped
drives.
Thanks in advanced

    I'm writing a client program and a corresponding server program that
runs strictly on Microsoft Networks. I need the programs to communicate
using TCP/IP and IPX/SPX. Its not important that they communication
between the two computers be very fast. Currently I'm using the
Microsoft Winsock control for TCP/IP communication and I don't know what
I'm going to use for IPX/SPX. I would like the person using the client
to interface with the server program in the same way that a person
interfacing with a typical Microsoft Network would. For example, using
NetBios names instead of IP addresses and using controls like the ones
in Network Neighborhood. Is there a way for two programs to communicate
on a Microsoft Network where you don't have to worry about TCP/IP  and
IPX/SPX and just let windows figure out which protocol to use. I read
that there is a NetBios layer on top of Microsoft TCP/IP. Is there a way
to use this layer to do other things besides file transferes like
sending strings of data from one computer to another. I would also like
to get all the information that Network Neighborhood displays into my
program. The DirListBox can't accessing anything but drives and mapped
drives.
Thanks in advanced

Sorry about all those posts. My client kept acting like my post would never
completely send so I kept resending it.