ME logging on to NT domain problem

I have a laptop with ME on it. I've configured it to log into my NT domain server. The network settings are correct, the system is obtaining the ip from the dhcp server, and all appears to be well. I can ping the server and other computers on the network from the laptop, but it will not:
1. in the logon screen, the domain name doesn't show up as it does on my 95 systems.
2. I get the "can't connect" error when I try to map drives to the server.
Any suggestions ? or is there something special I have to do with ME ?
Thanks
Tracy

1. RE: ME logging on to NT domain problem
lbyard Dec-05-01 04:13 PM
In response to message 0

In Start, Settings, Control Panel, Network, is your Priamry Network Login Wdinows or the Client for Microsoft Networks? Larry

2. RE: ME logging on to NT domain problem
Gixster Dec-05-01 04:28 PM
In response to message 1

I've tried it both ways. It is set to Client for Microsoft Networks, and that should work, but it's not. I can't get validated.
Thanks
Tracy

3. RE: ME logging on to NT domain problem
lbyard Dec-05-01 05:44 PM
In response to message 2

Are the workgroup and domain names identical? They have to be. Larry

4. RE: ME logging on to NT domain problem
Gixster Dec-06-01 12:12 PM
In response to message 3

Yes, they are identical. It's really throwing me for a loop.
Thanks
Tracy

6. RE: ME logging on to NT domain problem
lbyard Dec-06-01 05:44 PM
In response to message 4

How is it connected to the network? Larry

7. RE: ME logging on to NT domain problem
Gixster Dec-06-01 11:01 PM
In response to message 6

Connected through CAT 5 cable to my NT Server. I know the cable is ok, as it's the one I use to connect with my desktop, I just swapped the cable over to the laptop.
Thanks
Tracy

8. RE: ME logging on to NT domain problem
lbyard Dec-07-01 05:30 PM
In response to message 7

Odd... It may be something obvious that neither of us is seeing because it is so obvious. If it were my laptop, I would start by uninstalling everything network and reinstall. If that doesn’t fix it, it could be a winsock problem. This usually fixes those problems: http://duxcw.com/faq/network/winsock.htm. Larry