OMG I seem to have fixed it! I found KB article 292822 which doesn't seem to describe my problem, however one resolution is to add a Registry key called DisableNetbiosovertcpip within the tree of remote access.
It definately fixes the browsing problem but I'm testing whether remote clients are...
Server is in a 2000 domain yes.
WINS is up and running (if only for a couple of 98 clients)
On board 100mbps NIC is disbaled, 3COM Gigabit NIC is installed.
Other than RAS the server is a file server ONLY.
There's 4 other servers on the network.
Just noticed that my VPN server is experiencing...
I've been using browstat.exe to try and diagnose this, but the master browser is reported as the same before and after someone connects.
It sounds like it should be something to do with that though yes.
I could be wrong but doesn't MSN Messenger need to contact a ms passport server to log on? Funny feeling it reverts to using port 80 too, so I don't think your firewall is blocking anything?
The traffic is low, but you need to think about people wasting time chatting to mates over the net.
We...
I could be wrong but doesn't MSN Messenger need to contact a ms passport server to log on? Funny feeling it reverts to using port 80 too, so I don't think your firewall is blocking anything?
The traffic is low, but you need to think about people wasting tme chatting to mates over the net.
Seen a lot of threads on this but have figured out the cause of my problem, just not sure how to resolve it!
A single Windows 2000 server is able to browse the network fine..... until someone dials into it's local RAS server. The remote machine has no problems when remoting. After this happens...
should be same theory to fix it - have a look through the international settings and see if there's anything US in there - change them to UK and see if it fixes it!
Right, it's the regional settings for the aspnet user that you need to change. You can't log in as that user of course though...
so run regedit... then go to HKEY_USERS\CSID (trial and error to find it) \CONTROL PANEL\INTERNATIONAL then export the whole lot as a 98 format reg file. The aspnet...
I've fixed the problem.
It was the regional settings for the ASP.NET user account. Changing it is fun though, I had to find the SSID for the ASPNET user in the registry and change the regional settings there.
After a restart all is fine and I'm getting £s without changing any code!
If anyone...
Thanks Chris,
As a last resort there are several things I could do in the code to fix it, including using LCID stuff.
I'd rather not though - it works fine on one server and therefore should on the other, therefore something is different which i must be able to change?!
Anyone?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.