A rather unique SQL move issue...

Hooookay.

I have a forum at http://www.lowgenius.com/esdb/forum.

It works wonderfully!

But I'm in the slow process of changing lowgenius.com to be just a business site, and I am doing my personal thing at lowgenius.net.

Both sites are on the same server, and have full access to the same SQL database; I share data from other applications across multiple domains.

I installed WWF on lowgenius.net, and it seems to be working - as you can see if you load .net, the forum information is identical (although obviously the customizations I've made @ .com aren't on .net).

There's just one small problem (well, two):

I can't log in from lowgenius.net.  Nobody can.

Logs in fine at the .com side, but not at the .net side.

I'm sure this is some ridiculously simple thing that I can fix in a minute, but I'm darned if I can figure it out.

I have created a test user account with guest-only permissions if anyone wants to actually DO this and see what the problem looks like.  The username is test_user and the password is test.  Clever, I know.

The working forum is http://www.lowgenius.com/esdb/forum
The not-working one is http://www.lowgenius.net/forum

(Problem 2 is that the 'confirmation code' images used to log in from /admin are *always* broken.  Instead of 6 numbers, I get 2 or 3 numbers and 3 or 4 broken images.  I've checked and re-checked the graphic files and they seem to be fine.  Any ideas here?)

Thanks for help!

Thanks...I *know* that it's not a different app, because there's only like 4 pages on that site right now other than the forum.  I have noticed problems holding sessions before, on other sites on that server, but was never sure what to do about it - for instance, the canned login system in Dreamweaver uses session variables by default, and I re-write it to use cookies instead so that the information persists the way it should.  Now that I think about it, though, even the online help system @ my host has an awful short session time - I've found myself writing a long ticket, submitting it, and finding out that the information was lost because the session timed out and I had to log back in. 

Unfortunately the server side of things is sometimes a bit above my pay grade, as they say - is there something specific that I should ask my hosts to tweak so that the session persists longer (or in this case, at all)?  They've been pretty good to me over the years about responding to issues I raise that often seem unique to my accounts/sites, but I've found that it helps a LOT if I can say "Please do X, Y, and Z" rather than "I have this problem, not sure what it is exactly but here's the result, can you fix it?"  Is there something I can do on the design side, maybe a value I can tweak in the header file for the forums, that will help that session-ID persist?

Thanks a bunch for your help on this.  I wonder why it's only one of the sites, though...makes me think that I should be able to fix the issue from here, if I can isolate it.  Could it be just that I'm using the same 'WWF' string for the forum cookies at both sites?