Mac Server - NT network

[manitobaangler]

We have an iMac installed (OS 9.04) running FM server (5.0v2). Installed where they a NT network. Don't know the rev version.

The basic problem is that their network slows down if the iMac is on and plugged in to the network. (doesn't matter if the FM server is active) If the iMac is left on overnight their internet access is cut off totally.

It sounds like it's two seperate issues. One being the slowdown and the other somekind of process that takes their server down if the iMac is on during the night. We've checked to see if it was possible that a mounted NT drive on the iMac is a possibility and it isn't. They can't mount a network drive manually so most likely the Mac services module isn't installed on their NT's. At this point a bad ethernet card comes to mind. (It is possible to connect to theFM server's solution through one of the clients.)

So, without getting into NT networking garble too deep, is there know issues with this type of setup? As usual the onsite "tech's" are next to useless for information.

Suggestions (other than getting a PC Server) are all appreciated.

[This message has been edited by manitobaangler (edited February 09, 2001).]

[signal]

Does the Mac need to connect to the NT or vice versa? Have you verified different IP addresses?

Appletalk for the Mac is very noisy. I would suggest turning all Appletalk related stuff (printers, networking) if possible and use only TCP/IP.

All this said, I really doubt it's the Mac. The NT sounds like it needs the latest service pack and some better IT people.

[Anatoli]

Run ONLY the FM on Mac. Nothing else. No file sharing or other tasks.

Put always FM as Front application.

Or - you said that, not me

[scratchmalogicalwax]

Frankly your whole setup sound a bit dodgy! sorry mate but I dislike NT and try to avoid it at all costs (not always possible!) it's an over complicated OS made by people that like overcomplicating everything they can get their hands on.

nuff said

[yafreax]

what does scratchmalogicalwax mean anyway . . .?

[ speaking of his name, not his post. . . agree with his post. . .]

interesting.

yafreax

[This message has been edited by yafreax (edited February 23, 2001).]

[flexistentialism]

I administer an NT and 2 Apple Mac networks (which are not connected to the NT network).

Setting up the NT server took about three times as long as both the AppleShare IP 6.3 servers combined!. There is no noticeable performance difference (if anything the mac network is better) so why make NT so much of a pain in the arse to setup, add new hardware (especially things like ISDN cards), admin etc etc....(i could go on but i think you might be getting the point).

hence the comment above.

[LiveOak]

Do you think the interface for ASIP 6.3 is an improvement over 6.2? We have always used Timbuktu for remote administration, so I'm not sure we care much about that improvement. Local admin takes a long time to come up in 6.3. -bd

[manitobaangler]

Little bit more background for you helpful guys out there that took the time to check this post. We really didn't have a choice about their network as they already had NT installed along with all their client workstations. Our solution was just another piece of software to flesh out their system. Their NT is SP5. They didn't set the network up themselves but had contracted another outside source. That's just peachy ain't it!

BTY - This isn't the first installation for this solution. Previously been on mac networks with a few PC workstations. This is the first all PC client install though.

Q/A:

- Does the Mac connect to the NT or vice versa?

Nope, just uses the network for FM.

- Verified dif. IP #'s?

Yup, tried a couple of different ones that were supposed to be open. Didn't get any network error messages. This still could use some investigation though. Same results on all #'s.

- Turn off appletalk.

Pretty sure it is but will double check. Currently no devices using appletalk. FM is set to ONLY use TCP/IP.

- Filesharing.

It's off.

- FM as front app.

Yup.

Pretty much the only logical step left to take next is to get their iMac in-house. We'll get a couple of workstations from both platforms connecting and see what we can do to re-create the issue. Other than that, they had better get the cheque book out if they want us to go on site and tear into THEIR network.

[signal]

Put the Mac on a small 100 base switch (not hub) by itself and link it to the switch for the rest of the network.