have a problem, and this is where it began.
NT4 machine could access shares on a server running 2003. When the server was moved to another table, and thus connected to another port, NT4 machine could no longer access the shares.
Here's the problem, NT4 could ping the server and even ping it by name. Just not connect to the shares. It could telnet and Remote Connect into it.
I had the impression that maybe it had something to do with WINS not properly replicating but this doesn't make sense if nt4 can ping the server by name. Also, if nt4 can't find a machine via wins records, then I recall it uses dns as a last resort.
Other machines running 2000, and xp can access shares, but machines runing nt4 or 98 can't. (if this helps any)
Another bit that might help is this:
The server had some compaq NIC teaming protocol on it and because it was a little flakey with the switch we uninstalled all compaq 'proprietary' protocols.
what kind of reasons would there be for this problem, before the move it had no problem connecting. Could this be a setting on the server? (maybe something like ipsec policies or something?) What else should I be looking for here.
Thanks
NT4 machine could access shares on a server running 2003. When the server was moved to another table, and thus connected to another port, NT4 machine could no longer access the shares.
Here's the problem, NT4 could ping the server and even ping it by name. Just not connect to the shares. It could telnet and Remote Connect into it.
I had the impression that maybe it had something to do with WINS not properly replicating but this doesn't make sense if nt4 can ping the server by name. Also, if nt4 can't find a machine via wins records, then I recall it uses dns as a last resort.
Other machines running 2000, and xp can access shares, but machines runing nt4 or 98 can't. (if this helps any)
Another bit that might help is this:
The server had some compaq NIC teaming protocol on it and because it was a little flakey with the switch we uninstalled all compaq 'proprietary' protocols.
what kind of reasons would there be for this problem, before the move it had no problem connecting. Could this be a setting on the server? (maybe something like ipsec policies or something?) What else should I be looking for here.
Thanks