Hi,

>He did say however it was some security setting to do with cookies.

If that was the case you could probably have got round it be setting Cookieless true in the config which would cause .NET to embed the session id in the URL instead. But it's working now anyway so.....

Regards,
Viv


>>Gerard,
>>
>>Do you have any idea what that Firewall setting was? It might be good to know for future trouble-shooting.
>>
>>~~Bonnie
>>
>>
>>>Hi Folks
>>>Just to let you know that this problem seems to be resolved at last.
>>>On cantacting the Hardware guys who put in the network, there was a
>>> setting in the Firewall which eas somwhow affecting the site.
>>>When they turned off the setting, all worked ok.
>>>Why it ame up as a session variable probel and only with remote logins, I have no idea.
>>>Anyway, thanks again for your help.
>>>
>>>
>>>
>>>>Hi,
>>>>
>>>>My ASP.NET's a bit rusty but:
>>>>One thing to check is whether Session State is enabled on the problem web site. In IIS open Properties/Home Directory; click Configuration button in Application Settings; select 'App Options' tab and make sure 'Enable Session State' is checked.
>>>>
>>>>HTH,
>>>>Viv
>>>>
>>>>
>>>>>Hi Kevin,Viv Thanks for your replies
>>>>>
>>>>>Why then dos it work fine on my development machine ?, and no error
>>>>>comes up. If it is'nt defined , then would this not also happen on my development machine also.
>>>>>
>>>>>I thought that maybe it has something to do with session variable not being allowed on the production machine...do you know if there are any such setings ?
>>>>>
>>>>>Regards,
>>>>>Gerard
>>>>>
>>>>>
>>>>>>My guess is that your session variable isn't defined (or is null)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>Kevin