Search results for query: *

Thanks teleshooter. I was thinking of doing the same thing. Good to know it's a decent option. Another option is to upgrade the SWCS of take advantage of unicast. Unfortunately the server has not been scaled to support unicast connections.

Make sure you are identifing a path for this file. Give the file a name that you will clearly recognize as well. Just ask if you have any questions.

Only the SWCS IP was changed. We have verified all the address, naming etc. The SCCS' can communicate with the SWCS without problem. The upstream data is getting there. Our network is relatively simple with only 1 or 2 hops at the most (LAN extension). All the routers have been configured...

I'm not sure what your network config is but make sure to check your speed and duplex setting on your server network cards. If they are off (static opposed to auto-sense depending on your setup) it could be causing (network) errors that are causing your issues.

Just wondering if anyone has suffered through the same issue we are experiencing. We have three sites that register, listen and recieve multicast traffic for 3 reports - Agent, Application and Skillset (Moving window and Interval to date). In each of the sites the Skillset report data...

Are you recieving any file whatsoever? If so what app are you using to open it? In Options/Printer Port what do you have in the File field?

If you are using PCAnywhere for console level access to the server make sure to open these ports as well. It's a security risk though. Terminal services should provide decent access as well.